A · leads
paperclip
94.7
114,484 stars · MIT
Workflow Automation
paperclip leads by 6.0 · narrow
A · leads
94.7
114,484 stars · MIT
B
88.7
16,776 stars · Apache-2.0
paperclip versus trigger.dev is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 94.7 for paperclip and 88.7 for trigger.dev.
paperclip has 114,484 GitHub stars to trigger.dev's 16,776, a gap of 97,708 (6.82×). Forks are 18,987 for paperclip and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 74.
Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
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. trigger.dev 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. License scores in this pair are 96 for paperclip and 96 for trigger.dev. This is a procurement signal, not legal advice.
In Workflow Automation, both paperclip (114,484 stars) and trigger.dev (16,776 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: paperclip is open source, trigger.dev is open source.
The lead is split. paperclip is furthest ahead on fork community (100 to 74), while trigger.dev is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against trigger.dev at 88.7, a 6.0 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 | paperclip | trigger.dev |
|---|---|---|
| GitHub stars | 114,484 | 16,776 |
| Forks | 18,987 | 1,534 |
| Open issues | 6,806 | 268 |
| Adoption | 100 | 84 |
| Activity | 100 | 100 |
| Community | 100 | 74 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 88.7 |
The open-source app everyone uses to manage agents at work
Trigger.dev – build and deploy durable AI agents and workflows
paperclip has more GitHub stars: 114,484 versus 16,776 for trigger.dev. The gap is 97,708 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both paperclip and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. trigger.dev 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
paperclip scores 94.7 and trigger.dev scores 88.7. This page calls that a narrow lead for paperclip.