A · leads
playwright
99.1
100,414 stars · Apache-2.0
Workflow Automation
playwright leads by 32.4 · decisive
A · leads
99.1
100,414 stars · Apache-2.0
B
66.7
10,062 stars · LGPL-3.0
playwright versus tpot 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; tpot is written mainly in Jupyter Notebook. The composite score is 99.1 for playwright and 66.7 for tpot.
playwright has 100,414 GitHub stars to tpot's 10,062, a gap of 90,352 (9.98×). Forks are 6,908 for playwright and 1,557 for tpot. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 83.
Push history: playwright was last pushed on 17 November 2026 (0 days ago), and tpot was last pushed on 11 September 2025 (431 days ago). Open issues stand at 76 for playwright (0.001 per star) and 312 for tpot (0.031 per star). Issue-health scores are 96 and 70; activity scores are 100 and 16.
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. tpot is listed as LGPL-3.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for playwright and 78 for tpot. This is a procurement signal, not legal advice.
In Workflow Automation, both playwright (100,414 stars) and tpot (10,062 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, tpot is open source.
playwright is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is recent activity at 84 points (100 vs 16), and the tightest is self-hosting at 0 points (100 vs 100).
playwright finishes ahead at 99.1 against tpot at 66.7, a 32.4 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 | tpot |
|---|---|---|
| GitHub stars | 100,414 | 10,062 |
| Forks | 6,908 | 1,557 |
| Open issues | 76 | 312 |
| Adoption | 100 | 80 |
| Activity | 100 | 16 |
| Community | 100 | 83 |
| Issue health | 96 | 70 |
| License | 96 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 66.7 |
Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
A Python Automated Machine Learning tool that optimizes machine learning pipelines using genetic programming.
playwright has more GitHub stars: 100,414 versus 10,062 for tpot. The gap is 90,352 stars.
playwright was pushed more recently: 17 November 2026 versus 11 September 2025 for tpot. That is 431 days apart.
Yes. This catalog marks both playwright and tpot 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. tpot is listed as LGPL-3.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
playwright scores 99.1 and tpot scores 66.7. This page calls that a decisive lead for playwright.