A · leads
skyvern
92.6
23,434 stars · AGPL-3.0
Workflow Automation
skyvern leads by 3.3 · narrow
A · leads
92.6
23,434 stars · AGPL-3.0
B
89.3
18,618 stars · AGPL-3.0
skyvern versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. skyvern is written mainly in Python; Windmill is written mainly in Rust. The composite score is 92.6 for skyvern and 89.3 for Windmill.
skyvern has 23,434 GitHub stars to Windmill's 18,618, a gap of 4,816 (1.26×). Forks are 2,246 for skyvern and 1,165 for Windmill. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 92.
Push history: skyvern 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 301 for skyvern (0.013 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
Both skyvern and Windmill are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both skyvern (23,434 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: skyvern is open source, Windmill is open source.
skyvern is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 14 points (84 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
skyvern finishes ahead at 92.6 against Windmill at 89.3, a 3.3 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 | skyvern | Windmill |
|---|---|---|
| GitHub stars | 23,434 | 18,618 |
| Forks | 2,246 | 1,165 |
| Open issues | 301 | 889 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 84 | 70 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 89.3 |
Automate browser based workflows with AI
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.
skyvern has more GitHub stars: 23,434 versus 18,618 for Windmill. The gap is 4,816 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both skyvern and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
skyvern 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. 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.
skyvern scores 92.6 and Windmill scores 89.3. This page calls that a narrow lead for skyvern.