A
conductor
90.2
32,478 stars · Apache-2.0
Workflow Automation
paperclip leads by 4.5 · narrow
A
90.2
32,478 stars · Apache-2.0
B · leads
94.7
114,484 stars · MIT
conductor versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. conductor is written mainly in Java; paperclip is written mainly in TypeScript. The composite score is 90.2 for conductor and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to conductor's 32,478, a gap of 82,006 (3.52×). Forks are 1,074 for conductor and 18,987 for paperclip. On the log scale used inside this pair, adoption is 89 versus 100, and the fork community is 71 versus 100.
Push history: conductor was last pushed on 17 November 2026 (0 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 300 for conductor (0.009 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
conductor is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. paperclip is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for conductor and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both conductor (32,478 stars) and paperclip (114,484 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: conductor is open source, paperclip is open source.
The lead is split. conductor is furthest ahead on issue health (84 to 52), while paperclip is furthest ahead on fork community (100 to 71). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against conductor at 90.2, a 4.5 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | conductor | paperclip |
|---|---|---|
| GitHub stars | 32,478 | 114,484 |
| Forks | 1,074 | 18,987 |
| Open issues | 300 | 6,806 |
| Adoption | 89 | 100 |
| Activity | 100 | 100 |
| Community | 71 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.2 | 94.7 |
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 32,478 for conductor. The gap is 82,006 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both conductor and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
conductor is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. paperclip is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
paperclip scores 94.7 and conductor scores 90.2. This page calls that a narrow lead for paperclip.