Back to home
Use Case
Self-Service Kubernetes for Platform Teams
Developers need clusters. Platform teams can't provision them fast enough. Shared clusters create noisy-neighbor problems and restrict what developers can do. Dedicated clusters cost too much and take too long to provision.
kplane gives every developer their own Kubernetes control plane — provisioned in seconds, isolated by default, running on shared infrastructure.
What platform teams get
- Provision and deprovision control planes via API or CLI
- Per-team RBAC, CRDs, and namespace isolation without manual setup
- Policy-driven resource quotas and node pool allocation
- One management plane to monitor and operate, not hundreds of clusters
- Horizontal scaling when you outgrow a single replica
What developers get
- A real Kubernetes API with full compatibility
- kubectl, Helm, ArgoCD, Terraform — standard tooling works
- Cluster-admin access to their own control plane
- No tickets, no shared restrictions, no waiting
How it fits
kplane is the multi-tenancy layer. It sits between your infrastructure (nodes, storage, networking) and your developers. Combine it with GitOps (ArgoCD, Flux), service meshes, policy engines, or whatever your platform stack already includes. kplane handles isolation and density — everything else stays the same.