When you tell an engineer you are building a deployment platform, the first question is usually: which flavor of Kubernetes? It is the default answer for running containers in production. We went a different way on purpose, and we want to explain why.
The job to be done
Our goal is narrow and specific: take a developer’s app from a git commit to a live URL in seconds, reliably, cheaply, and without making them learn a new platform. That goal does more to shape our infrastructure than any industry default.
What Kubernetes is great at
Kubernetes is genuinely excellent for large organizations running many teams and services with complex networking, custom controllers, and dedicated platform engineers. If that is you, it earns its complexity.
But that complexity is the product. For a single developer shipping a handful of apps, it is a tax: more moving parts, more ways to misconfigure things, more surface area to secure, and a steep learning curve before you get a URL back.
Why Swarm fits our users
- Auditable. The whole system is small enough to understand end to end. When something breaks, you can actually trace it.
- Portable. It is standard Docker. Your images and workflow are not tied to one vendor’s control plane.
- Cheap to run. Fewer components means lower overhead, and we pass that saving on to you.
- Fast to reason about. Simpler orchestration means we can make deploys fast and keep them fast.
Calling it “unsophisticated” misses the point. Unsophisticated by design is a strength when your users want one command and a URL, not a platform to operate.
The tradeoffs we accept
Swarm has a smaller ecosystem and fewer turn-key add-ons. We take that on ourselves so you never have to. The things a platform should handle, like rollouts, health checks, secrets, and rollback, we build and operate for you. The things you should never have to think about, you will not.
The bottom line
We did not pick the tool with the most features. We picked the one that lets us deliver the experience we care about: commit, one command, live in seconds. If that sounds like the deploy story you want, get on the list.