Skip to content
DevUtils Online

Workflow Automation

keep vs Node-RED

Node-RED leads by 20.1 · decisive

A

keep

77.8

12,531 stars · license n/a

B · leads

Node-RED

97.9

23,852 stars · Apache-2.0

keep 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. keep is written mainly in Python; Node-RED is written mainly in JavaScript. The composite score is 77.8 for keep and 97.9 for Node-RED.

Node-RED has 23,852 GitHub stars to keep's 12,531, a gap of 11,321 (1.90×). Forks are 1,555 for keep and 4,033 for Node-RED. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 88 versus 100.

Push history: keep was last pushed on 16 November 2026 (1 day ago), and Node-RED was last pushed on 17 November 2026 (0 days ago). Open issues stand at 708 for keep (0.056 per star) and 355 for Node-RED (0.015 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.

keep is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for keep and 96 for Node-RED. This is a procurement signal, not legal advice.

Only Node-RED is marked self-hostable here (23,852 stars, deploy score 100). keep is not (12,531 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: keep is unpriced in this catalog, Node-RED is open source.

Node-RED is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is recent activity at 0 points (100 vs 100).

Node-RED finishes ahead at 97.9 against keep at 77.8, a 20.1 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

keep versus Node-RED metrics
Signal keep Node-RED
GitHub stars 12,531 23,852
Forks 1,555 4,033
Open issues 708 355
Adoption 94 100
Activity 100 100
Community 88 100
Issue health 52 84
License 30 96
Self-hosting 35 100
Composite 77.8 97.9

Node-RED

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, keep or Node-RED?

Node-RED has more GitHub stars: 23,852 versus 12,531 for keep. The gap is 11,321 stars.

Which was updated more recently, keep or Node-RED?

Node-RED was pushed more recently: 17 November 2026 versus 16 November 2026 for keep. That is 1 days apart.

Can I self-host both keep and Node-RED?

Only Node-RED is marked self-hostable. keep is not.

Which license is easier to embed in a commercial product, keep or Node-RED?

keep is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.

Who wins the keep vs Node-RED score?

Node-RED scores 97.9 and keep scores 77.8. This page calls that a decisive lead for Node-RED.

Related comparisons