A
leon
86.3
17,690 stars · MIT
Workflow Automation
n8n leads by 4.7 · narrow
A
86.3
17,690 stars · MIT
B · leads
91.0
210,804 stars · Sustainable Use License
leon versus n8n 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 86.3 for leon and 91.0 for n8n.
n8n has 210,804 GitHub stars to leon's 17,690, a gap of 193,114 (11.92×). Forks are 1,484 for leon and 61,571 for n8n. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 66 versus 100.
Push history: leon was last pushed on 17 November 2026 (0 days ago), and n8n was last pushed on 17 November 2026 (0 days ago). Open issues stand at 118 for leon (0.007 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
leon 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. 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. License scores in this pair are 96 for leon and 38 for n8n. This is a procurement signal, not legal advice.
In Workflow Automation, both leon (17,690 stars) and n8n (210,804 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: leon is open source, n8n is freemium.
The lead is split. leon is furthest ahead on license flexibility (96 to 38), while n8n is furthest ahead on fork community (100 to 66). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against leon at 86.3, a 4.7 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 | leon | n8n |
|---|---|---|
| GitHub stars | 17,690 | 210,804 |
| Forks | 1,484 | 61,571 |
| Open issues | 118 | 1,266 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 66 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 38 |
| Self-hosting | 100 | 100 |
| Composite | 86.3 | 91.0 |
🧠 Leon is your open-source personal assistant.
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.
n8n has more GitHub stars: 210,804 versus 17,690 for leon. The gap is 193,114 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both leon and n8n as self-hostable. Confirm each project's deploy docs before you plan a migration.
leon 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
n8n scores 91.0 and leon scores 86.3. This page calls that a narrow lead for n8n.