Cloud & DevOps
I set up and operate cloud infrastructure on the stack I actually use in production: Vercel for serverless, DigitalOcean for Kubernetes and VMs, Cloudflare for DNS and edge, and Terraform to version-control all of it.
At a glance
- Backed by public open-source code, not just a description on a page.
- Long-form essays on the same topics, with sources cited.
- Production patterns the same hiring team can lift straight into their stack.
About Sarma
Sarma is a UK-based software engineer running Sarmalinux as a one-person studio. He ships nineteen open-source repositories spanning LLM gateways, coding agents, inference, storage engines and consensus, and writes long-form engineering essays at sarmalinux.com/blog. Senior IC, end to end.
I do not do AWS or Azure as a primary platform. That is deliberate. My production infrastructure runs on Vercel for Next.js deployments, DigitalOcean Kubernetes for containerised workloads, Cloudflare for DNS, edge caching, and Workers, and DigitalOcean managed Postgres where Supabase is not the right fit. All of it is Terraform-managed, one apply and a fresh environment comes up. I have published both k8s-ops-toolkit (a Helm chart for Next.js with a full observability stack: ingress-nginx, cert-manager, kube-prometheus-stack, Loki) and terraform-stack (Vercel + Supabase + Cloudflare + DigitalOcean in one repo). If your project fits this stack, I can move fast because I am not learning it on your time.
What this covers in practice
Kubernetes on DigitalOcean
Cluster setup, Helm chart configuration, ingress-nginx, cert-manager, horizontal pod autoscaling, and Loki log aggregation. k8s-ops-toolkit is the production reference.
Vercel deployments
Production-grade Next.js App Router deployments with environment management, preview branches, Edge Config, and Vercel Postgres or Supabase backends.
Cloudflare configuration
DNS management, Workers for edge logic, Pages for static assets, WAF rules, and R2 for object storage. Integrated into Terraform so it is reproducible.
Terraform infrastructure
Full IaC across Vercel, Supabase, Cloudflare, and DigitalOcean in one terraform-stack repo. Modules are independently usable. State in Terraform Cloud or S3-compatible storage.
CI/CD pipelines
GitHub Actions pipelines for build, test, typecheck, and deploy. Environment promotion from preview to production with rollback.
Observability
kube-prometheus-stack for metrics, Loki for logs, Grafana dashboards, and alerting via PagerDuty or Slack webhook.
Stack
Recent work in this lane
What a hiring team gets
Read the evidence
Open the public repositories, browse past work, then look at the hiring page if a PAYE shape fits your team.