A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 5.4 · narrow
A · leads
97.4
112,653 stars · MIT
B
92.0
23,852 stars · Apache-2.0
Agent-Reach 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. Agent-Reach is written mainly in Python; Node-RED is written mainly in JavaScript. The composite score is 97.4 for Agent-Reach and 92.0 for Node-RED.
Agent-Reach has 112,653 GitHub stars to Node-RED's 23,852, a gap of 88,801 (4.72×). Forks are 10,094 for Agent-Reach and 4,033 for Node-RED. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 90.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and Node-RED was last pushed on 17 November 2026 (0 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 355 for Node-RED (0.015 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.
Agent-Reach 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 Agent-Reach and 96 for Node-RED. This is a procurement signal, not legal advice.
In Workflow Automation, both Agent-Reach (112,653 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: Agent-Reach is open source, Node-RED is open source.
The lead is split. Agent-Reach is furthest ahead on adoption (100 to 87), while Node-RED is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
Agent-Reach finishes ahead at 97.4 against Node-RED at 92.0, a 5.4 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 | Agent-Reach | Node-RED |
|---|---|---|
| GitHub stars | 112,653 | 23,852 |
| Forks | 10,094 | 4,033 |
| Open issues | 133 | 355 |
| Adoption | 100 | 87 |
| Activity | 92 | 100 |
| Community | 100 | 90 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 92.0 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
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.
Agent-Reach has more GitHub stars: 112,653 versus 23,852 for Node-RED. The gap is 88,801 stars.
Node-RED was pushed more recently: 17 November 2026 versus 08 November 2026 for Agent-Reach. That is 9 days apart.
Yes. This catalog marks both Agent-Reach and Node-RED as self-hostable. Confirm each project's deploy docs before you plan a migration.
Agent-Reach 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.
Agent-Reach scores 97.4 and Node-RED scores 92.0. This page calls that a narrow lead for Agent-Reach.