A
bruno
88.6
48,427 stars · MIT
Workflow Automation
n8n leads by 2.4 · narrow
A
88.6
48,427 stars · MIT
B · leads
91.0
210,804 stars · Sustainable Use License
bruno versus n8n is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruno is written mainly in JavaScript; n8n is written mainly in TypeScript. The composite score is 88.6 for bruno and 91.0 for n8n.
n8n has 210,804 GitHub stars to bruno's 48,427, a gap of 162,377 (4.35×). Forks are 3,115 for bruno and 61,571 for n8n. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 73 versus 100.
Push history: bruno 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 2,002 for bruno (0.041 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
bruno 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 bruno and 38 for n8n. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 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: bruno is open source, n8n is freemium.
The lead is split. bruno is furthest ahead on license flexibility (96 to 38), while n8n is furthest ahead on fork community (100 to 73). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against bruno at 88.6, a 2.4 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 | bruno | n8n |
|---|---|---|
| GitHub stars | 48,427 | 210,804 |
| Forks | 3,115 | 61,571 |
| Open issues | 2,002 | 1,266 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 73 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 38 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 91.0 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
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 48,427 for bruno. The gap is 162,377 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruno and n8n as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruno 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 bruno scores 88.6. This page calls that a narrow lead for n8n.