Which models can I use?

Bring your own keys: Anthropic, OpenAI or local models. Or run on Kortix compute. Add your keys with kortix providers.

Can I self-host Kortix?

Yes. Run the exact same stack on a laptop, a VPS or your own VPC with kortix self-host.

Where do my tool credentials live?

Connector credentials stay server-side and never reach the sandbox. Agents reach connectors through one scoped Kortix token.

Can agents use the CLI themselves?

Yes. The same Kortix CLI runs inside every sandbox, pre-authenticated, so agents use the exact commands you do.

How do runs stay isolated?

Every session runs in its own sandbox on its own git branch. Nothing is shared between runs.

Get started

One kortix.yaml.Your AI workforce, as code.

Agents, skills, tools, connectors and schedules are files in a repo. Edit them in your IDE, ship them with one command.

$ curl -fsSL https://kortix.com/install | bash

Read the docs

kortix_version: 2
default_agent: support-triage

project:
  name: acme-ops

agents:
  support-triage:
    file: agents/support-triage.md
    connectors: [slack, linear]

connectors:
  - slug: slack
    provider: composio
    app: slack
  - slug: linear
    provider: composio
    app: linear

triggers:
  - slug: daily-triage
    type: cron
    agent: support-triage
    cron: "0 0 8 * * *"
    prompt: "Triage new support tickets and flag the urgent ones."

Agents are sandboxes.

Work is code.

You own the stack.

Every agent runs in its own disposable cloud VM, on its own git branch. Spin up thousands in parallel. Nothing is shared between runs.

Sandbox bootsruntime + your repo
Agent workson branch session/1f3a
Change requestyou review the diff
Merged to mainsandbox thrown away

Agents are sandboxes.

Every agent runs in its own disposable cloud VM, on its own git branch. Spin up thousands in parallel. Nothing is shared between runs.

Sandbox bootsruntime + your repo
Agent workson branch session/1f3a
Change requestyou review the diff
Merged to mainsandbox thrown away

Work is code.

Agents, skills, triggers, connectors and policies are plain files in one repo. Diff them, review them in a change request, roll them back.

agents/support-triage.md+1−1

  ---- model: anthropic/claude-opus-4-8+ model: openai/gpt-5  tools:    lookup_order: true

You own the stack.

Open source. Self-host the exact same stack, bring your own runtime and model keys. No black box, no lock-in.

Write it like code. Run it like a fleet.

Agents live in your repo as files. Kortix runs each session in its own sandbox.

One line to start.
kortix init adds kortix.yaml, agents/ and skills/ to your repo.
Agents are markdown.
A persona, a model and its tools in one file you can review.
Ship with one command.
kortix ship pushes, builds the sandbox and asks for missing secrets.
A sandbox per session.
Every session runs in its own cloud VM, on its own branch.
Every change is a diff.
Agents work on branches. You review and merge.
Your model. Your choice.
Pick the model per agent, or bring your own coding agent.

1 session = 1 sandbox = 1 branch.

Every session runs in its own isolated sandbox on its own branch off main. Run them in parallel; nothing is shared.

1f3a · triage 14 tickets9b22 · build board deck4e07 · draft outreach

mainreview → merge → main

One binary.The whole lifecycle.

16 matches

Click a command to copy itRead docs

The same binary is pre-authenticated inside every sandbox, so agents use it too.

Your computer

Slack

GitHub

Stripe

Linear

Notion

+ any MCP server

Every tool,behind one interface.

3,000+ apps, plus any MCP, OpenAPI, GraphQL or raw HTTP endpoint, behind one Connector interface your agents call.

Only a scoped token leaves the boxKORTIX_TOKEN
Declared once in kortix.yamlconnectors:
Managed from the terminalkortix connectors

Questions, answered.

Run your whole company from one repo you own.

Start with one job and grow from there.

Get started

One kortix.yaml.Your AI workforce, as code.

Agents, skills, tools, connectors and schedules are files in a repo. Edit them in your IDE, ship them with one command.

$ curl -fsSL https://kortix.com/install | bash

Read the docs

kortix_version: 2
default_agent: support-triage

project:
  name: acme-ops

