Skip to content
DevUtils Online

Workflow Automation

Node-RED vs trigger.dev

Node-RED leads by 2.8 · narrow

A · leads

Node-RED

97.9

23,852 stars · Apache-2.0

Node-RED 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. Node-RED is written mainly in JavaScript; trigger.dev is written mainly in TypeScript. The composite score is 97.9 for Node-RED and 95.1 for trigger.dev.

Node-RED has 23,852 GitHub stars to trigger.dev's 16,776, a gap of 7,076 (1.42×). Forks are 4,033 for Node-RED and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 88.

Push history: Node-RED 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 355 for Node-RED (0.015 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Both Node-RED and trigger.dev are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Workflow Automation, both Node-RED (23,852 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: Node-RED is open source, trigger.dev is open source.

Node-RED is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 12 points (100 vs 88), and the tightest is self-hosting at 0 points (100 vs 100).

Node-RED finishes ahead at 97.9 against trigger.dev at 95.1, a 2.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.

Node-RED versus trigger.dev metrics
Signal Node-RED trigger.dev
GitHub stars 23,852 16,776
Forks 4,033 1,534
Open issues 355 268
Adoption 100 96
Activity 100 100
Community 100 88
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 97.9 95.1

Node-RED

Node-RED is a flow-based programming tool from the OpenJS Foundation, widely used to wire APIs, devices, and events. Flows are JSON graphs of nodes that you can version and run on your own host.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Node-RED or trigger.dev?

Node-RED has more GitHub stars: 23,852 versus 16,776 for trigger.dev. The gap is 7,076 stars.

Which was updated more recently, Node-RED or trigger.dev?

Both were last pushed on 17 November 2026.

Can I self-host both Node-RED and trigger.dev?

Yes. This catalog marks both Node-RED 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, Node-RED or trigger.dev?

Node-RED 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. 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 Node-RED vs trigger.dev score?

Node-RED scores 97.9 and trigger.dev scores 95.1. This page calls that a narrow lead for Node-RED.

Related comparisons