A
n8n-as-code
74.2
1,663 stars · MIT
Workflow Automation
paperclip leads by 20.5 · decisive
A
74.2
1,663 stars · MIT
B · leads
94.7
114,484 stars · MIT
n8n-as-code 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 74.2 for n8n-as-code and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to n8n-as-code's 1,663, a gap of 112,821 (68.84×). Forks are 190 for n8n-as-code and 18,987 for paperclip. On the log scale used inside this pair, adoption is 64 versus 100, and the fork community is 53 versus 100.
Push history: n8n-as-code was last pushed on 01 November 2026 (16 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 20 for n8n-as-code (0.012 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 84 and 52; activity scores are 78 and 100.
Both n8n-as-code 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 n8n-as-code (1,663 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-as-code is open source, paperclip is open source.
The lead is split. n8n-as-code is furthest ahead on issue health (84 to 52), while paperclip is furthest ahead on fork community (100 to 53). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against n8n-as-code at 74.2, a 20.5 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 | n8n-as-code | paperclip |
|---|---|---|
| GitHub stars | 1,663 | 114,484 |
| Forks | 190 | 18,987 |
| Open issues | 20 | 6,806 |
| Adoption | 64 | 100 |
| Activity | 78 | 100 |
| Community | 53 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 74.2 | 94.7 |
Give your AI agent n8n superpowers. 537 nodes with full schemas, 7,700+ templates, Git-like sync, and TypeScript workflows.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 1,663 for n8n-as-code. The gap is 112,821 stars.
paperclip was pushed more recently: 17 November 2026 versus 01 November 2026 for n8n-as-code. That is 16 days apart.
Yes. This catalog marks both n8n-as-code and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
n8n-as-code 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 n8n-as-code scores 74.2. This page calls that a decisive lead for paperclip.