What is a company operating system?
A company operating system is a company's standard way of running: its processes, roles, meeting rhythms, scorecards and accountability. It is the written answer to how work gets decided and reviewed, and it applies whether the company has ten people or a thousand. Management frameworks such as EOS and Scaling Up are packaged examples of one.
An AI company operating system keeps that meaning and adds a persistent team of AI agents working from shared context, skills and memory.
Two meanings of company operating system
The management meaning. In management writing, a business operating system is the enterprise-wide collection of processes a company runs on, together with the structure and principles behind them. EOS gives that idea a fixed shape: six components (Vision, People, Data, Issues, Process, Traction), a scorecard of objective measurables, and documented core processes. People sit in named seats, so accountability is clear, and the team sets priorities every 90 days. Scaling Up packages a comparable system. In both, people do the work, and the playbook is what persists.
The AI meaning. An AI company operating system is a running team of agents you hand recurring work to. Something has to receive the goal, split it into tasks, and route each task to a worker that can carry it. Context has to survive the session, and the system has to stop wherever a person should decide. The system persists, and the workers become replaceable.
| What it is | Who does the work | What persists | |
|---|---|---|---|
| Management framework (EOS, Scaling Up) | A written management system: vision, seats, scorecard, meeting rhythm and processes | People in the company, following the playbook | The playbook and the meeting rhythm, carried by the people who run them |
| AI agent framework (LangChain, CrewAI, the OpenAI Agents SDK) | A library developers build agent logic with, inside their own application | The application your team writes and operates | Whatever state the developer chooses to store, from a checkpoint to nothing at all |
| Persistent agent swarm (Agent Swarm) | A running system where a lead agent routes work to workers and keeps the team's context | AI workers on Claude Code, Codex or another harness, each in an isolated container | The team's tasks, memory and schedules, in the swarm's own database |
Where persistent agents fit
Routing and isolated execution. A lead agent takes a goal, breaks it into tasks and sends each one to a worker. Each worker runs the harness you pick for it, such as Claude Code or Codex, inside its own container with its own workspace. See the architecture overview.
Shared context and memory. Memory outlives the session. Next Monday's worker can read what last Monday's worker learned, so context is rebuilt from the record instead of from someone's explanation. See memory.
Skills. A skill is a written procedure an agent loads when the work matches it: how we review a pull request, how we write a release note. Skills install per agent or across the swarm, so a procedure is written once and reused. See the skills reference.
Workflows and schedules. A workflow runs steps in a fixed order, retrying a failed step under its own policy and validating what each step returns. A schedule starts work on a cadence without anyone kicking it off. See workflows and scheduling.
Human accountability. A human-in-the-loop step pauses a workflow until a person approves or answers. Review gates sit wherever you configure them, and a person still owns the decision and the merge. See the task lifecycle.
What Agent Swarm does not replace
Agent Swarm does not replace your management framework. If you run EOS or Scaling Up, or a system you wrote yourself, that system still defines the vision and the seats, plus the meeting rhythm. Agent Swarm runs recurring work inside the operating system you already have.
It does not replace the accountability those frameworks assign to people, and it does not make leadership decisions. Priorities and hiring are still yours, along with pricing and the decision about what to stop. It also does not take over the operator's duties: deploying the system and upgrading it stay with you, along with backups and network exposure. The security page sets out which controls the software provides and which duties remain the operator's.
One naming collision is worth clearing up. Agent Swarm is not OpenAI Swarm. OpenAI Swarm is OpenAI's experimental educational library, since replaced by the OpenAI Agents SDK. Agent Swarm is a different product, an open-source, self-hosted system built by Desplega Labs. The comparison page covers the difference in detail.
See it in practice
- An issue that ends in a human-approved merge: a coding worker implements a memory feature and triages a security finding on its own pull request, then answers review until a maintainer merges.
- A brief that runs every morning: a schedule fires before dawn, scripts assemble the brief from registered sources, and the email is waiting before the founders start the day.
- Security alerts triaged behind an approval gate: a worker reads the Dependabot queue and proposes one grouped pull request, a person approves the plan, and a maintainer merges.
Start at the product page for what the swarm does. The security page covers the trust model, and the documentation covers setup.
FAQ
Is a company operating system the same as EOS?
No. A company operating system is the general idea: the standard way a company runs. EOS and Scaling Up are specific versions of it, and so is a system you wrote yourself.
Does Agent Swarm replace EOS or Scaling Up?
No. Those frameworks set the vision and the seats for the people in the company. Agent Swarm runs recurring work inside the system you already have, and the accountability the framework assigns stays in place.
What does an AI company operating system add?
A standing team of agents that keeps context between sessions. Goals become tasks and tasks go to workers. Memory and skills hold the company's procedures instead of one person's recollection of them.
Who stays accountable for agent work?
People do. A human-in-the-loop step pauses the workflow for a named decision, review gates sit where you configure them, and a person approves and merges.
Is Agent Swarm the same as OpenAI Swarm?
No. OpenAI Swarm is OpenAI's experimental educational library, replaced by the OpenAI Agents SDK. Agent Swarm is an open-source, self-hosted system built by Desplega Labs.
How do I run it?
Self-host it. The code is open source under the MIT License, and the documentation covers Docker Compose and a Kubernetes Helm chart. For support or deployment questions, use the contact page.