# Komodor - KAOP

- [Overview](https://docs.komodor.com/get-started/overview.md): What the Komodor Agentic Operation Platform is, who it is for, what teams use it for, and where to start.
- [Quickstart](https://docs.komodor.com/get-started/quickstart.md): Sign in, get a first run out of the built-in assistant, deploy one catalog agent and run it, and read the evidence every run records, in about ten minutes.
- [Onboarding](https://docs.komodor.com/get-started/onboarding.md): The six steps that take an account from a first run to agents working against your systems, your model, your alerts, and your team.
- [Deployment methods](https://docs.komodor.com/get-started/deployment-methods.md): Where your agents run, where the control plane runs, and how to choose.
- [Concepts & glossary](https://docs.komodor.com/get-started/concepts.md): The terms you will meet in the console, the API, and the rest of this documentation, each defined once.
- [Architecture](https://docs.komodor.com/get-started/architecture.md): How the control plane, your agents, and the evidence trail fit together, and the boundaries you can rely on.
- [How it works](https://docs.komodor.com/manage-your-agents/build/how-it-works.md): What building an agent involves in KAOP — the two authoring paths, and everything you attach to an agent before it runs.
- [Import an existing agent](https://docs.komodor.com/manage-your-agents/build/import-an-agent.md): Connect an agent you already run — Google ADK, LangChain, Claude Agent SDK or Agno — by generating the wrapper that registers it and reports its evidence.
- [Use specialized agents](https://docs.komodor.com/manage-your-agents/build/use-specialized-agents.md): Deploy a Komodor-built specialized agent from the catalog — validated, ready to run, and live in minutes without writing code.
- [Agent catalog](https://docs.komodor.com/manage-your-agents/build/catalog/overview.md): Reference for every Komodor-built agent you can deploy from the catalog — what each one reads, what it costs in time, and where it stops.
- [Cloud providers](https://docs.komodor.com/manage-your-agents/build/catalog/cloud-providers.md): The read-only investigators for AWS, Azure and Google Cloud — what each reads, what to connect, what to ask it, and where each stops.
- [APM](https://docs.komodor.com/manage-your-agents/build/catalog/apm.md): The read-only investigators for Datadog and Grafana — what each reads, the paths to reach it, what to ask it, and where each stops.
- [Kubernetes](https://docs.komodor.com/manage-your-agents/build/catalog/kubernetes.md): Three catalog agents for Kubernetes — one resource, one cluster with telemetry and GPU signals, or a question across every cluster Komodor covers.
- [Code Review](https://docs.komodor.com/manage-your-agents/build/catalog/code-review.md): Code Reviewer reviews pull requests. GitHub Agent locates a problem in a repository and, once a person approves, opens a pull request for a configuration fix.
- [Orchestrator](https://docs.komodor.com/manage-your-agents/build/catalog/orchestrator.md): The catalog agent that routes work to other agents — running a declarative workflow over your fleet, or executing one orchestrated step of a module workflow.
- [Remediation](https://docs.komodor.com/manage-your-agents/build/catalog/remediation.md): Reads a finished investigation and returns a typed decision — propose a fix, decide no action is warranted, or ask the questions that would settle it.
- [Remediation Executor](https://docs.komodor.com/manage-your-agents/build/catalog/remediation-executor.md): Carries a finished investigation into action — briefing Klaudia to fix the live resource, or opening the pull request that fixes the source.
- [AWS Cost Analyzer](https://docs.komodor.com/manage-your-agents/build/catalog/aws-cost-analyzer.md): Scans a connected AWS account for waste across six use cases and reports findings ranked by estimated monthly impact, each with its evidence.
- [Integrations overview](https://docs.komodor.com/manage-your-agents/build/integrations-overview.md): The two ways an agent reaches anything external — the built-in integration catalog or the MCP Gateway — and how to choose between them.
- [Integrations list](https://docs.komodor.com/manage-your-agents/build/built-in-integrations.md): The catalog of ready-made connections — cloud, observability, source control, ticketing, chat — with the credentials each needs and how to test one.
- [Integration groups](https://docs.komodor.com/manage-your-agents/build/integration-groups.md): Bundle your connected tool servers into a named group, narrow which tools it grants, and attach the whole set to an agent in one move.
- [Knowledge base](https://docs.komodor.com/manage-your-agents/build/knowledge-base.md): Give agents your runbooks, postmortems, and service docs as a searchable source they retrieve from and cite during a run.
- [Memory](https://docs.komodor.com/manage-your-agents/build/memory.md): What an agent learned in one run and wrote down for its future self — reviewed before it is published, and searchable by the agents you bind to it.
- [Skills](https://docs.komodor.com/manage-your-agents/build/skills.md): Package your runbooks and procedures as reusable, versioned skills, attach them to any agent, and see which ones a run actually used.
- [Triggers & schedules](https://docs.komodor.com/manage-your-agents/build/triggers-schedules.md): Run an agent on a recurring cron schedule from the trigger registry — and where inbound webhook endpoints live instead.
- [How Run works](https://docs.komodor.com/manage-your-agents/run/how-it-works.md): Every way work reaches an agent, what one execution records, and where to look when you need to know what happened.
- [Chat & history](https://docs.komodor.com/manage-your-agents/run/chat-history.md): Work conversationally with your agents in resumable sessions, and read every run and chat in one ledger.
- [Runs & evidence](https://docs.komodor.com/manage-your-agents/run/runs-evidence.md): Every execution is a run with a full evidence trail — inputs, tool calls, reasoning, output, and cost. Here is how to read it.
- [Outbound webhooks](https://docs.komodor.com/manage-your-agents/run/outbound-webhooks.md): Have KAOP post signed, retried, auditable events to your own endpoints so external systems react to what your agents do.
- [Channels](https://docs.komodor.com/manage-your-agents/run/channels.md): Connect Slack so your team starts agents, workflows, and incident pipelines from the conversation they are already having.
- [Attention](https://docs.komodor.com/manage-your-agents/run/attention.md): The operator inbox — held calls waiting on approval, parked selections waiting on a choice, and runs that stopped and need a look.
- [Optimize — how it works](https://docs.komodor.com/manage-your-agents/optimize/how-it-works.md): The four lenses on a running fleet — reliability, quality, cost, and portability — and which surface answers each.
- [Fleet health](https://docs.komodor.com/manage-your-agents/optimize/fleet-health.md): Read the whole agent fleet at a glance — what is online, what went quiet, what is failing, and what changed.
- [Insights](https://docs.komodor.com/manage-your-agents/optimize/insights.md): Failures across your agents, grouped and ranked, each with the evidence behind it and an agent-produced next step.
- [Evaluations](https://docs.komodor.com/manage-your-agents/optimize/evaluations.md): Grade agent runs with LLM judges against explicit rubrics, and read exactly why a score is what it is.
- [Model Evaluation](https://docs.komodor.com/manage-your-agents/optimize/model-evaluation.md): Run a candidate agent or model beside production on real traffic and let a blinded judge say which one is better.
- [Agent spend attribution](https://docs.komodor.com/manage-your-agents/optimize/agent-spend-attribution.md): What the fleet costs per run, agent, and model — how each figure is derived, and how to cap spend with budgets.
- [Observability & OTel export](https://docs.komodor.com/manage-your-agents/optimize/observability-otel-export.md): Export agent traces, logs, and metrics over OpenTelemetry so agent activity sits beside the rest of your systems.
- [Modules & workflows](https://docs.komodor.com/modules-and-workflows/overview.md): A module is an operational outcome you own; the workflows inside it are the automation that delivers it.
- [Incident management & troubleshooting](https://docs.komodor.com/modules-and-workflows/sre/incidents.md): Detect, group, investigate, remediate, and learn from production incidents — with the evidence behind every conclusion.
- [Alert Intelligence](https://docs.komodor.com/modules-and-workflows/sre/alert-hygiene.md): Classify which monitors are worth waking someone for, and propose the threshold, dedupe, and suppression fixes that quiet the rest.
- [Proactive reliability optimization](https://docs.komodor.com/modules-and-workflows/sre/reliability-optimization.md): Turn indicators, error budgets, and recurring failure patterns into concrete reliability improvements — including the agent that eliminates the recurrence.
- [Kubernetes Cost](https://docs.komodor.com/modules-and-workflows/cost-optimization/k8s-cost.md): Attribute Kubernetes spend by cluster, namespace and workload, and cut waste with policy-driven right-sizing and pod placement.
- [Cloud Cost](https://docs.komodor.com/modules-and-workflows/cost-optimization/cloud-optimization.md): Track cloud vendor spend, catch the anomaly the week it happens, and convert waste into remediation actions with an owner attached.
- [Observability Cost](https://docs.komodor.com/modules-and-workflows/cost-optimization/observability-optimization.md): Find the observability spend that buys nothing — high-cardinality metrics, unread logs, unused dashboards — with an agent configured to manage that provider.
- [Change Intelligence & Risk Control](https://docs.komodor.com/modules-and-workflows/ops-automation/change-intelligence.md): Decide whether the change that just shipped is good — and undo it if not — with a verdict backed by the signals inside its blast radius.
- [Production Readiness & Standards](https://docs.komodor.com/modules-and-workflows/ops-automation/production-readiness.md): Score services and release candidates against production standards, block unsafe releases, and manage evidence-backed waivers.
- [CI/CD Health & Remediation](https://docs.komodor.com/modules-and-workflows/ops-automation/ci-cd-pipeline-health.md): Keep the merge path trustworthy — flaky stages quarantined, queue time cut, and a broken delivery stage caught before it blocks everyone.
- [How it works](https://docs.komodor.com/security-and-governance/how-it-works.md): The six layers that decide what an agent may do — identity, permissions, standards, runtime guardrails, approvals, and the record of every decision.
- [Signing in](https://docs.komodor.com/security-and-governance/identity-and-access/signing-in.md): How people authenticate through your identity provider, how a session behaves, and how someone comes to belong to an account.
- [Accounts & members](https://docs.komodor.com/security-and-governance/identity-and-access/accounts-members.md): The account as an isolation boundary, belonging to several at once, and how to invite, suspend, and restore the people in one.
- [Roles & permissions](https://docs.komodor.com/security-and-governance/identity-and-access/roles-permissions.md): How KAOP combines capabilities, policies, roles, and resource scopes into default-deny access.
- [API keys](https://docs.komodor.com/security-and-governance/identity-and-access/api-keys.md): Create, use, and revoke KAOP bearer tokens, and choose whether each key acts as a service account or as you.
- [Service accounts](https://docs.komodor.com/security-and-governance/identity-and-access/service-accounts.md): Create durable non-human identities for automation, with independent roles, attributes, and API keys.
- [Agent identity](https://docs.komodor.com/security-and-governance/identity-and-access/agent-identity.md): How KAOP gives every agent its own governed identity, permissions, and revocable worker token.
- [Access explorer](https://docs.komodor.com/security-and-governance/identity-and-access/access-explorer.md): Ask what an identity can actually do, and test one action against one resource, before you grant or revoke anything.
- [Configuration clusters](https://docs.komodor.com/security-and-governance/identity-and-access/configuration-clusters.md): Declare KAOP resources from Kubernetes manifests and understand cluster ownership, reconciliation, and edit behavior.
- [Declaring resources](https://docs.komodor.com/security-and-governance/identity-and-access/declaring-resources.md): Declare KAOP resources as Kubernetes custom resources, read their status, and understand how deletion and secrets work.
- [Credentials & secrets](https://docs.komodor.com/security-and-governance/identity-and-access/credentials-secrets.md): Store encrypted credentials, bind them to specific agents, and control how their values are delivered and replaced.
- [Standards & Guardrails](https://docs.komodor.com/security-and-governance/controls/standards-guardrails.md): The standards every new agent inherits, and the rules that block, hold, redact, or record an action at the boundary.
- [Approvals](https://docs.komodor.com/security-and-governance/controls/approvals.md): A consequential action gets a person's decision, with the evidence needed to make it — and the decision becomes part of the run's record.
- [Audit log](https://docs.komodor.com/security-and-governance/controls/audit-log.md): An append-only record of every governed change and an explicit set of sensitive reads.
- [Agent isolation & tenancy](https://docs.komodor.com/security-and-governance/architecture-considerations/agent-isolation-tenancy.md): How KAOP binds requests to one account and limits every agent to its own identity, permissions, and credentials.
- [Secrets & credential handling](https://docs.komodor.com/security-and-governance/architecture-considerations/secrets-credential-handling.md): How a stored secret reaches the run that needs it without being exposed to a browser, a deploy, a log, or another agent.
- [Data handling & redaction](https://docs.komodor.com/security-and-governance/architecture-considerations/data-handling-redaction.md): What agents can see, what KAOP masks automatically, and how to control what reaches models, tools, and run records.
- [Data retention, deletion & export](https://docs.komodor.com/security-and-governance/architecture-considerations/data-retention-deletion-export.md): What KAOP keeps as operating history, what archive and deletion mean, and how to request an account-level export or deletion.
- [Network & egress control](https://docs.komodor.com/security-and-governance/architecture-considerations/network-egress-control.md): A worker dials out and nothing dials in — and what an agent can reach on the way out is decided by its tool surface, not by its network.
- [MCP Gateway](https://docs.komodor.com/security-and-governance/architecture-considerations/mcp-gateway.md): Expose your own tools to agents — an MCP server you run, or an OpenAPI document that becomes tools — governed by gateway policy.
- [Outposts](https://docs.komodor.com/security-and-governance/architecture-considerations/outposts.md): A small relay you run inside your own network so agents can reach private services — outbound only, deny-by-default, with no inbound hole to open.
- [Providers](https://docs.komodor.com/security-and-governance/architecture-considerations/providers.md): The models your fleet can call — through Komodor-managed access, your provider keys, or a gateway that stays in your environment.
- [Overview](https://docs.komodor.com/developer-tools/overview.md): The three programmatic surfaces — REST API, MCP server, and a coding-agent connection — and which one to reach for.
- [APIs](https://docs.komodor.com/developer-tools/apis.md): The REST API behind the console — base URL, bearer authentication, error and pagination conventions, and the interactive reference.
- [MCP server](https://docs.komodor.com/developer-tools/mcp-server.md): The platform's own capabilities as MCP tools — grouped into toolsets, scopable per connection, and authorized exactly like the API.
- [Connect coding agents](https://docs.komodor.com/developer-tools/connect-coding-agents.md): Wire Claude Code, Codex CLI, or Cursor to your account over MCP.
- [Troubleshooting](https://docs.komodor.com/reference/troubleshooting.md): Find help with agent connectivity, authentication, credentials, integrations, triggers, and runs.
- [Limits & quotas](https://docs.komodor.com/reference/limits-quotas.md): The caps, sizes, timeouts, and page limits KAOP enforces — what each one is, and what happens when you reach it.
- [What's new](https://docs.komodor.com/reference/changelog.md): The latest features, improvements, and fixes in KAOP.
- [Support](https://docs.komodor.com/reference/support.md): How to get help with KAOP — who to contact, what to include in a report, and the resources that resolve common issues.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.