· Company · 5 min read
Why we built Nimbus
By Ethan Cole, Co-Founder & CTO
We started Nimbus in Austin because product engineers were spending quarters learning ingress instead of shipping.
Nimbus Container started in Austin in December 2023. The people building it had just spent a quarter standing up Kubernetes for a product that was still finding its first customers. The cluster worked. The calendar did not.
Ingress, certs, probes, Helm values, node upgrades — none of it was exotic. All of it was someone on the product team doing it between features. That is a fine hobby. It is a bad job description for a team of fifteen.
The tools on offer split in two. Docker Compose was honest and local, and it fell over the moment you wanted a second environment or a restart that was not a shell script. Raw Kubernetes was powerful and assumed a platform group we did not have and did not want to hire yet.
Nimbus is the layer we wanted in between. You draw services and dependencies. Deploys know about health and startup order. Logs, metrics, and traces are there before the first incident. Kubernetes stays underneath, in your cloud account, running normal images.
We are early. The product is aimed at teams of about 10 to 100 people who are past Compose and not ready to staff a platform org. If that is you, the early-access list is open.