A · leads
Scrapling
99.1
103,871 stars · BSD-3-Clause
Workflow Automation
Scrapling leads by 16.3 · decisive
A · leads
99.1
103,871 stars · BSD-3-Clause
B
82.8
18,618 stars · AGPL-3.0
Scrapling versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Scrapling is written mainly in Python; Windmill is written mainly in Rust. The composite score is 99.1 for Scrapling and 82.8 for Windmill.
Scrapling has 103,871 GitHub stars to Windmill's 18,618, a gap of 85,253 (5.58×). Forks are 10,835 for Scrapling 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 76.
Push history: Scrapling 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 21 for Scrapling (0.000 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
Scrapling is listed as BSD-3-Clause, 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 Scrapling and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both Scrapling (103,871 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: Scrapling is open source, Windmill is open source.
Scrapling 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).
Scrapling finishes ahead at 99.1 against Windmill at 82.8, a 16.3 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 | Scrapling | Windmill |
|---|---|---|
| GitHub stars | 103,871 | 18,618 |
| Forks | 10,835 | 1,165 |
| Open issues | 21 | 889 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 96 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 82.8 |
🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
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.
Scrapling has more GitHub stars: 103,871 versus 18,618 for Windmill. The gap is 85,253 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Scrapling and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
Scrapling is listed as BSD-3-Clause, 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.
Scrapling scores 99.1 and Windmill scores 82.8. This page calls that a decisive lead for Scrapling.