New · Kobi reads your AWS account

From alert to root cause, no kubectl needed.

Kubernetes monitoring: health, capacity, cost and security in one place, with an AI SRE.

Start free
KubeBolt Fleet view: 3 clusters, kubeshop-eks in a critical state, and $717 per month.
Kobi Copilot

The store has been returning errors for a few minutes, what's going on?

Investigation 0:55 16 reads · 4 in AWS · 1 guide · 1 could not be read

The network rule that let the pods in is gone.

The database is available: the failure is in the network. It gives you the command to restore it, and you run it.

“Fast visibility into cluster health. Less friction when investigating incidents.”
David González Vega · founder and Platform Architect, Nubyron

1,400+ pods

and 41 servers monitored today at companies in Europe and LATAM: consulting, data and services. November 2026

55 s vs 7 min 5 s

Kobi and AWS DevOps Agent, same incident. One run. See the method →

13 releases in 10 weeks

From 2.1 to 2.6, one every five days. Changelog →

01 · The platform · When you connect your cluster

It reads what you already run.
Out through one channel.

The agent brings the basics and finds the tools you already use on its own. Each one lights up its view. What you don't have, you don't need.

Your cluster · EKS, GKE, AKS, OpenShift or any KubernetesYour cluster · any KubernetesYour cluster

Built into the agentBuilt in

  • API server state, events and changes built in
  • kubelet resource metrics built in
  • Observed trafficTraffic who talks to whom built in

If you have it, it finds itIf you run it

  • Prometheus your metrics optional
  • OpenCost real cost optional
  • Cilium · Hubble L3/L4/L7 flows optional
  • Trivy image CVEs optional
  • Kyverno admission policies optional
  • Falco runtime threats optional
  • ArgoCD · Flux apps, sync, health optional
  • Helm deployed releases optional

KubeBolt agentAgentaction applied ✓

KubeBolt · Cloud or self‑hostedKubeBolt

KubeBolt with Kobi
  • Health built in
  • Map built in
  • Capacity built in
  • Cost with OpenCost
  • Security with Trivy +2
  • Reliability with Cilium

Where it goes

Your teamTeamSlack, Discord or email
AI modelsModelsAnthropic and OpenAI, or yours
Your AI clientMCPOver MCP, read-only

What it reads outside

Your cloudCloudAWS, and Azure on open source
  • Health built in
  • Map built in
  • Capacity built in
  • Cost with OpenCost
  • Security with Trivy +2
  • Reliability with Cilium

The six views

All of this, nothing to configure.

Six views, ready when you connect. Each opens with the number that matters and, when something fails, says who and since when.

The six views

All of this, nothing to configure.

Six views, ready when you connect. Each opens with the number that matters and, when something fails, says who and since when.

Cluster health 86 of 100, with catalog-api and orders-api at zero available replicas

Healthbuilt in

86 / 100cluster health

What's broken right now, by name and time. 24 rules active from the first minute.

Cluster map: the shop, from the ingress to its services, its pods and what lives outside the cluster

Mapbuilt in

Service → Pod

What depends on what, from service to replica, with its status in view.

Cluster trends: CPU, memory, network and disk

Capacitybuilt in

1.4 coresreclaimable

What you request against what you use, with the sizing recommendation.

Cost: $147 a month, $101 idle and spend trend

Costwith OpenCost

$101/mo idle

69% of the spend nothing requested. And you see where.

kubeshop-eks security: 26 findings, the top five images and the workloads to fix

Securitywith Trivy, Kyverno, Falco

26findings · 2 critical

Your scanners in one view, by workload and by image. KubeBolt doesn't scan: it reads them.

Reliability: the cluster error rate spikes and shop-web is the hot-spot

Reliabilitywith Cilium

1.0 %5xx · mostly shop-web

Errors and latency by service, from what Hubble sees.

Real captures of the app. What you install and what you don't

  • Healthbuilt in 86 / 100 cluster health · 9 insights
  • Mapbuilt in Service → Pod ingress · service · pod
  • Capacitybuilt in 1.4 cores cores reclaimable · 13 recs
  • Costwith OpenCost $101 69% of spend nothing requested
  • Securitywith Trivy, Kyverno, Falco 26 findings · 2 critical
  • Reliabilitywith Cilium 1.0 % 5xx · mostly shop-web

02 · Kobi, one agent, two modes

Ask it, or let it act. You decide how far it goes.

You choose how far: suggest only (default), approve each action, or autonomous (open beta).

CopilotAvailable today

Ask it.

It investigates for you and answers with the root cause.

Kobi Copilot Available today

The store has been returning errors for a few minutes, what's going on?

