A · leads
paperclip
94.7
114,484 stars · MIT
Workflow Automation
paperclip leads by 17.4 · decisive
A · leads
94.7
114,484 stars · MIT
B
77.3
1,285 stars · MIT
paperclip versus workflow is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. paperclip is written mainly in TypeScript; workflow is written mainly in PHP. The composite score is 94.7 for paperclip and 77.3 for workflow.
paperclip has 114,484 GitHub stars to workflow's 1,285, a gap of 113,199 (89.09×). Forks are 18,987 for paperclip and 94 for workflow. On the log scale used inside this pair, adoption is 100 versus 62, and the fork community is 100 versus 46.
Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and workflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 12 for workflow (0.009 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
Both paperclip and workflow are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both paperclip (114,484 stars) and workflow (1,285 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, workflow is open source.
The lead is split. paperclip is furthest ahead on fork community (100 to 46), while workflow is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against workflow at 77.3, a 17.4 point decisive 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 | workflow |
|---|---|---|
| GitHub stars | 114,484 | 1,285 |
| Forks | 18,987 | 94 |
| Open issues | 6,806 | 12 |
| Adoption | 100 | 62 |
| Activity | 100 | 100 |
| Community | 100 | 46 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 77.3 |
The open-source app everyone uses to manage agents at work
Core package for defining and running durable workflows and activities. Supports long-running persistent workflows, retries, queues, parallel execution, workflow monitoring, dedicated storage connections, and orchestration for microservices, data pipelines, sagas, agentic workflows, and other complex business processes.
paperclip has more GitHub stars: 114,484 versus 1,285 for workflow. The gap is 113,199 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both paperclip and workflow 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. workflow 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 workflow scores 77.3. This page calls that a decisive lead for paperclip.