The Autonomous Company Operating System

The AI command center for a workforce of agents.

Your whole company. One repo you own.

Every agent, skill, connector, and memory is a file — 3,000+ tools connected, one versioned source of truth, scoped so each person and agent has exactly the right access.

Projects

Each project is a repo your agents run from — scaffolded with kortix init, deployed with kortix ship.

No projects yet
Run kortix init in your terminal to scaffold one.
Everything is code you own

Your whole company, as files.

Kortix treats your company as a Git repo. Every agent, skill, connector, policy, and memory is a file your whole company shares — one config, one source of truth, so everyone works from the same agents and skills, and the company's memory compounds in one place instead of scattering. grep it, diff it, own it outright.

acme — company OS
main
kortix.toml
[project]
name = "acme"
[[connectors]] # 3,000+ apps, one scoped token
slug = "slack"
[[agents]]
name = "go-to-market"
connectors = ["slack", "hubspot", "gmail"]
[[triggers]] # runs in a loop, in the night
slug = "morning-brief"
cron = "0 8 * * 1-5"
[[channels]] # delivered where people work
slug = "slack"

A skill for every job

How your company does the work, written down once and reused everywhere.

Agents live with their context

Every agent is a file in the same repo as the skills it needs.

Shared by the whole company

One config everyone works from — not twelve SaaS tools each holding a slice.

Memory that compounds

Every reviewed change lands in main, so skills and context grow instead of getting lost.

From a request to finished work.

Connect your tools, ask for the outcome, and review what comes back. The best workflows become reusable skills, and the company's memory compounds — for everyone.

Connect

Connect your tools once.

Wire up Slack, docs, tickets, CRM, databases, and code with scoped access — once, for the whole company.

  • 3,000+ apps, plus MCP, OpenAPI, GraphQL, and HTTP
  • Credentials stay brokered by Kortix, never copied into a session
  • Scope each tool per project, per agent, per person
  • Admins set what can run, what asks first, and what stays blocked
Models

Models

Bring any provider — routed per session, keys stay in Secrets

Kortix Gateway
Managed routing — injected into every sandbox
Managed
Anthropic
Anthropic
Claude — Opus, Sonnet, Haiku
OpenAI
OpenAI
GPT-5, GPT-4o, o-series
Google
Google
Gemini 2.5 Pro, Flash
Groq
Groq
Fast inference — Llama, Mixtral, Kimi
xAI
xAI
Grok
Connecting a provider writes its API key to Secrets — sessions pick it up at sandbox boot.
Ask

Ask for the outcome.

Anyone on the team describes what they need in plain language — from Slack, Teams, the web, or their phone.

  • No prompt-engineering course before the first useful task
  • Ask for a report, brief, dashboard, reply, app, or change
  • Every surface starts the same underlying kind of work
  • Follow-up messages keep the context instead of starting over
Chat
draft the Monday revenue brief
coworker reading connected tools…
sources: Stripe · HubSpot · Linear · Slack
Work

It works in a safe sandbox.

Each task runs in its own isolated machine with scoped permissions, its own files, and a full audit trail.

  • Every session gets its own isolated sandbox and branch
  • Agents use connected tools without ever holding raw keys
  • Long-running work keeps going after you close the tab
  • Every important action stays logged, reviewable, or approval-gated
Chat
sessions /
Run kortix sessions create to start.
Review

Review what comes back.

Kortix returns finished work — a report, deck, dashboard, app, reply, or a change request you approve.

  • People stay in control before anything important ships
  • Files, diffs, and results open right in the workspace
  • Change requests make every edit auditable before it reaches main
  • Approved work becomes part of the company
Review

Review

See what went in and what came back before you keep it

Input

Draft the Monday revenue brief

Stripe · HubSpot · Linear

Output
Monday revenue brief

MRR, pipeline, and blockers in one doc — ready to share.

ready
Read the output first — nothing ships until you say so.
Skills

Save the workflow as a skill.

