Minimal overhead. Just control planes, virtualized.
it's a cluster f*ck.
Run thousands of Kubernetes control planes on a single shared API server — just 0.8 MB of memory overhead per control plane.
Cluster topology
Management Plane
Getting started
Three commands.
$ brew tap kplane-dev/tap$ brew install kplane
$ kplane up$ kp create cluster example1 API server. Many control planes.
Each control plane is a path-isolated, policy-driven environment. Stack thousands of them on a single shared core without duplication.
Isolation by design.
Requests are routed per cluster path with native Kubernetes semantics. Every control plane boundary is enforced, not assumed.
0.8 MB per control plane.
Scale without the fixed cost of full-stack clusters. The footprint is so small, density becomes your advantage.
Built for density, isolation, and speed
Virtualized Control Plane
Single apiserver, shared storage, per-cluster isolation. Every plane runs lightweight without duplicating infrastructure.
Multi-Cluster Aware
Controllers share caches and informers across clusters. No redundant watches, no wasted memory.
Policy-Driven Access
CRD-backed policies with native RBAC inside each plane. Fine-grained access control at every boundary.
The approach
Real virtual clusters
Kubernetes plumbing
Kubernetes plumbing
We handle the API server, etcd, controllers, and scheduler so you don’t have to. Every cluster gets its own control plane without the operational weight.
How it works
How it works
Control planes become lightweight slices on a shared core. You keep native Kubernetes behavior and isolation, without the compute tax.
Short version
Short version
Virtual control planes. Native Kubernetes. Near‑zero overhead.
Built by platform teams pushing Kubernetes to its limits.