A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 15.9 · decisive
A · leads
99.1
95,849 stars · Apache-2.0
B
83.2
18,618 stars · AGPL-3.0
puppeteer versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. puppeteer is written mainly in TypeScript; Windmill is written mainly in Rust. The composite score is 99.1 for puppeteer and 83.2 for Windmill.
puppeteer has 95,849 GitHub stars to Windmill's 18,618, a gap of 77,231 (5.15×). Forks are 9,607 for puppeteer and 1,165 for Windmill. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 77.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and Windmill was last pushed on 17 November 2026 (0 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
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. Windmill is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for puppeteer and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and Windmill (18,618 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: puppeteer is open source, Windmill is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against Windmill at 83.2, a 15.9 point decisive 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 | puppeteer | Windmill |
|---|---|---|
| GitHub stars | 95,849 | 18,618 |
| Forks | 9,607 | 1,165 |
| Open issues | 201 | 889 |
| Adoption | 100 | 86 |
| Activity | 100 | 100 |
| Community | 100 | 77 |
| Issue health | 96 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 83.2 |
JavaScript API for Chrome and Firefox
Windmill runs scripts and approval flows as internal apps, with workers you can scale. It is used by teams that want automation closer to a developer platform than a no-code zap.
puppeteer has more GitHub stars: 95,849 versus 18,618 for Windmill. The gap is 77,231 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both puppeteer and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Windmill is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
puppeteer scores 99.1 and Windmill scores 83.2. This page calls that a decisive lead for puppeteer.