in its own terms
What Paperclip is for.
Paperclip is the app people use to manage AI agents for work. It is a Node.js server and React UI that orchestrates a team of agents to run a business: you bring your own agents, assign goals, and track work and costs from one dashboard. Its own line is “Manage business goals, not pull requests.”
Under the hood are org charts, budgets, governance, goal alignment, and agent coordination. Tasks are ticket-based, linked to company goals, and finished when their configured review passes. It runs self-hosted — locally as one Node.js process, in production against your own Postgres — and it is MIT-licensed.
side by side
The two, side by side.
| aspect | Paperclip | yardr |
|---|---|---|
| unit of work | A ticket, linked to a company goal. | An issue in a repository. |
| where it runs | Your own machine or server, as a Node.js process. A hosted cloud is on a waitlist. | Your own machine, as one binary. |
| whose credentials | Your agents, with your models and logins. | Your agents, with your logins. |
| who reviews | Management, at configured review and approval stages. | A second agent, then you where the decision is yours. |
| what decides a merge | There is no merge: a configured review decides when a task is done. | Your tests, run on exactly the commit that merges. |
| licence | MIT. | Source-available; the terms are in the repository. |
The choice is what you want managed. To run agents toward business goals — a company with an org chart, budgets, and approval stages — is Paperclip’s shape. To file issues in a repository and get them back as reviewed, tested merges is yardr’s.
sources
Where each fact came from.
Paperclip
What Paperclip is and its shape: the title, the company line, the Node.js server and React UI, and “Manage business goals, not pull requests.”
Ticket tasks linked to goals, configured review and approval stages, bringing your own agents, and the self-hosted setup.
The licence.
yardr
An issue per repository, built by one agent and reviewed by a second, merged after its tests pass.
One binary on macOS and Linux, with your own logins.
The tests run on exactly what merges; nothing is pushed unless YARDR_PUSH names a remote.
The source-available terms.