Onboarding

The Quickstart proves the loop on a fresh Komodor Agentic Operation Platform (KAOP) account. The six steps below connect it to your systems, your model, your alerts, and your team. They are ordered by dependency: an agent needs something to reach before it is worth creating, and a workflow needs agents to bind to. You act inside one account at a time. If you belong to more than one, use the account switcher at the foot of the sidebar. Anything your role does not grant appears locked. See Accounts & members.

​

1. Connect your systems

An agent that cannot see your systems cannot do operations work. Connect Datadog, AWS, GitHub, Kubernetes, Slack and the rest from the catalog, or expose your own tools through the MCP Gateway. Both paths keep credentials away from the agent. See Integrations overview.

​

2. Connect a model provider

Agents call models through KAOP, never with a provider key of their own. Register your provider account and the models on it, or use the models Komodor manages for your account; an agent can be pointed at either. See Providers.

​

3. Create your agents

There are three ways to create one: Start from catalog to deploy a Komodor-built agent, Build from scratch to author a worker with the SDK, or Import to bring in an agent that already exists. Whichever you choose, the agent gets its own identity, permissions, and run history. See How building works.

​

4. Create an endpoint for alerts and CI to post to

An endpoint is an inbound URL an external system posts to in order to start work: an alerting tool, a CI job, a webhook from your own service. Create one under Integrations → Endpoints; the requests it receives start runs with their origin recorded. See Triggers & schedules.

​

5. Chain agents into a workflow

Most operations work is too big for one agent. A workflow is an ordered set of steps, each delivering a task to one or more agents. One step correlates alerts, the next investigates, the next proposes a remediation. See Orchestrator.

​

6. Connect Slack

A channel puts agents where the team already works. Connect Slack and people invoke agents from a channel and get results in the thread; routing rules decide what each inbound message targets: an agent, a workflow, or an incident pipeline. See Channels.

​

Next steps