A
dagster
90.8
16,433 stars · Apache-2.0
Workflow Automation
Node-RED leads by 7.1 · clear
A
90.8
16,433 stars · Apache-2.0
B · leads
97.9
23,852 stars · Apache-2.0
dagster versus Node-RED is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dagster is written mainly in Python; Node-RED is written mainly in JavaScript. The composite score is 90.8 for dagster and 97.9 for Node-RED.
Node-RED has 23,852 GitHub stars to dagster's 16,433, a gap of 7,419 (1.45×). Forks are 2,425 for dagster and 4,033 for Node-RED. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 94 versus 100.
Push history: dagster was last pushed on 17 November 2026 (0 days ago), and Node-RED was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,630 for dagster (0.160 per star) and 355 for Node-RED (0.015 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
Both dagster and Node-RED 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 dagster (16,433 stars) and Node-RED (23,852 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: dagster is open source, Node-RED is open source.
Node-RED is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 50 points (34 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
Node-RED finishes ahead at 97.9 against dagster at 90.8, a 7.1 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | dagster | Node-RED |
|---|---|---|
| GitHub stars | 16,433 | 23,852 |
| Forks | 2,425 | 4,033 |
| Open issues | 2,630 | 355 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.8 | 97.9 |
An orchestration platform for the development, production, and observation of data assets.
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.
Node-RED has more GitHub stars: 23,852 versus 16,433 for dagster. The gap is 7,419 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dagster and Node-RED as self-hostable. Confirm each project's deploy docs before you plan a migration.
dagster 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Node-RED scores 97.9 and dagster scores 90.8. This page calls that a clear lead for Node-RED.