A · leads
n8n
91.0
210,804 stars · Sustainable Use License
Workflow Automation
n8n leads by 15.4 · decisive
A · leads
91.0
210,804 stars · Sustainable Use License
B
75.6
1,285 stars · MIT
n8n versus workflow 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; workflow is written mainly in PHP. The composite score is 91.0 for n8n and 75.6 for workflow.
n8n has 210,804 GitHub stars to workflow's 1,285, a gap of 209,519 (164.05×). Forks are 61,571 for n8n and 94 for workflow. On the log scale used inside this pair, adoption is 100 versus 58, and the fork community is 100 versus 41.
Push history: n8n was last pushed on 17 November 2026 (0 days ago), and workflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,266 for n8n (0.006 per star) and 12 for workflow (0.009 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. workflow 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 workflow. This is a procurement signal, not legal advice.
In Workflow Automation, both n8n (210,804 stars) and workflow (1,285 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, workflow is open source.
The lead is split. n8n is furthest ahead on fork community (100 to 41), while workflow is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against workflow at 75.6, a 15.4 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 | workflow |
|---|---|---|
| GitHub stars | 210,804 | 1,285 |
| Forks | 61,571 | 94 |
| Open issues | 1,266 | 12 |
| Adoption | 100 | 58 |
| Activity | 100 | 100 |
| Community | 100 | 41 |
| Issue health | 84 | 84 |
| License | 38 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.0 | 75.6 |
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.
Core package for defining and running durable workflows and activities. Supports long-running persistent workflows, retries, queues, parallel execution, workflow monitoring, dedicated storage connections, and orchestration for microservices, data pipelines, sagas, agentic workflows, and other complex business processes.
n8n has more GitHub stars: 210,804 versus 1,285 for workflow. The gap is 209,519 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both n8n and workflow 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. workflow 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 workflow scores 75.6. This page calls that a decisive lead for n8n.