· Architecture · 5 min read
What “Kubernetes-compatible” actually means
By Ethan Cole, Co-Founder & CTO
Compatibility is not a kubeconfig and a wave goodbye. It is ordinary images, a real cluster in your account, and a way out.
A lot of platforms say they are simple Kubernetes. Some mean “we hid it.” Some mean “here is a kubeconfig, good luck.” We mean something narrower, on purpose.
Your build produces an OCI image. Nimbus runs that image. There is no proprietary runtime and no rewrite of your process model. If the container starts in Docker, it can start here.
The cluster is Kubernetes in your AWS, GCP, or Azure account. We operate the control plane you see: services, environments, deploys, secrets, scale. We do not ask you to babysit node pools to ship a bugfix.
The spec we generate stays Kubernetes-shaped. If you outgrow Nimbus, or you just want a second opinion, you can take the workload with you. Lock-in by obscurity is a bad trade for a team this size.
What we will not do is hand you a raw cluster and call it a product. The point of the interface is that day-2 operations have defaults. Compatibility is the floor, not the experience.