A · leads
playwright
99.1
100,414 stars · Apache-2.0
Workflow Automation
playwright leads by 15.6 · decisive
A · leads
99.1
100,414 stars · Apache-2.0
B
83.5
18,618 stars · AGPL-3.0
playwright versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. playwright is written mainly in TypeScript; Windmill is written mainly in Rust. The composite score is 99.1 for playwright and 83.5 for Windmill.
playwright has 100,414 GitHub stars to Windmill's 18,618, a gap of 81,796 (5.39×). Forks are 6,908 for playwright and 1,165 for Windmill. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 80.
Push history: playwright 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 76 for playwright (0.001 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
playwright 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 playwright and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both playwright (100,414 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: playwright is open source, Windmill is open source.
playwright 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).
playwright finishes ahead at 99.1 against Windmill at 83.5, a 15.6 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 | playwright | Windmill |
|---|---|---|
| GitHub stars | 100,414 | 18,618 |
| Forks | 6,908 | 1,165 |
| Open issues | 76 | 889 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 80 |
| Issue health | 96 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 83.5 |
Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
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.
playwright has more GitHub stars: 100,414 versus 18,618 for Windmill. The gap is 81,796 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both playwright and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
playwright 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.
playwright scores 99.1 and Windmill scores 83.5. This page calls that a decisive lead for playwright.