A · level
n8n
91.0
210,804 stars · Sustainable Use License
Workflow Automation
Too close to call · 91.0 to 91.5
A · level
91.0
210,804 stars · Sustainable Use License
B · level
91.5
114,484 stars · MIT
n8n 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 91.0 for n8n and 91.5 for paperclip.
n8n has 210,804 GitHub stars to paperclip's 114,484, a gap of 96,320 (1.84×). Forks are 61,571 for n8n and 18,987 for paperclip. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 89.
Push history: n8n 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 1,266 for n8n (0.006 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
n8n is listed as Sustainable Use License, which this catalog treats as source-available terms, not a standard OSI open-source license. The grant often limits competing hosted services or some commercial uses. 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 38 for n8n and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both n8n (210,804 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: n8n is freemium, paperclip is open source.
The lead is split. n8n is furthest ahead on issue health (84 to 52), while paperclip is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.
Composite score: n8n 91.0, paperclip 91.5. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | n8n | paperclip |
|---|---|---|
| GitHub stars | 210,804 | 114,484 |
| Forks | 61,571 | 18,987 |
| Open issues | 1,266 | 6,806 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 84 | 52 |
| License | 38 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.0 | 91.5 |
n8n is a workflow automation product with a node canvas, self-hosting, and a paid cloud. Its code is source-available under a sustainable-use license, not an OSI open-source license.
The open-source app everyone uses to manage agents at work
n8n has more GitHub stars: 210,804 versus 114,484 for paperclip. The gap is 96,320 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both n8n and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
n8n is listed as Sustainable Use License, which this catalog treats as source-available terms, not a standard OSI open-source license. The grant often limits competing hosted services or some commercial uses. 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.
Neither tool clears a one-point margin. n8n scores 91.0 and paperclip scores 91.5.