A · leads
n8n
91.0
210,804 stars · Sustainable Use License
Workflow Automation
n8n leads by 4.0 · narrow
A · leads
91.0
210,804 stars · Sustainable Use License
B
87.0
14,334 stars · Apache-2.0
n8n versus nanobrowser 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 91.0 for n8n and 87.0 for nanobrowser.
n8n has 210,804 GitHub stars to nanobrowser's 14,334, a gap of 196,470 (14.71×). Forks are 61,571 for n8n and 1,540 for nanobrowser. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 67.
Push history: n8n was last pushed on 17 November 2026 (0 days ago), and nanobrowser was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,266 for n8n (0.006 per star) and 62 for nanobrowser (0.004 per star). Issue-health scores are 84 and 96; 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. nanobrowser 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 nanobrowser. This is a procurement signal, not legal advice.
In Workflow Automation, both n8n (210,804 stars) and nanobrowser (14,334 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, nanobrowser is open source.
The lead is split. n8n is furthest ahead on fork community (100 to 67), while nanobrowser is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against nanobrowser at 87.0, a 4.0 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 | nanobrowser |
|---|---|---|
| GitHub stars | 210,804 | 14,334 |
| Forks | 61,571 | 1,540 |
| Open issues | 1,266 | 62 |
| Adoption | 100 | 78 |
| Activity | 100 | 100 |
| Community | 100 | 67 |
| Issue health | 84 | 96 |
| License | 38 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.0 | 87.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.
Open-source AI agent for web automation. Use your real, logged-in browser to automate daily tasks.
n8n has more GitHub stars: 210,804 versus 14,334 for nanobrowser. The gap is 196,470 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both n8n and nanobrowser 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. nanobrowser 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 nanobrowser scores 87.0. This page calls that a narrow lead for n8n.