agents:
  support-triage:
    file: agents/support-triage.md
    connectors: [slack, linear]

connectors:
  - slug: slack
    provider: composio
    app: slack
  - slug: linear
    provider: composio
    app: linear

triggers:
  - slug: daily-triage
    type: cron
    agent: support-triage
    cron: "0 0 8 * * *"
    prompt: "Triage new support tickets and flag the urgent ones."

Agents are sandboxes.

Work is code.

You own the stack.

Every agent runs in its own disposable cloud VM, on its own git branch. Spin up thousands in parallel. Nothing is shared between runs.

Sandbox bootsruntime + your repo
Agent workson branch session/1f3a
Change requestyou review the diff
Merged to mainsandbox thrown away

Agents are sandboxes.

Every agent runs in its own disposable cloud VM, on its own git branch. Spin up thousands in parallel. Nothing is shared between runs.

Sandbox bootsruntime + your repo
Agent workson branch session/1f3a
Change requestyou review the diff
Merged to mainsandbox thrown away

Work is code.

Agents, skills, triggers, connectors and policies are plain files in one repo. Diff them, review them in a change request, roll them back.

agents/support-triage.md+1−1

  ---- model: anthropic/claude-opus-4-8+ model: openai/gpt-5  tools:    lookup_order: true

You own the stack.

Open source. Self-host the exact same stack, bring your own runtime and model keys. No black box, no lock-in.

Write it like code. Run it like a fleet.

Agents live in your repo as files. Kortix runs each session in its own sandbox.

One line to start.
kortix init adds kortix.yaml, agents/ and skills/ to your repo.
Agents are markdown.
A persona, a model and its tools in one file you can review.
Ship with one command.
kortix ship pushes, builds the sandbox and asks for missing secrets.
A sandbox per session.
Every session runs in its own cloud VM, on its own branch.
Every change is a diff.
Agents work on branches. You review and merge.
Your model. Your choice.
Pick the model per agent, or bring your own coding agent.

1 session = 1 sandbox = 1 branch.

Every session runs in its own isolated sandbox on its own branch off main. Run them in parallel; nothing is shared.

1f3a · triage 14 tickets9b22 · build board deck4e07 · draft outreach

mainreview → merge → main

One binary.The whole lifecycle.

16 matches

Click a command to copy itRead docs

The same binary is pre-authenticated inside every sandbox, so agents use it too.

Your computer

Slack

GitHub

Stripe

Linear

Notion

+ any MCP server

Every tool,behind one interface.

3,000+ apps, plus any MCP, OpenAPI, GraphQL or raw HTTP endpoint, behind one Connector interface your agents call.

Only a scoped token leaves the boxKORTIX_TOKEN
Declared once in kortix.yamlconnectors:
Managed from the terminalkortix connectors

Questions, answered.

Run your whole company from one repo you own.

Start with one job and grow from there.

Get started

One kortix.yaml.Your AI workforce, as code.

Agents are sandboxes.

Work is code.

You own the stack.

Agents are sandboxes.

Work is code.

You own the stack.

Write it like code. Run it like a fleet.

One line to start.

Agents are markdown.

Ship with one command.

A sandbox per session.

Every change is a diff.

Your model. Your choice.

1 session = 1 sandbox = 1 branch.

One binary.The whole lifecycle.

Every tool,behind one interface.

Questions, answered.

Which models can I use?

Can I self-host Kortix?

Where do my tool credentials live?

Can agents use the CLI themselves?

How do runs stay isolated?

Run your whole company from one repo you own.

One kortix.yaml.Your AI workforce, as code.

Agents are sandboxes.

Work is code.

You own the stack.

Agents are sandboxes.

Work is code.

You own the stack.

Write it like code. Run it like a fleet.

One line to start.

Agents are markdown.

Ship with one command.

A sandbox per session.

Every change is a diff.

Your model. Your choice.

1 session = 1 sandbox = 1 branch.

One binary.The whole lifecycle.

Every tool,behind one interface.

Questions, answered.

Which models can I use?

Can I self-host Kortix?

Where do my tool credentials live?

Can agents use the CLI themselves?

How do runs stay isolated?

Run your whole company from one repo you own.