A
Node-RED
92.5
23,852 stars · Apache-2.0
Workflow Automation
puppeteer leads by 6.6 · narrow
A
92.5
23,852 stars · Apache-2.0
B · leads
99.1
95,849 stars · Apache-2.0
Node-RED versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Node-RED is written mainly in JavaScript; puppeteer is written mainly in TypeScript. The composite score is 92.5 for Node-RED and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to Node-RED's 23,852, a gap of 71,997 (4.02×). Forks are 4,033 for Node-RED and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 90 versus 100.
Push history: Node-RED was last pushed on 17 November 2026 (0 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 355 for Node-RED (0.015 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both Node-RED and puppeteer are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both Node-RED (23,852 stars) and puppeteer (95,849 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: Node-RED is open source, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is adoption at 12 points (88 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against Node-RED at 92.5, a 6.6 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 | Node-RED | puppeteer |
|---|---|---|
| GitHub stars | 23,852 | 95,849 |
| Forks | 4,033 | 9,607 |
| Open issues | 355 | 201 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.5 | 99.1 |
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.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 23,852 for Node-RED. The gap is 71,997 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Node-RED and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. puppeteer 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.
puppeteer scores 99.1 and Node-RED scores 92.5. This page calls that a narrow lead for puppeteer.