A · leads
n8n
91.0
210,804 stars · Sustainable Use License
Workflow Automation
n8n leads by 2.6 · narrow
A · leads
91.0
210,804 stars · Sustainable Use License
B
88.4
23,852 stars · Apache-2.0
n8n versus Node-RED 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; Node-RED is written mainly in JavaScript. The composite score is 91.0 for n8n and 88.4 for Node-RED.
n8n has 210,804 GitHub stars to Node-RED's 23,852, a gap of 186,952 (8.84×). Forks are 61,571 for n8n and 4,033 for Node-RED. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 75.
Push history: n8n was last pushed on 17 November 2026 (0 days ago), and Node-RED was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,266 for n8n (0.006 per star) and 355 for Node-RED (0.015 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. Node-RED is listed as Apache-2.0, 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 Node-RED. This is a procurement signal, not legal advice.
In Workflow Automation, both n8n (210,804 stars) and Node-RED (23,852 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, Node-RED is open source.
The lead is split. n8n is furthest ahead on fork community (100 to 75), while Node-RED is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against Node-RED at 88.4, a 2.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 | n8n | Node-RED |
|---|---|---|
| GitHub stars | 210,804 | 23,852 |
| Forks | 61,571 | 4,033 |
| Open issues | 1,266 | 355 |
| Adoption | 100 | 82 |
| Activity | 100 | 100 |
| Community | 100 | 75 |
| Issue health | 84 | 84 |
| License | 38 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.0 | 88.4 |
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.
Node-RED is a flow-based programming tool from the OpenJS Foundation, widely used to wire APIs, devices, and events. Flows are JSON graphs of nodes that you can version and run on your own host.
n8n has more GitHub stars: 210,804 versus 23,852 for Node-RED. The gap is 186,952 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both n8n and Node-RED 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. Node-RED is listed as Apache-2.0, 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 Node-RED scores 88.4. This page calls that a narrow lead for n8n.