Skip to content
DevUtils Online

Workflow Automation

n8n vs trigger.dev

n8n leads by 4.8 · narrow

A · leads

n8n

91.0

210,804 stars · Sustainable Use License

n8n versus trigger.dev 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 86.2 for trigger.dev.

n8n has 210,804 GitHub stars to trigger.dev's 16,776, a gap of 194,028 (12.57×). Forks are 61,571 for n8n and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 66.

Push history: n8n was last pushed on 17 November 2026 (0 days ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,266 for n8n (0.006 per star) and 268 for trigger.dev (0.016 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. trigger.dev 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 trigger.dev. This is a procurement signal, not legal advice.

In Workflow Automation, both n8n (210,804 stars) and trigger.dev (16,776 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, trigger.dev is open source.

The lead is split. n8n is furthest ahead on fork community (100 to 66), while trigger.dev is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.

n8n finishes ahead at 91.0 against trigger.dev at 86.2, a 4.8 point narrow 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 trigger.dev metrics
Signal n8n trigger.dev
GitHub stars 210,804 16,776
Forks 61,571 1,534
Open issues 1,266 268
Adoption 100 79
Activity 100 100
Community 100 66
Issue health 84 84
License 38 96
Self-hosting 100 100
Composite 91.0 86.2

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 trigger.dev?

n8n has more GitHub stars: 210,804 versus 16,776 for trigger.dev. The gap is 194,028 stars.

Which was updated more recently, n8n or trigger.dev?

Both were last pushed on 17 November 2026.

Can I self-host both n8n and trigger.dev?

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

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. trigger.dev 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.

Who wins the n8n vs trigger.dev score?

n8n scores 91.0 and trigger.dev scores 86.2. This page calls that a narrow lead for n8n.

Related comparisons