Overview - Komodor

The Komodor Agentic Operation Platform (KAOP) runs AI agents on your production operations work: investigating incidents, reviewing changes, finding wasted spend. It does so with the controls your security team will ask about: each agent has its own identity and permissions, reaches your systems without ever seeing a credential, and leaves a complete record of what it did and what it cost. Under the hood it has three parts: a control plane Komodor operates, the SDK you write agents with, and the workers that run them, on Komodor’s infrastructure or inside your own network.

Who it is for

Platform engineers, SREs, and developers responsible for production operations, who need agent work to be governed, auditable, and measurable.

What teams use it for

Komodor packages its operational expertise as modules, in three families. A module holds the workflows and specialist agents for one domain; you enable it per account.

Family	Modules	What it does
AI SRE	Incident management & troubleshooting · Alert Intelligence · Proactive reliability optimization	Detect, investigate, and remediate production incidents; classify which monitors justify paging; convert error budgets and recurring failures into concrete work.
Cost Optimization	Kubernetes Cost · Cloud Cost · Observability Cost	Attribute Kubernetes spend to the teams that cause it; catch cloud billing anomalies; find monitoring spend that buys nothing.
AI Software Operations	Change Intelligence & Risk Control · Production Readiness & Standards · CI/CD Health & Remediation	Decide whether a shipped change is good and roll it back if not; score services against production standards; keep the merge path trustworthy.

Where no module covers the work, you build the agent yourself with the SDK and govern it through the same identity, evidence, and policy model. See Build from scratch.

What you get


Agents that already know your stack	The catalog is Komodor-built and validated agents for Kubernetes, AWS, Azure, Google Cloud, Datadog, Grafana and GitHub: investigators, remediators, code reviewers, a cost analyzer. Deploy one in a couple of minutes; it arrives with its own identity, permissions, and run history.
Expertise, not just a runtime	Modules package how experienced SREs work a domain as ready workflows: an incident detected, grouped, investigated and remediated; alerts sorted by whether they justify paging; Kubernetes spend attributed to the teams causing it; a bad change caught and rolled back. You enable the module; the workflows run.
Agents that act on production, safely	Agents do not only read. They fix a live resource, open the pull request, roll back the deploy. A risky action pauses for a human with the evidence to decide; guardrails block or redact; every step lands in the audit log.
Proof for every run	Every run records what the agent was asked, which tools it called, how it reasoned, what it concluded, and what it cost. Grade that against your own criteria, compare models on the same work, and see spend per agent and per team.
Your own agents, same guarantees	Where no catalog agent fits, write one with the SDK or import one you already run. It gets the same identity, evidence, approvals and audit trail as Komodor’s. Nothing is bolted on afterwards.

Where the agents run and where the control plane runs are separate choices. See Deployment methods.

How you drive it

Interface	Use it to	Who reaches for it
Web console	Build agents, watch runs, operate modules, manage access	Everyone; the primary surface
Slack	Invoke agents and receive results where the team already works	On-call and responders
REST API	Automate anything the console does	Platform engineers, CI, internal tooling
MCP server	Let a coding assistant or another agent inspect the account and invoke agents	Claude Code, Cursor, Codex
MCP Gateway	Expose your tools to agents	Platform engineers

The programmatic surfaces are covered in Developer tools; Slack in Channels.

Give your AI agent the full context

Download all published documentation as a single Markdown file to give your AI agent context about Komodor’s platform, features, and workflows. Each download includes the latest published pages.

Download docs for AI (.md)

Where to go next

Quickstart

Onboarding

The six steps that connect an account to your systems, your model, your alerts, and your team.

Deployment methods

Where agents run, where the control plane runs, and what leaves your network.

Concepts & glossary

The objects and vocabulary the rest of this documentation uses.

​Who it is for

​What teams use it for

​What you get

​How you drive it

​Give your AI agent the full context