What it is
KAOP manages four things for every agent it runs:
Workers run either on Komodor’s infrastructure or in your own environment, against a control plane
Komodor operates — or, in Beta, one you run yourself. See
Deployment methods.
Who it is for
Platform engineers, SREs, and developers responsible for production operations, who need agent work to be governed, auditable, and measurable. It assumes working knowledge of the systems the agents will operate on — Kubernetes, cloud infrastructure, CI/CD, and observability tooling — and of the access model your organization applies to them.What teams use it for
Operational outcomes ship as modules, in three families. Each module contains workflows you enable per account.
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.
Where to go next
Onboarding
The checklist that takes a new account from empty to a working agent.
Concepts & glossary
The objects and vocabulary the rest of this documentation uses.
Build your first agent
Create an agent, run it, and read its evidence.
Architecture
How the control plane and agents communicate.