Concepts & glossary - Komodor

Every piece of work an agent does in the Komodor Agentic Operation Platform (KAOP), whether it investigates an alert, reviews a pull request, or answers a question in Slack, is recorded as a run. The sections below follow one run from start to finish and define each term where it first appears.

Architecture diagram. A trigger, workflow step, chat or module starts an Agent. The agent runs as a Worker, which produces a Run plus evidence, which is graded by Evaluations. The agent also uses Integrations and the MCP Gateway, reads a Knowledge base, and follows Skills.

One run, and the terms around it.

What starts a run

A run begins when something asks an agent to work. That can be a person, a schedule, an external system, or a message in Slack.

Term	What it means	Read more
Manual	A person or a system starts the run directly, from the console, a chat message, or the API.
Endpoint	An inbound URL you create under Integrations → Endpoints. An external system posts to it and the run starts. This is how alerting and CI tools drive agents.	Triggers & schedules
Trigger	A recurring cron schedule, and the only thing the product calls a trigger.	Triggers & schedules
Channel	A messaging surface, Slack today, where people invoke agents and get results in the thread. Routing rules decide what each message starts.	Channels

A workflow step, a module, or another agent can also start a run.

The agent

The agent is what you build and configure. It carries its instructions, the tools it may use, and the knowledge you give it. When it runs, a process called a worker does the executing.

Term	What it means	Read more
Agent	The thing you create, name, deploy and grant access to: its instructions, the tools it may reach, the permissions it holds, and its history. An agent is a principal: KAOP authorizes its actions the same way it authorizes a person’s.	How building works
Worker	The process that runs an agent. One worker runs one agent. You configure and inspect the agent; you look at the worker when one is offline or on the wrong version.	Fleet health
Skill	A reusable unit of know-how (a runbook, a procedure, a pattern) attached to an agent. Skills tell it how to work.	Skills
Knowledge base	Documents you upload, indexed so agents can search them at run time and cite what they used. Knowledge tells an agent what you know. Nothing is ingested automatically.	Knowledge base
Memory	What an agent carries forward between runs, so a later run finds what an earlier one worked out instead of re-deriving it. Memory tells it what it has already learned. Writes are reviewed before a later run can read them.	Memory

What the agent reaches

To do anything useful, an agent needs access to your systems. Every connection is one of two kinds, and in both the credentials stay with the platform, never with the agent.

Term	What it means	Read more
Built-in integration	A system from the catalog, such as Datadog, AWS, Azure, GitHub, Slack, Kubernetes or PagerDuty, connected once and shared by the agents you allow.	Built-in integrations
MCP Gateway	Your own tool surface, any MCP server or OpenAPI endpoint, exposed to agents as tools, with the gateway holding the credentials.	MCP Gateway
Integration group	A named bundle of integrations you attach to an agent as a set.	Integration groups
Credential	A stored secret, encrypted at rest, bound to the agents allowed to use it, and delivered to a run without its value ever appearing to you or in the agent’s logs.	Credentials & secrets
Outbound webhook	The reverse direction: KAOP posting events (a run finished, an incident was triaged) to an endpoint you own, signed and retried.	Outbound webhooks

What the run leaves behind

When the run finishes you have a complete record of it, and the means to judge whether it was any good and what it cost.

Term	What it means	Read more
Run	One execution of an agent, with everything it did: the input, each tool call, the reasoning, the output, and the cost. The unit you open to find out what happened.	Runs & evidence
Evidence	That record. It is what every term below measures.	Runs & evidence
Evaluation	Grading a run against explicit criteria. A judge (an LLM or agent) applies a rubric (the named criteria) and returns a verdict with per-criterion reasoning. A verdict is itself a run you can open.	Evaluations
Golden scenario	A fixed input with a known-good result, kept as a regression test for an agent’s behavior.	Evaluations
Model evaluation	Comparing models on the same work, to decide which one an agent should use. Shadow runs a candidate alongside the live agent without serving its output.	Model evaluation
Fleet health	The operational state of every agent you run: online, failing, drifting, idle.	Fleet health
Agent spend	What each agent costs, per agent and per run, with budgets that can stop an agent at a cap.	Agent spend

Workflows and modules

Most operations work takes more than one agent, and it has a shape: first correlate the alerts, then investigate, then propose a fix, then ask a person before applying it. A workflow is that sequence of steps, with agents assigned to each. A module packages Komodor’s expertise in one operational domain, such as incident management or Kubernetes cost, as the workflows and specialist agents for that domain. You enable a module; its workflows do the work. For example, the module Incident management & troubleshooting contains the workflow Production Alert Investigation. That workflow has four steps: source, dedupe and correlate, investigation, remediation. The investigation step is handled by the Datadog, Kubernetes and AWS investigators; the remediation step proposes a fix and waits for a person to approve it. When you open a module you see its workflows; when you open a workflow you see its steps and which agents handle each.

Term	What it means	Read more
Module	Komodor’s expertise in one operational domain, such as “Incident management & troubleshooting” or “Kubernetes Cost”, packaged as workflows and the specialist agents they use. You enable it for your account. It answers which domain is this?; its workflows answer how does the work get done?	Modules & workflows
Workflow	A sequence of steps inside a module that carries out one piece of that domain’s work. The steps are fixed by the workflow’s template; you choose which agents handle each step.	Orchestrator
Step	One named task in a workflow, with a goal, an input, and an output. A step is carried out by the agents assigned to it, by KAOP itself with no model involved, or by a person choosing between options.
Orchestrator	The catalog agent that works a step through the agents assigned to it, so several specialists can contribute to one task.	Orchestrator

Who may do what

Everything above happens inside an account, under permissions that apply to people and agents alike.

Term	What it means	Read more
Account	The tenant boundary: its members, agents, and data. Everything belongs to exactly one, and you act in one at a time.	Accounts & members
Member	A person with access to an account. One person can belong to several.	Accounts & members
Role	A bundle of permissions assigned to a member, a service account, or an agent.	Roles & permissions
Service account	A non-human identity for automation, with its own grants and API keys.	Service accounts
API key	A credential that authenticates a person or a service account to the API.	API keys
Agent identity	The principal an agent authenticates as, separate from whoever deployed it.	Agent identity
Guardrail	A rule evaluated at a gate that blocks an action, holds it for approval, redacts a matched value, or records it.	Standards & guardrails
Approval	A risky action paused for a human decision, with the evidence needed to make it.	Approvals
Audit log	The append-only record of sensitive actions and access decisions.	Audit log
Access explorer	Who, or which agent, can reach a given resource, and by which grant.	Access explorer
Configuration cluster	Configuration managed as code and applied to the platform, rather than edited in the console.	Configuration clusters

Next steps

Architecture

How the control plane, SDK and workers fit together.

Modules & workflows

The module catalog, and how modules contain workflows.

Build an agent

Author your own or deploy one from the catalog.

Runs & evidence

What a run records and how to read it.

​What starts a run

​The agent

​What the agent reaches

​What the run leaves behind

​Workflows and modules

​Who may do what

​Next steps