/ paperclip vs agent swarm

Orchestration is the layer.
Accumulation is the moat.

Paperclip and a swarm are both open-source, self-hosted and agent-agnostic — Paperclip runs Claude, Codex and Gemini under one org chart. So this was never rented vs owned; it's what compounds. Paperclip coordinates and governs a company of agents, built to run with fewer humans in the loop. A swarm turns every run into memory, identities and evals that make the next one smarter — with a human still in command.

open-source agent
Paperclip
Paperclip logo
vs
Agent Swarm logo
owned swarm
Agent Swarm

The real question isn't which agent is smarter today — it's where the learning accrues, and who owns it.

/ tldr

Paperclip and Agent Swarm are both open-source, self-hosted and agent-agnostic, so this was never rented vs owned — it's what compounds. Paperclip orchestrates and governs a company of agents to run with fewer humans in the loop; Agent Swarm turns every run into memory, identities and evals that make the next one smarter, with a human still in command.

/ both self-hosted, opposite bet

Same infra.
Opposite moats.

OrchestrationPaperclip
The bet

Orchestration is the durable layer — a governed control plane that runs a company of agents.

What compounds

Persistent task state, runtime-injected skills and portable company templates — accumulation for reuse and coordination.

Who's in command

You're the board — set goals, approve hiring and strategy; agents run the company day-to-day. The aim is the 'zero-human company.'

How it improves

Swap in stronger agents or shared templates; the platform coordinates and governs whatever you plug in.

The metaphor

A company of AI employees — org chart, roles, budgets, approval gates, a CEO agent.

AccumulationAgent Swarm
The bet

Accumulation is the moat — a learning loop that compounds into company-specific expertise.

What compounds

Cross-session memory, journals and agent identities — accumulation that makes the next run start smarter.

Who's in command

You direct the Lead — workers execute, reviewers challenge. A human commands the work itself, not just the budget.

How it improves

Private evals on your workflows — and a roadmap to private RL — measured on your definition of done.

The metaphor

A swarm — a Lead that fans work to workers and reviewers, kept as an owned, versioned asset.

/ side by side

The practical
comparison.

Dimension
Core bet
PaperclipOrchestration and governance are the durable layer.
Agent SwarmAccumulation is the moat — the learning loop on top of the agents.
What persists
PaperclipPersistent task state, runtime-injected skills, portable company templates and an append-only audit log.
Agent SwarmCross-session memory, journals and agent identities that compound into institutional context.
How it gets better
PaperclipSwap in stronger agents or shared templates; Paperclip coordinates and governs them.
Agent SwarmPrivate evals on your workflows — roadmap to private RL — on your definition of done.
Human role
PaperclipYou act as the board: set goals and approve structural changes; agents run autonomously between gates.
Agent SwarmYou direct the Lead; workers execute, reviewers challenge — a human stays in command of the work.
Mental model
PaperclipA company of AI employees — org chart, reporting lines, budgets, a CEO agent (Zeus).
Agent SwarmA Lead that decomposes and fans work across many workers and reviewers.
Governance
PaperclipFirst-class — budget caps, atomic task checkout, approval gates, full append-only audit trail.
Agent SwarmHuman-in-command review and challenge; traces and journals stay inside your perimeter.
Agent / model choice
PaperclipAgent-agnostic — Claude, Codex, Gemini, Cursor, Pi, OpenCode, scripts and webhooks under one org chart.
Agent SwarmModel- and harness-agnostic — Claude, Codex, opencode, pi; the model is replaceable compute.
Deployment
PaperclipOpen-source (MIT), self-hosted — Node.js + PostgreSQL + React; managed cloud on the roadmap.
Agent SwarmSelf-hosted (Docker Compose) — or our cloud.
/ the honest tradeoff

Where they're
genuinely strong.

A useful comparison says where each tool actually wins. Agent Swarm is for a persistent, owned operating team; the alternative wins when its shape fits your job better.

Paperclip is genuinely impressive: MIT-licensed, free, self-hosted and agent-agnostic, with first-class governance most tools skip — budget caps, atomic task checkout, approval gates and an append-only audit trail, plus portable company templates and runtime skill injection. Tens of thousands of GitHub stars say it nails the coordination problem. Both self-host and both are model-agnostic, so this isn't a rented-vs-owned infra story. The real difference is the bet: Paperclip wagers that orchestration — running a company of agents, ideally with fewer humans — is the durable layer. A swarm wagers that accumulation is the moat: cross-session memory, identities and private evals that make the system measurably better at your work, with a human kept in command rather than designed out. Want a control plane? Paperclip is excellent. Want a compounding, owned asset? Own the loop.

/ proof by trying

Try the team you'd actually own

Agent Swarm is open source and deploys in minutes. Give it a real Slack, GitHub, or repo task for a day. The useful question isn't which model is best — it's what you can hand to a team that keeps the learning.

/ faq

Direct answers for
AI search.

Is Agent Swarm a Paperclip alternative?

Yes, when the goal is a compounding, owned learning loop rather than a control plane for running a company of agents. Both are open-source and self-hosted; Paperclip orchestrates and governs many agents, while Agent Swarm turns every run into memory, identities and evals that make the next one smarter.

Both are open-source — what actually differs?

The bet, not the infrastructure. Both self-host and both are agent-agnostic, so this isn't rented vs owned. Paperclip wagers that orchestration and governance — running a company of agents, ideally with fewer humans — is the durable layer. Agent Swarm wagers that accumulation is the moat: cross-session memory, identities and private evals that make the system measurably better at your work.

Can I keep a human in command with Agent Swarm?

Yes. Agent Swarm uses a Lead model: you direct the Lead, workers execute, and reviewers challenge — a human stays in command of the work itself, not just the budget. Paperclip's design points toward a board-style role where agents run the company day-to-day between approval gates.

“The moat is not access.
It is accumulation.”

Read the full argument →
/ sources

This page compares product categories and operating models from public product documentation and repositories. We do not claim the tools are interchangeable.

/ keep comparing

See how Agent Swarm stacks up against the rest.

All comparisons
/ get started

Build your swarm tonight.

A 7-day free trial on Cloud, or fork it on GitHub. Either way, your agents start compounding today.