A · leads
n8n
91.0
210,804 stars · Sustainable Use License
Workflow Automation
n8n leads by 7.0 · clear
A · leads
91.0
210,804 stars · Sustainable Use License
B
84.0
9,166 stars · MIT
n8n versus rig is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. n8n is written mainly in TypeScript; rig is written mainly in Rust. The composite score is 91.0 for n8n and 84.0 for rig.
n8n has 210,804 GitHub stars to rig's 9,166, a gap of 201,638 (23.00×). Forks are 61,571 for n8n and 1,023 for rig. On the log scale used inside this pair, adoption is 100 versus 74, and the fork community is 100 versus 63.
Push history: n8n was last pushed on 17 November 2026 (0 days ago), and rig was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,266 for n8n (0.006 per star) and 64 for rig (0.007 per star). Issue-health scores are 84 and 84; 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. rig 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 rig. This is a procurement signal, not legal advice.
In Workflow Automation, both n8n (210,804 stars) and rig (9,166 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, rig is open source.
The lead is split. n8n is furthest ahead on fork community (100 to 63), while rig is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against rig at 84.0, a 7.0 point clear 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 | rig |
|---|---|---|
| GitHub stars | 210,804 | 9,166 |
| Forks | 61,571 | 1,023 |
| Open issues | 1,266 | 64 |
| Adoption | 100 | 74 |
| Activity | 100 | 100 |
| Community | 100 | 63 |
| Issue health | 84 | 84 |
| License | 38 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.0 | 84.0 |
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.
⚙️🦀 Build modular and scalable LLM Applications in Rust
n8n has more GitHub stars: 210,804 versus 9,166 for rig. The gap is 201,638 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both n8n and rig 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. rig 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.
n8n scores 91.0 and rig scores 84.0. This page calls that a clear lead for n8n.