KubeBolt docs
ENES GitHub

Getting Started

KubeBolt Cloud

Managed KubeBolt at app.kubebolt.io — nothing to host, with a Free plan and Kobi Autopilot in open beta.

On this page
  1. Open source vs Cloud
  2. Kobi Autopilot (open beta)
  3. AI credits
  4. When Kobi is busy
  5. Out-of-date agents by email
  6. Next

KubeBolt Cloud is the managed offering of KubeBolt, the Kubernetes operations platform: the same core, run by us at app.kubebolt.io, plus the features that only exist there. You connect clusters with the agent exactly as documented in Connecting Clusters — the agent only ever dials outbound, so no inbound access to your clusters is required.

Sign up at app.kubebolt.io/signup with email or social login (Google, Microsoft, or GitHub); the walkthrough is Getting started on Cloud. Free and Team are available today; Business and Enterprise arrive in stages — see the public roadmap and Pricing.

Open source vs Cloud

Open source (self-hosted)Cloud
Core platform — dashboards, insights, security findings, actions, multi-cluster✅ Apache 2.0, free forever✅
Kobi Copilot — you ask, Kobi answers and proposes actions you approve✅ With your own LLM key (Anthropic or any OpenAI-compatible API)✅ Managed, no key to configure
Kobi MCP server (read-only)✅✅
Cloud connectors — Kobi reads your cloud account✅ AWS and Azure, with your own credentials✅ AWS, from the Team plan
AI usageYou pay your provider directlyAI credits included per plan
Kobi Autopilot — Kobi acts on its own, you approve the destructive part—✅ Open beta, from the Free plan
Hosting, upgrades, backupsYouUs
Sign-inLocal users and passwordsEmail and password, or Google, Microsoft and GitHub
Teams & organizationsOne organization, a single default team; Viewer / Editor / Admin rolesOrganizations and teams with roles

The open-source core is not a demo — it’s the same engine, including Kobi Copilot, and it stays Apache 2.0. Cloud is for teams that would rather not run it themselves, and for Kobi Autopilot.

Kobi Autopilot (open beta)

Kobi Autopilot is Kobi’s autonomous mode: it investigates an incident and, within the policy your team sets, remediates it. It runs only on Cloud and is in open beta from the Free plan. Its settings live in Administration → AI & Autopilot → Kobi Autopilot. It ships with deliberate guardrails:

Autopilot is a Cloud feature. In the open-source distribution, Kobi Copilot proposes and you approve — see Actions & Governance.

Repeats and credit pacing

Three rules keep Autopilot from spending the month on problems it has already diagnosed. The first and the last are settings in Administration → AI & Autopilot → Kobi Autopilot → Repeats and credit pacing.

A parked incident (skipped_quota, skipped_schedule, skipped_rate_limit, skipped_pacing) stays one incident for as long as the problem lasts.

Who hears about a recommendation

A recommendation waits for a person, so Autopilot makes sure one hears about it. In Kobi Autopilot → Who hears about it, Email recommendations and a weekly digest to the organization’s admins is on by default and independent of insight email, so silencing noisy insight mail does not silence Autopilot.

A run that concludes only a person can fix the problem (the cause is outside what Autopilot may change, or the diagnosis is below the confidence floor) ends as a recommendation too, with a warning notice that says Autopilot changed nothing. Failed is kept for runs that tried and did not get there.

Only the organization’s master notifications switch turns both emails off.

Home’s Needs your attention lists what Autopilot waits on a person for: pending approvals, runs that stopped because only a person can go on, and recommendations nobody applied. Mark as handled, on the incident (Editor), closes a recommendation or a stop you took care of or decided not to act on, with an optional note; either also closes itself when its condition clears. See Home and Fleet.

AI credits

Cloud plans include AI credits consumed by Kobi Copilot conversations and Autopilot runs; there is no bring-your-own-key on Cloud. Usage is visible in the unified AI hub, in credits, not dollars: the Copilot and Autopilot usage views, the credit pool, the session and run details and the incident pages all count in the same unit your plan is sold in (Administration → AI & Autopilot → Usage & Credits). The app warns at 80% of the pool, and the organization’s admins get an email as it runs low. When a plan’s monthly credits run out, Kobi pauses until the next month — the non-AI parts of the product keep working.

When Kobi is busy

A Kobi question holds the AI provider for tens of seconds, so each plan sets how many questions can run at once, per organization and per person. A question past that limit waits in line, up to 30 seconds, inside its own stream. The panel shows the wait from the first second: whose limit is full (yours or the organization’s), how many questions are running and how long it has waited. The question starts as soon as a turn frees; past 30 seconds it ends with a message naming the full limit.

The colour says what you have to do:

Out-of-date agents by email

Besides the chip on Clusters (Multi-Cluster), the organization’s admins get an email when one of its clusters should upgrade its agent, with the same reasons, command and warnings as the Clusters dialog. Each cluster appears under the name you gave it, with a link that opens its dialog.

Next

Signing up? Go straight to Cloud onboarding. Self-hosting instead? Installation methods covers every way to run KubeBolt yourself.