A · level
Huginn
96.2
50,561 stars · MIT
Workflow Automation
Too close to call · 96.2 to 95.4
A · level
96.2
50,561 stars · MIT
B · level
95.4
23,852 stars · Apache-2.0
Huginn 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. Huginn is written mainly in Ruby; Node-RED is written mainly in JavaScript. The composite score is 96.2 for Huginn and 95.4 for Node-RED.
Huginn has 50,561 GitHub stars to Node-RED's 23,852, a gap of 26,709 (2.12×). Forks are 4,356 for Huginn and 4,033 for Node-RED. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 99.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and Node-RED was last pushed on 17 November 2026 (0 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 355 for Node-RED (0.015 per star). Issue-health scores are 84 and 84; activity scores are 92 and 100.
Huginn 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 Huginn and 96 for Node-RED. This is a procurement signal, not legal advice.
In Workflow Automation, both Huginn (50,561 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: Huginn is open source, Node-RED is open source.
The lead is split. Huginn is furthest ahead on adoption (100 to 93), while Node-RED is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
Composite score: Huginn 96.2, Node-RED 95.4. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | Huginn | Node-RED |
|---|---|---|
| GitHub stars | 50,561 | 23,852 |
| Forks | 4,356 | 4,033 |
| Open issues | 692 | 355 |
| Adoption | 100 | 93 |
| Activity | 92 | 100 |
| Community | 100 | 99 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 95.4 |
Huginn is a self-hosted agent system that watches the web and triggers actions from events. It predates the current wave of LLM agents and is closer to a personal IFTTT you run yourself.
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.
Huginn has more GitHub stars: 50,561 versus 23,852 for Node-RED. The gap is 26,709 stars.
Node-RED was pushed more recently: 17 November 2026 versus 09 November 2026 for Huginn. That is 8 days apart.
Yes. This catalog marks both Huginn and Node-RED as self-hostable. Confirm each project's deploy docs before you plan a migration.
Huginn 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.
Neither tool clears a one-point margin. Huginn scores 96.2 and Node-RED scores 95.4.