About
Hey, I'm Sid 👋 and I build Sailor.
Here's what I've realized after years of doing infra across wildly different environments: we're all doing the same thing. Nobody is reinventing the wheel. The journey is shockingly similar whether you're running a single EC2 box or a fleet of Kubernetes clusters — just at different scales.
Same problems, different scale
Small startup
One engineer, the whole stack, same problems.
Early on I was the only infra person. EC2, deploys, on-call, all of it. You'd think that's a completely different world from "real" infrastructure — but honestly? The problems were the same. Networking, reliability, deployments, logs. Just smaller blast radius.
On-prem
Different hardware, same patterns.
Bare metal, Ansible, no managed services. People act like on-prem is a totally different discipline — but you still need routing, redundancy, monitoring, and a way to deploy without breaking things. The abstractions change, the actual job doesn't.
Kubernetes at scale
Hundreds of thousands of messages. Same game.
Co-founded a startup, took it through YC, ran EKS at serious volume. Migrated from EC2 to EKS, CloudFormation to Terraform, scripts to CI. And the whole time I kept thinking — we're all solving the same handful of problems. Networking. Deploys. Observability. Incidents. The scale changes, the requirements don't.
After doing this enough times, across enough environments, the thought just kept coming back: "I think I can automate this." So that's what I'm building.
Want to talk infra?
Whether it's Sailor, a scaling problem, or just nerding out about Kubernetes — I'm always up for a chat.
Book a 30-min call