Fourteen years designing, automating and running cloud infrastructure — AWS, GCP and Azure, Kubernetes, Terraform — for teams who need it to stay up. Lately I've been building my own: three open-source products, shipped end to end and running in production today.
Three products taken from an empty repo to something people actually run — the infrastructure, the product surface and the operations. All open source: read the code before you read my CV.
A full cloud platform, built solo: multi-tenant compute with hardware isolation, managed Postgres with point-in-time restore, git-driven app hosting with blue-green deploys, serverless functions, two SDKs and usage billing — on GCP, with Terraform and Ansible underneath. Workloads boot in 179 milliseconds.
Prompt → a running full-stack app, then fork it. A self-hostable Lovable/v0 alternative where generated apps run in real microVMs with real databases — and you can branch a running app and its data to explore variations in parallel.
A drag-and-drop canvas for AI agent workflows. Wire LLMs, databases, APIs and code-execution nodes together and deploy — with code nodes running in isolated microVMs so untrusted code never touches the orchestrator.
Long enough to have seen most failure modes twice — and recent enough to have built a production platform from scratch this year.
Cloud architecture, Kubernetes, Terraform, CI/CD, observability and the kernel-level plumbing beneath it. I've owned every layer, so I know where they break each other.
Solo on-call for a multi-tenant platform. That shapes the designs I bring you: blast radius, recovery paths, and alerts that fire before customers notice.
A complete cloud platform in about six months, alone. Public commit history — you don't have to take my word for the pace.
I pay my own cloud invoice, so cost is an engineering constraint to me. Scale-to-zero and usage billing exist because idle infrastructure offended me.
Not a keyword list — this is what I operate in production right now.
Platform engineering, cloud architecture, and SRE work — for teams who need someone who has operated what they're about to build.
GCP, AWS and Azure architecture. GKE/EKS, autoscaling, multi-region, migrations — design review or hands-on build.
Terraform, Ansible and CI/CD that reproduces your infrastructure instead of describing it. Blue-green deploys and clean rollbacks.
Alerting that catches failures before customers do, plus the unglamorous work of cutting a cloud bill in half.
The rare specialty: hardware-isolated compute, snapshot/restore, egress policy. If your product executes code you didn't write, this is my day job.
Deep technical posts written from incidents I had to fix myself.
Hibernate took 50 seconds. Wake took 14, not the 1.3 I had reported. The measured price of building scale to zero on a Firecracker fleet, and every fix.
9 minSep 2, 2026Every AI sandbox matrix has a creation time column spanning 0.79ms to 2.7s. That spread is definitional, not performance. Here's how to make it comparable.
10 minSep 2, 2026A free-tier signup mined crypto on my microVM fleet in 27 minutes. Containment held perfectly and it changed nothing. What I built afterwards, in what order.
9 minI take a small number of consulting engagements, and I'm open to select full-time infrastructure roles — remote.
Platform engineering, cloud architecture, SRE. Project-based or monthly retainer.
$75–100/hr · $6–8K/mo retainer
What I deliver →Senior/staff/principal infrastructure, platform or SRE. Remote, with US or EU overlap.
Go · Kubernetes · Terraform · GCP/AWS/Azure
LinkedIn →Tell me what's slow, expensive or on fire. I reply to everything that isn't a template.
hello@ajayk.sh
Email me →