Skip to content
DevUtils Online

Workflow Automation

n8n vs openbrowser

n8n leads by 19.9 · decisive

A · leads

n8n

91.0

210,804 stars · Sustainable Use License

n8n versus openbrowser 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 71.1 for openbrowser.

n8n has 210,804 GitHub stars to openbrowser's 9,589, a gap of 201,215 (21.98×). Forks are 61,571 for n8n and 867 for openbrowser. On the log scale used inside this pair, adoption is 100 versus 75, and the fork community is 100 versus 61.

Push history: n8n was last pushed on 17 November 2026 (0 days ago), and openbrowser was last pushed on 02 April 2026 (229 days ago). Open issues stand at 1,266 for n8n (0.006 per star) and 20 for openbrowser (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 36.

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. openbrowser 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 openbrowser. This is a procurement signal, not legal advice.

In Workflow Automation, both n8n (210,804 stars) and openbrowser (9,589 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, openbrowser is open source.

The lead is split. n8n is furthest ahead on recent activity (100 to 36), while openbrowser is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.

n8n finishes ahead at 91.0 against openbrowser at 71.1, a 19.9 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

n8n versus openbrowser metrics
Signal n8n openbrowser
GitHub stars 210,804 9,589
Forks 61,571 867
Open issues 1,266 20
Adoption 100 75
Activity 100 36
Community 100 61
Issue health 84 96
License 38 96
Self-hosting 100 100
Composite 91.0 71.1

n8n

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, n8n or openbrowser?

n8n has more GitHub stars: 210,804 versus 9,589 for openbrowser. The gap is 201,215 stars.

Which was updated more recently, n8n or openbrowser?

n8n was pushed more recently: 17 November 2026 versus 02 April 2026 for openbrowser. That is 229 days apart.

Can I self-host both n8n and openbrowser?

Yes. This catalog marks both n8n and openbrowser as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, n8n or openbrowser?

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. openbrowser 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.

Who wins the n8n vs openbrowser score?

n8n scores 91.0 and openbrowser scores 71.1. This page calls that a decisive lead for n8n.

Related comparisons