A
cadence
85.0
9,557 stars · Apache-2.0
Workflow Automation
paperclip leads by 9.7 · clear
A
85.0
9,557 stars · Apache-2.0
B · leads
94.7
114,484 stars · MIT
cadence versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cadence is written mainly in Go; paperclip is written mainly in TypeScript. The composite score is 85.0 for cadence and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to cadence's 9,557, a gap of 104,927 (11.98×). Forks are 931 for cadence and 18,987 for paperclip. On the log scale used inside this pair, adoption is 79 versus 100, and the fork community is 69 versus 100.
Push history: cadence 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 220 for cadence (0.023 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
cadence 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 cadence and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both cadence (9,557 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: cadence is open source, paperclip is open source.
The lead is split. cadence is furthest ahead on issue health (70 to 52), while paperclip is furthest ahead on fork community (100 to 69). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against cadence at 85.0, a 9.7 point clear 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 | cadence | paperclip |
|---|---|---|
| GitHub stars | 9,557 | 114,484 |
| Forks | 931 | 18,987 |
| Open issues | 220 | 6,806 |
| Adoption | 79 | 100 |
| Activity | 100 | 100 |
| Community | 69 | 100 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 85.0 | 94.7 |
Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 9,557 for cadence. The gap is 104,927 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cadence and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
cadence 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 cadence scores 85.0. This page calls that a clear lead for paperclip.