KubeBolt documentation
Install KubeBolt, connect a cluster, and run it. Start with the path that matches how you want to run it.
Start here
There are two ways to run KubeBolt, and they diverge immediately. Pick the one that matches you: the rest of the docs assume you already chose.
Managed KubeBolt Cloud
Nothing to host. Sign up, paste one command into your cluster, and you
have data. Free plan, no time limit.
Get started on Cloud → Self-hosted Run it yourself
Apache 2.0, your infrastructure, your AI provider. Helm into a cluster,
or Docker Compose against a kubeconfig.
Quick start →
If something is already wrong
Agent connected but the dashboards are empty, a limited-access banner, a 503 while the connector syncs, a lost admin password: the troubleshooting page is symptom-first.
The rest of the docs
Deployment Guides One page per platform, with the provider-specific setup. 5 pages Core Concepts What each screen shows and how the pieces fit. 10 pages Security The four lenses, and wiring the scanners you already run. 4 pages Configuration Every knob: AI, auth, RBAC, metrics, notifications, agents. 11 pages API Reference The REST surface and the realtime channel. 2 pages Project What shipped, what is next, and how to contribute. 4 pages
Most asked
- Enabling Kobi — Turn Kobi Copilot on with your own key — the copilot.* Helm values, the KUBEBOLT_AI_* environment variables, and the Configuration page that overrides both.
- Connecting Clusters — Three ways to connect a cluster — kubeconfig, the KubeBolt agent, or metrics-only. The Add cluster wizard generates the exact helm command for you.
- RBAC & Permissions — KubeBolt auto-detects your kubeconfig's permissions and adapts automatically.
- Compatibility — Which agent version pairs with which backend, what breaks when they disagree, and which Kubernetes versions and providers are supported.