Skip to content
DevUtils Online

Workflow Automation

BrowserOS vs n8n

n8n leads by 10.5 · clear

B · leads

n8n

91.0

210,804 stars · Sustainable Use License

BrowserOS versus n8n is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. BrowserOS is written mainly in Rust; n8n is written mainly in TypeScript. The composite score is 80.5 for BrowserOS and 91.0 for n8n.

n8n has 210,804 GitHub stars to BrowserOS's 14,379, a gap of 196,425 (14.66×). Forks are 1,552 for BrowserOS and 61,571 for n8n. On the log scale used inside this pair, adoption is 78 versus 100, and the fork community is 67 versus 100.

Push history: BrowserOS 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 162 for BrowserOS (0.011 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

BrowserOS is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for BrowserOS and 38 for n8n. This is a procurement signal, not legal advice.

In Workflow Automation, both BrowserOS (14,379 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: BrowserOS is open source, n8n is freemium.

The lead is split. BrowserOS is furthest ahead on license flexibility (52 to 38), while n8n is furthest ahead on fork community (100 to 67). Choose the dimension a rollout cannot compromise on.

n8n finishes ahead at 91.0 against BrowserOS at 80.5, a 10.5 point clear 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.

BrowserOS versus n8n metrics
Signal BrowserOS n8n
GitHub stars 14,379 210,804
Forks 1,552 61,571
Open issues 162 1,266
Adoption 78 100
Activity 100 100
Community 67 100
Issue health 84 84
License 52 38
Self-hosting 100 100
Composite 80.5 91.0

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, BrowserOS or n8n?

n8n has more GitHub stars: 210,804 versus 14,379 for BrowserOS. The gap is 196,425 stars.

Which was updated more recently, BrowserOS or n8n?

Both were last pushed on 17 November 2026.

Can I self-host both BrowserOS and n8n?

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

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

BrowserOS is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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.

Who wins the BrowserOS vs n8n score?

n8n scores 91.0 and BrowserOS scores 80.5. This page calls that a clear lead for n8n.

Related comparisons