A
edict
87.4
17,077 stars · MIT
Workflow Automation
Node-RED leads by 10.5 · clear
A
87.4
17,077 stars · MIT
B · leads
97.9
23,852 stars · Apache-2.0
edict 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. edict is written mainly in Python; Node-RED is written mainly in JavaScript. The composite score is 87.4 for edict and 97.9 for Node-RED.
Node-RED has 23,852 GitHub stars to edict's 17,077, a gap of 6,775 (1.40×). Forks are 1,771 for edict and 4,033 for Node-RED. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 90 versus 100.
Push history: edict was last pushed on 28 September 2026 (50 days ago), and Node-RED was last pushed on 17 November 2026 (0 days ago). Open issues stand at 15 for edict (0.001 per star) and 355 for Node-RED (0.015 per star). Issue-health scores are 96 and 84; activity scores are 58 and 100.
edict is listed as MIT, 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. License scores in this pair are 96 for edict and 96 for Node-RED. This is a procurement signal, not legal advice.
In Workflow Automation, both edict (17,077 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: edict is open source, Node-RED is open source.
The lead is split. edict is furthest ahead on issue health (96 to 84), while Node-RED is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
Node-RED finishes ahead at 97.9 against edict at 87.4, a 10.5 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 | edict | Node-RED |
|---|---|---|
| GitHub stars | 17,077 | 23,852 |
| Forks | 1,771 | 4,033 |
| Open issues | 15 | 355 |
| Adoption | 97 | 100 |
| Activity | 58 | 100 |
| Community | 90 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.4 | 97.9 |
🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System — 9 specialized AI agents with real-time dashboard, model config, and full audit trails
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 17,077 for edict. The gap is 6,775 stars.
Node-RED was pushed more recently: 17 November 2026 versus 28 September 2026 for edict. That is 50 days apart.
Yes. This catalog marks both edict and Node-RED as self-hostable. Confirm each project's deploy docs before you plan a migration.
edict is listed as MIT, 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 edict scores 87.4. This page calls that a clear lead for Node-RED.