Skip to main content
The catalog holds Komodor-built agents that you deploy as-is, supply credentials for, and run. This section is the reference for each one: what it reads, what to connect before deploying it, how to ask it for something useful, and the boundary it will not cross. For browsing the catalog and walking the deploy wizard, see Use specialized agents. Agents are grouped by domain, and every agent is written to the same seven sections — Overview, Tools supported, Scenario examples, Prerequisites, As part of a workflow, Limitations and Recommended model — so two agents can be compared side by side, whether or not they share a page.
The catalog is curated per account, so the entries you see in your own console are the authoritative list. An agent documented here may not be offered to your account, and the console is the place to check.

​
Choosing one

Start from the system that already holds your evidence. An investigator is only as useful as the data it can reach, so the shortest path from deploy to a useful run is the one pointed at a system you already operate.

​
The domains

Cloud providers

AWS, Azure and Google Cloud — one read-only investigator each.

APM

Datadog and Grafana, across traces, logs, metrics and profiles.

Kubernetes

One resource, one cluster with GPU signals, or every cluster Komodor covers.

Code Review

Reviewing pull requests, and locating a problem in the code.

Orchestrator

Agents that route work to other agents rather than doing it.

Remediation

Deciding what to do, and — separately — carrying it out.

​
What every catalog agent has in common

A few facts hold for all of them, so the individual pages do not repeat them.
A time budget bounds how long one run may take. It does not cap what a run costs — the Komodor Agentic Operation Platform (KAOP) reports spend per run rather than refusing an expensive one. See Agent spend attribution.

​
Next steps

Use specialized agents

Browse the catalog and walk the deploy wizard.

Integrations list

Connect what an agent needs before you deploy it.

Modules & workflows

Bind these agents to workflow steps instead of running them one at a time.