· Architecture · 6 min read

What runs in our control plane, and what stays in your cloud account

By Ethan Cole, Co-Founder & CTO

Running containers on AWS, GCP, or Azure works best when the boundary is explicit: Nimbus coordinates rollouts, while your clusters, images, and data stay yours.

Engineering teams evaluating a container platform usually ask the same question within ten minutes: where do our workloads and database traffic actually live?

With Nimbus, the split is deliberate. We operate the control plane — the visual service designer, deployment orchestration, rollout history, and environment coordination. Your Kubernetes cluster and running containers stay inside the AWS, GCP, or Azure account you already pay for.

Your container images stay in your registry, your VPC routing stays under your cloud permissions, and persistent data never detours through a third-party multi-tenant runtime.

That architecture avoids both painful extremes. You do not give up cloud credits, compliance posture, or network locality to get a clean deploy workflow, and you do not have to babysit control-plane upgrades yourself.

If your organization eventually hires a full-time platform group, the cluster and workloads are already sitting in your own cloud account in standard Kubernetes shape.

All notes