Know WhyIt Broke

KubeiQ Overview: 9 failing of 25 workloads, with workload health for every namespace

KubeiQ is open source AI for Kubernetes. It finds why your workloads fail and hands you the commands to fix them

Steer to What Broke

A real scan of the kubeiq-demo namespace found 9 failing workloads. Pick one, or turn the wheel, and read its entry in the log

Log of kind-kubeiq-dev22 Oct 2026, 23:04:40

Bearing 000°·Confidence 94paymentDeployment in kubeiq-demo

Position: Deployment/kubeiq-demo/payment
Observed: Environment variable DATABASE_URL is missingAdd DATABASE_URL to the container env, usually from a Secret or ConfigMap
Action: kubectl set env deployment/payment DATABASE_URL=<database-url> -c app -n kubeiq-demo
Check: kubectl rollout status deployment/payment -n kubeiq-demo --timeout=120s
kubectl get pods -n kubeiq-demo -l app=payment
Affected: Deployment/kubeiq-demo/paymentPod/kubeiq-demo/payment-6858dfbd56-bv8fnPod/kubeiq-demo/payment-6858dfbd56-tj6s7
Next time: Validate required configuration at startup and in CI before deploying

How a Scan Runs

Every scan takes the same four steps, and none of them changes your cluster. The one on this page took 15 seconds and checked 11 pods, 9 workloads, 8 events and 13 logs

Read the Cluster

Pods, events, workloads, services, nodes and logs, read with the access your kubeconfig already has. Secret values are never read

Cluster Manager listing the pods of kubeiq-demo with their status and restarts

Name the Cause

Known failures are recognized in seconds and their symptoms grouped under one root cause: 126 restarts of payment become one missing variable

Cluster Doctor naming the root cause of payment: environment variable DATABASE_URL is missing

Dig Deeper

When the cause is unclear, an AI agent reads previous logs, ConfigMaps and related resources with read-only tools. Passwords and tokens are masked first

The investigation steps: evidence collected, problems found, and the agent checking orders and queue-worker

Fix and Check

Commands with your real names, filled from the cluster, and the command that proves the fix rolled out. Changes stay off until an admin turns them on

The fix command for payment and the commands that check the rollout

One Finding, Start to Finish

This is how Cluster Doctor reports the payment deployment. Point at a note to find its part

paymentDeployment in kubeiq-demo

94 confidence

Environment variable DATABASE_URL is missing

Container 'app' keeps crashing (126 restarts, last exit code 1). Environment variable DATABASE_URL is missing.

How to fix

Add DATABASE_URL to the container env, usually from a Secret or ConfigMap

kubectl set env deployment/payment DATABASE_URL=<database-url> -c app -n kubeiq-demo

Replace the highlighted values

Check that it worked

kubectl rollout status deployment/payment -n kubeiq-demo --timeout=120s
kubectl get pods -n kubeiq-demo -l app=payment

Affected resources

Deployment/kubeiq-demo/payment
Pod/kubeiq-demo/payment-6858dfbd56-bv8fn
Pod/kubeiq-demo/payment-6858dfbd56-tj6s7

Three Instruments, One Install

Every product ships in the same install and shares your clusters, users and AI settings. Each one leads to the others: a red node on the map opens Cluster Doctor on that workload

Admiralty Chart No 2613 of the north coast of France, published in 1894

Cluster Map showing each app and its resources, broken ones in red — Cluster MapThe chart of your namespace: every resource, how it connects, and what is brokenLearn more

Cluster Doctor showing a failing workload with its root cause and fix command — Cluster DoctorFinds why workloads fail and hands you the commands to fix themLearn more

Cluster Manager listing deployments with one open — Cluster ManagerEvery resource with its YAML, events and logs, read-only by defaultLearn more

Known on Sight

The failures Cluster Doctor recognizes in seconds: CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending pods, Probe failures, Missing config, Service selectors, Init containers, Failed jobs, Stuck rollouts, Node pressure. Anything else goes to the AI agent, so an unhealthy pod is never reported as fine

Pricing

The core stays free and open source. Paid plans will add what teams and organizations need

Free

For anyone running Kubernetes, with every product included

Cluster Doctor, Cluster Map and Cluster Manager. Up to 3 users, with access by project. Read-only by default, opt-in changes with an activity log. Any AI model, or rules only. Community support on GitHub. Open source under Apache-2.0, on your own servers

Get Started

Pro and Enterprise

For teams, and for organizations at scale

Pro: Everything in Free. Unlimited users. Scheduled scans and alerts. PDF investigation reports. More cluster connections.

Enterprise: Everything in Pro. SSO with OIDC and LDAP. Custom roles and fine-grained access. Audit log export and retention. AI keys per team, managed hosting.

Coming Soon

Watch the repository for updates

One command installs every product on your own serversInstall