How Gameplane compares
A quick look at how a Kubernetes-native control plane differs from single-host, Docker-based panels.
Hosting model
Single host, Docker containers
Kubernetes primitives — CRDs, an operator, StatefulSets, PVCs
Scaling
One host per install
Same control plane, from a k3s homelab to a multi-node production cluster
Operational model
Tooling differs by install size
Same tooling at every scale
Automation path
Dashboard-driven
Dashboard or kubectl apply — both stay in sync via the operator
This is a high-level snapshot, not a feature-by-feature audit. For a fuller comparison against AMP, Pterodactyl, and PufferPanel, see thedocs.
Why Kubernetes-native matters
The operator handles everything a cluster admin expects from a K8s controller — declarative reconciliation, owner references, leader election. Advanced users can bypass the dashboard entirely and manage Gameplane with kubectl apply.
Gameplane itself is open-source, licensed AGPL-3.0-or-later — see thelicense on GitHub.