Runs 21 clusters from one Git repo
Argo CD hub-and-spoke on EKS in three AWS regions. Moving a live cluster onto it passed all 535 in-cluster health checks.
Chicago, working with teams anywhere in the US
I set up the cloud, deploy pipelines and AI tools that small and mid-size companies run on. At my day job I run 21 Kubernetes clusters in three AWS regions.
Waste and risk in your AWS account, fixed in Terraform.
GitLab CI, Helm and Argo CD, with tests on every merge.
Off EKS extended support, at $0.60 a cluster-hour.
Terraform modules, Helm library charts, CI components.
Company AI accounts, sign-on and a written use policy.
Set hours a month to keep it patched and monitored.
public policy too.How I work
Every change goes through a merge request, passes its tests before it ships, and comes with a runbook, so your team can run it without me.
Argo CD hub-and-spoke on EKS in three AWS regions. Moving a live cluster onto it passed all 535 in-cluster health checks.
Weighted DNS added to the shared Helm library chart every service uses, driven by Kargo. Promotions sync in seconds, not three minutes.
Over 60 resources in four regions moved into reusable modules with moved blocks, so nothing was destroyed or rebuilt.
Managed Kafka with SCRAM sign-in, and CI runners that reach it across AWS accounts.
Every change is a merge request with an AI review, a smoke test and automatic rollback.
It reads alerts, opens tickets and merges low-risk fixes. What it can reach sets its limits, not its prompt.
Single sign-on across the apps, secrets in Infisical, and a nightly scan that files each vulnerability as an issue.
I'm a platform engineer in Chicago. By day I build the platform a multi-region SaaS company ships on: AWS, Terraform, Kubernetes, Argo CD and Istio.
I consult for companies that need that kind of work but not a full-time hire. I take a few clients at a time, and each project is scoped in writing before it starts.
I don't take GovCloud work. On AI policy I write the technical controls, and your own lawyer or accountant signs off.
Small and mid-size companies that run on AWS and have no one whose job is to own the infrastructure.
Projects have a fixed price, agreed in writing before work starts. Ongoing work is a monthly retainer for a set number of hours.
The code in your own repository, a runbook for each system, and a walkthrough with your team.
Yes. I never name a client or show its systems without written permission.