Investigation 0:55 16 reads · 4 in AWS · 1 guide · 1 could not be read
  1. Insights 5 ms 11 insights · 2 critical · 6 warning · 3 info
  2. Logs · orders-api 575 ms 1 of 1183 lines match the filter · burst 22:16-22:27
  3. YAML · Service shop-db 271 ms Service · last write kubectl-client-side-apply Oct 27 09:34
  4. Leaves the cluster → AWS read-only
  5. AWSRDS · DescribeDBInstances 2.0 s 1 DB instance
  6. AWSRoute 53 · ListHostedZonesByName 2.1 s Denied — AccessDenied for route53:ListHostedZonesByName
  7. AWSEC2 · DescribeSecurityGroups 2.0 s 1 security group
  8. AWSCloudTrail RevokeSecurityGroupIngress · 22:16:05

The network rule that let the pods in is gone.

The database is available: the failure is in the network. It gives you the command to restore it, and you run it.

You can also ask Where am I paying for capacity I don't use?Which workload has the most findings?

Watch Kobi resolve it (45s)

AutopilotOpen beta

Let it act.

If the incident is in the catalog, it fixes it, verifies it and rolls back if it fails.

Kobi Autopilot Open beta

Needs a human · 4:05

  1. TriageHaiku 5.5 Warning · routed to investigation
  2. InvestigatorSonnet 5.5 Logs · orders-api · 1 of 1183 lines match the filter

    Leaves the cluster → AWS us-east-2 · read-only

    EC2 DescribeSecurityGroups1 security group

    RDS DescribeDBInstances1 DB instance

    Root cause · 92% · needs a human
  3. Planner No action
  4. Executor skipped · nothing to run
  5. Postmortem Postmortem · 2 action items

The cause is outside the cluster: it touches nothing and tells you what it found.

If the incident is in the catalog, it fixes it, verifies it and rolls back if it fails: Resolved · verified · 0:33

Watch the incident · 1:40

You choose how far: suggest only (default), approve each action, or autonomous (open beta).

Suggest onlydefault · Kobi proposes

Approve and executeyou approve each action

Autonomousopen beta · destructive actions need your sign-off

Multi-provider

The best models from Anthropic and OpenAI. And the one you prefer.

Claude, GPT, Grok, GLM, Kimi, DeepSeek, Mistral, Llama, Qwen

Copilot

On Cloud it's managed, with no key to configure: Anthropic as primary and OpenAI as fallback. On open source you bring your provider: Anthropic, OpenAI or any compatible API, such as Azure OpenAI, xAI, DeepSeek, Groq, Mistral, OpenRouter, Ollama or vLLM.

Autopilot

Five stages, each with its own model and a fallback if it fails. Claude on the Anthropic engine, or GLM and Kimi through an OpenAI-compatible gateway.

Subagent models Engine Anthropic Gateway · GLM / Kimi

  1. Triage Economy Claude Haiku 5.5 on fail → Claude Haiku 4.5
  2. Investigator Balanced Claude Sonnet 5.5 on fail → Claude Sonnet 5
  3. Planner Balanced Claude Sonnet 5.5 on fail → Claude Sonnet 5
  4. Executor Balanced Claude Sonnet 5.5 on fail → Claude Sonnet 5
  5. Postmortem Premium Claude Opus 5.5 on fail → Claude Opus 5

Copilot: a real lab run, sped up. Autopilot: a generated view with the product's literals. AWS connector on Cloud from Team; on open source, Azure too.

03 · How far it goes

The model doesn't decide what can touch production.

Closed catalog

Six typed actions. Never free-form kubectl.

Your RBAC

A ServiceAccount with three tiers. No kubeconfig on any laptop.

Verifies and reverts

It checks the pods come back Ready. If not, it undoes its change.

04 · Pricing

Free to start. No per-user fees.

Open source

No cost

On your own Kubernetes cluster, under Apache 2.0. With Kobi Copilot, your own key and the AWS and Azure connectors.

See it on GitHub

Cloud · Free

$0

2 clusters, 10 nodes and 150 pods, 3 users, 15 days of retention and 100 AI credits a month. No card.

Start free

Cloud · Team

$49 /mo + usage

Unlimited clusters, 15 users, 30 days of retention, 1,500 AI credits a month and the AWS connector for Kobi.

Work out your bill

We bill infrastructure, not people: the team grows and the bill doesn't.

Cloud

Connect your cluster
in under 2 minutes.

Create the account, install the agent, and on the first alert you'll see Kobi working with you. Start in suggest-only.

Free · 2 clusters · no time limit

Example · the app generates it with your token docs

helm install kubebolt-agent \
  oci://…/helm/kubebolt-agent \
  … --set cluster.name=<cluster-name>

Rather see it with a person? Book 20 minutes

Open source on your cluster

Install KubeBolt on the cluster you want to monitor. The agent is added from inside the product.

bash
$ helm install kubebolt \
  oci://ghcr.io/clm-cloud-solutions/kubebolt/helm/kubebolt \
  --namespace kubebolt --create-namespace --wait

Apache 2.0 · ★ on GitHub · the agent dials out, never in.

What's next

One note per release, no noise.