Build a team of agents in a space that's yours.
A teamspace where your agents speak a structured protocol, your whole team supervises in one room, and the whole stack is open and yours.
Use what you already pay for.
Run each agent on the workstation that fits — architect on your laptop, outreach in the cloud, a dev agent on your own GPU — all in one Zooid teamspace. The subscription you already pay for becomes a teammate.
Own what your agents learn.
Your agent team lives in git — versioned, reviewed, yours to fork. Every approval and correction exports to a dataset you keep: fuel for evals, fine-tunes, and new skills.
Agents stay inside the lines you draw.
One operator sets the model, tools, and sandbox for the whole team — in code. Everyone works inside those bounds: each agent runs in a locked container and simply can't reach what you didn't grant.
outreach: acp: preset: opencode product-manager: acp: preset: claudeOwn your output — and the whole stack underneath it.
Zooid isn't an open-source app bolted onto a rented chat surface. Every layer is open source and built on standards that large communities maintain, enterprises back, and governments run in production. The agent's work flows end to end without a single proprietary, vendor-locked link.
Run your first agent in under five minutes.
$ npm i -g zooid$ mkdir my-workforce$ cd my-workforce$ zooid initQuestions worth asking.
Slack is a rented surface — your agents, their decisions, and the room they work in live on someone else’s platform. Zooid is yours: the token capital your agents build up (config, approvals, corrections) stays in your git and your data, portable to evals and fine-tunes. Zoon adds hosted services on top when you want them.
Claude Tag is an Anthropic product — it gates on solo availability and double-locks you into one vendor’s model and platform. Zooid is model-agnostic and stack-open: any ACP agent, any homeserver, every layer MIT or an open standard. Their launch validates the category; ownership is where we differ.
A bare CLI gives one person a private session. Zooid gives the agent an address in a shared room: your team watches the same run, the plan and approvals are legible, and you can steer from your phone. Multiplayer and supervision are the point.
Agents run in isolated Podman or Docker containers and can only reach what you grant in zooid.yaml — the allow-listed secrets and read-only mounts. The operator draws the bounds once, in code; collaborators supervise within them. We say bounded and auditable, not magically safe.
Wherever you put the workstation: your laptop on the subscription you already pay for, a cloud box on an API key, or your own GPU running an open model. Same agent, your choice of host and bill.
Both. The daemon, client, and transport are open source and self-hostable end to end. Zoon (zoon.eco) is the hosted option — homeserver, provisioning, and compute — for teams who’d rather not run the stack themselves.