A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 3.5 · narrow
A · leads
97.9
50,147 stars · MIT
B
94.4
23,852 stars · Apache-2.0
nanobot 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. nanobot is written mainly in Python; Node-RED is written mainly in JavaScript. The composite score is 97.9 for nanobot and 94.4 for Node-RED.
nanobot has 50,147 GitHub stars to Node-RED's 23,852, a gap of 26,295 (2.10×). Forks are 8,755 for nanobot 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 92.
Push history: nanobot 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 872 for nanobot (0.017 per star) and 355 for Node-RED (0.015 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
nanobot 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 nanobot and 96 for Node-RED. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 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: nanobot is open source, Node-RED is open source.
nanobot 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 8 points (100 vs 92), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against Node-RED at 94.4, a 3.5 point narrow 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 | nanobot | Node-RED |
|---|---|---|
| GitHub stars | 50,147 | 23,852 |
| Forks | 8,755 | 4,033 |
| Open issues | 872 | 355 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 94.4 |
Your lightweight open-source personal agent.
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.
nanobot has more GitHub stars: 50,147 versus 23,852 for Node-RED. The gap is 26,295 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobot and Node-RED as self-hostable. Confirm each project's deploy docs before you plan a migration.
nanobot 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.
nanobot scores 97.9 and Node-RED scores 94.4. This page calls that a narrow lead for nanobot.