The best way to do a job becomes a reusable skill file — so the next person, and every agent, starts from a stronger place.

  • Capture repeatable know-how in simple files
  • Attach skills to the agents that need them
  • Improve them through the same reviewable change flow
  • One person levels up the whole company overnight
Skills

Skills

A good workflow becomes reusable — attached to coworkers, improved by review

Skill library· 3
board-updatenew

Posts the Monday revenue brief to #leadership

ops-coworker·24 runs·reviewed
deal-desk-recap

Summarizes won and lost deals for the sales sync

sales-coworker·12 runs·reviewed
incident-postmortem

Drafts a postmortem from the incident channel

sre-coworker·7 runs·reviewed

One person captures it once — the whole team levels up overnight.

Memory

It learns by itself.

Every session adds to a shared memory — people, docs, decisions, context — so the next one starts smarter. The company gets sharper on its own.

  • Relevant projects, people, and decisions carry forward
  • Agents stop asking the same setup questions twice
  • Memory is shared by everyone and inspectable as files
  • Your company compounds what it learns, every run
MemorySyned 2 minutes ago

Memory

Context Kortix learned from your tools, files, and past sessions

Captured this weekfrom real work
Decision
Revenue brief ships Mondays 9am to #leadership
Blocker
HubSpot deal-stage mapping needs finance sign-off
Workflow
Month-end recon runs the board-update skill
Carries forward
marko · DomQ3 board deckacme-ops

Reused across sessions — every coworker starts from what the team already knows.

How the company runs

One ask. A workforce. One shared brain everyone builds on.

Every request fans out into isolated sessions, each in its own sandbox on its own branch. They work in parallel, then land it back to one shared main through a reviewed change request — so everyone's work and the company's memory compound in one place.

You ask — or a trigger fires
session/outreach
isolated sandbox · own branch
change request
session/pr-review
isolated sandbox · own branch
change request
session/close-month
isolated sandbox · own branch
change request
main · shared by the whole company

Isolated & parallel

Thousands of sessions at once, each walled off in its own microVM sandbox.

Real work, not chat

Agents act on real machines and return finished deliverables, not a paragraph.

Reviewed into main

Durable changes land only through an approved change request you can diff.

Compounds over time

Every reviewed change lands in one shared main, so skills and memory grow instead of scattering.

The AI gap

Your best people have AI superpowers. The rest of your company doesn't.

1%

Your power users

Built the agents and skills that do their work for them — locked in one person's setup, invisible to everyone else.

99%

Everyone else

Not sure what to use, or when. The company never compounds what its best people already figured out.

Kortix takes what your best people build and shares it with everyone — the same agents, skills, and memory, as files your whole company uses.

Open. Self-hostable. Yours down to the metal.

Most AI gives you a toy or a cage. Kortix is neither.

Open source

One of the largest open AI-for-work platforms. Read every line — nothing is a black box.

Any model, your keys

Bring any provider, or the Claude, ChatGPT, or Cursor subscription you already pay for.

Self-host anywhere

Managed cloud, your VPC, on-prem, even air-gapped. Nothing phones home.

Fork a whole company

Start from another company's OS in one click — and publish your own.

Your company's brain shouldn't live in twelve tools that lease it back to you.

Enterprise & security

Built to survive a security review.

Isolated execution, scoped credentials, a complete audit trail, and human approval gates — not retrofits, it's how Kortix is built. Run it on our cloud or your own infrastructure.

Every session spins up its own isolated sandbox on its own Git branch — a clean clone of main with its own compute. Thousands of coworkers can run in parallel with zero crossover, and durable changes return only as reviewable change requests.

Get started

Run your whole company from one repo you own.

Start with one workflow, connect the tools it needs, and let your team use it from Slack, the web, or the CLI. Self-host for free, or managed cloud from $20 / seat + usage.

Open source · SSO, RBAC & on-prem · Any model, your keys · No lock-in

kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
kortix
Kortix – The AI Command Center for Your Company