Kamaji
kamaji.clastix.io
- Free plan
- API
- Self-hosted
What Kamaji is
Kamaji runs Kubernetes control planes as pods in a management cluster, providing a way to operate multiple tenant clusters. Each tenant control plane is independent and separated from others. Kamaji uses upstream Kubernetes components and kubeadm, and tenant clusters are CNCF conformant. Worker nodes can run on bare metal, virtual machines, or cloud instances. Integration with Cluster API supports infrastructure provisioning and lifecycle management. Datastore options include etcd and MySQL- or PostgreSQL-compatible databases through kine; NATS support is experimental. Konnectivity, enabled by default, creates secure tunnels between tenant control planes and worker nodes. Kamaji exposes management-plane and tenant control-plane metrics in Prometheus format. By default, the manager and kubeconfig-generator metrics endpoints use plaintext without authentication; documentation describes an option to require HTTPS and bearer-token authentication. Kamaji collects usage data about its version and tenant control planes, with an opt-out setting. The open-source plan is free under Apache 2.0. Clastix offers subscription-based enterprise support, including SLA response times and ongoing engineering support through Clastix Care, or one-off deployment assistance through Clastix Ready.
Who it suits
Kamaji is aimed at platform engineering, managed services, and multi-tenant environments that need Kubernetes clusters at scale. Its free open-source plan may suit teams operating control planes in their own management cluster.
Good to know, and what to watch
- Separates tenant control planes from one another.
- Integrates with Cluster API for provisioning and lifecycle management.
- Supports etcd and MySQL- or PostgreSQL-compatible datastores.
- Konnectivity tunnels are enabled by default.
- Provides Prometheus-format metrics for both planes.
- NATS datastore support is experimental.
- Metrics endpoints use unauthenticated plaintext by default.
- Kamaji collects usage data unless users opt out.
Plans
Every plan and priceKamaji Open Source
Free plan
The verdict
Kamaji combines tenant control-plane management with Cluster API integration and multiple datastore options. Review the default metrics endpoint security and usage-data settings when planning a deployment.
What the maker publishes
- Cluster API
- Kamaji integrates with Cluster API for infrastructure provisioning and lifecycle management. source
- Datastores
- Supported datastore options include etcd and MySQL- or PostgreSQL-compatible databases through kine; NATS support is experimental. source
- Headquarters
- Naples, Italy source
- Infrastructure
- Worker nodes can run on bare metal, virtual machines, or cloud instances. source
- Intended users
- The product is described for platform engineering, managed services, and multi-tenant environments that need Kubernetes clusters at scale. source
- Kubernetes compatibility
- Kamaji uses upstream Kubernetes components and kubeadm, and its tenant clusters are CNCF conformant. source
- Metrics security
- By default, the manager and kubeconfig-generator metrics endpoints use plaintext without authentication; the documentation describes an option to require HTTPS and bearer-token authentication. source
- Monitoring
- Kamaji exposes management-plane and tenant control-plane metrics in Prometheus format. source
- Multi-tenancy
- Each tenant control plane operates independently, with separation between tenants. source
- Networking
- Kamaji integrates Konnectivity to provide secure tunnels between tenant control planes and worker nodes, and it is enabled by default. source
- Purpose
- Kamaji runs Kubernetes control planes as pods in a management cluster to simplify operating multiple Kubernetes clusters. source
- Support
- Clastix offers subscription-based enterprise support plans for Kamaji. source
- Support options
- Clastix Care includes SLA response times and ongoing engineering support, while Clastix Ready offers one-off deployment assistance. source
- Telemetry
- Kamaji collects usage data about its version and tenant control planes, and users can opt out through deployment settings. source
Checked against the maker's pages on 3 Oct 2026.