K8sGPT vs Resolve AI
K8sGPT
k8sgpt.aiResolve AI
resolve.aiSide by side
| Figure | K8sGPT | Resolve AI |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 1 | 1 |
| Spec score · AI DevOps Assistants | 7.9 (#10) | 7.0 (#24) |
| Integrations | Documented integrations include Prometheus, Trivy, Kyverno, KEDA, and AWS. | The integrations page lists tools including Google Cloud, Grafana, Kubernetes, Datadog, GitHub, Splunk, Slack, AWS, Claude, Codex, Cursor, and Notion. |
Plans
In their own words
K8sGPT
K8sGPT scans Kubernetes clusters with SRE-grade analyzers and explains problems in plain English. It provides a CLI, an in-cluster operator, and an MCP interface for AI assistants. The project lists 23 built-in analyzers and supports custom analyzers over gRPC. Fourteen cloud or local AI backends are listed, including OpenAI, Azure OpenAI, Amazon Bedrock, Google Vertex AI, Ollama, and LocalAI. Documented integrations include Prometheus, Trivy, Kyverno, KEDA, and AWS. Analysis without the explain option can run without an AI backend, while explanations require one. Local or air-gapped operation can use Ollama, LocalAI, or a custom REST backend. Anonymization masks names and identifiers before prompts are sent. Optional operator auto-remediation uses a configurable risk threshold. CLI, Docker, and operator paths require a reachable cluster and kubeconfig; operator installation requires Helm 3.