A
Activepieces
90.1
25,581 stars · MIT
Workflow Automation
paperclip leads by 4.6 · narrow
A
90.1
25,581 stars · MIT
B · leads
94.7
114,484 stars · MIT
Activepieces versus paperclip 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 90.1 for Activepieces and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to Activepieces's 25,581, a gap of 88,903 (4.48×). Forks are 4,476 for Activepieces and 18,987 for paperclip. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 85 versus 100.
Push history: Activepieces 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 961 for Activepieces (0.038 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
Both Activepieces and paperclip 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 Activepieces (25,581 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: Activepieces is open source, paperclip is open source.
The lead is split. Activepieces is furthest ahead on issue health (70 to 52), while paperclip is furthest ahead on fork community (100 to 85). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against Activepieces at 90.1, a 4.6 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 | Activepieces | paperclip |
|---|---|---|
| GitHub stars | 25,581 | 114,484 |
| Forks | 4,476 | 18,987 |
| Open issues | 961 | 6,806 |
| Adoption | 87 | 100 |
| Activity | 100 | 100 |
| Community | 85 | 100 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.1 | 94.7 |
Activepieces is a TypeScript workflow tool positioned as a self-hosted automation builder. It focuses on connecting business apps with a visual builder and an MIT-licensed core.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 25,581 for Activepieces. The gap is 88,903 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
Activepieces 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. 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 Activepieces scores 90.1. This page calls that a narrow lead for paperclip.