Skip to content
DevUtils Online

Workflow Automation

n8n vs skyvern

n8n leads by 8.6 · clear

A · leads

n8n

91.0

210,804 stars · Sustainable Use License

B

skyvern

82.4

23,434 stars · AGPL-3.0

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

n8n has 210,804 GitHub stars to skyvern's 23,434, a gap of 187,370 (9.00×). Forks are 61,571 for n8n and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 70.

Push history: n8n was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,266 for n8n (0.006 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 84 and 84; 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. skyvern 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. License scores in this pair are 38 for n8n and 52 for skyvern. This is a procurement signal, not legal advice.

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

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

n8n finishes ahead at 91.0 against skyvern at 82.4, a 8.6 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.

n8n versus skyvern metrics
Signal n8n skyvern
GitHub stars 210,804 23,434
Forks 61,571 2,246
Open issues 1,266 301
Adoption 100 82
Activity 100 100
Community 100 70
Issue health 84 84
License 38 52
Self-hosting 100 100
Composite 91.0 82.4

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 skyvern?

n8n has more GitHub stars: 210,804 versus 23,434 for skyvern. The gap is 187,370 stars.

Which was updated more recently, n8n or skyvern?

Both were last pushed on 17 November 2026.

Can I self-host both n8n and skyvern?

Yes. This catalog marks both n8n and skyvern 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 skyvern?

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. skyvern 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the n8n vs skyvern score?

n8n scores 91.0 and skyvern scores 82.4. This page calls that a clear lead for n8n.

Related comparisons