A · leads
Windmill
91.2
18,618 stars · AGPL-3.0
Workflow Automation
Windmill leads by 3.5 · narrow
A · leads
91.2
18,618 stars · AGPL-3.0
B
87.7
2,735 stars · MIT
Windmill versus yao-meta-skill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Windmill is written mainly in Rust; yao-meta-skill is written mainly in Python. The composite score is 91.2 for Windmill and 87.7 for yao-meta-skill.
Windmill has 18,618 GitHub stars to yao-meta-skill's 2,735, a gap of 15,883 (6.81×). Forks are 1,165 for Windmill and 254 for yao-meta-skill. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 78.
Push history: Windmill was last pushed on 17 November 2026 (0 days ago), and yao-meta-skill was last pushed on 09 November 2026 (8 days ago). Open issues stand at 889 for Windmill (0.048 per star) and 3 for yao-meta-skill (0.001 per star). Issue-health scores are 70 and 96; activity scores are 100 and 92.
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. yao-meta-skill is listed as MIT, 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. License scores in this pair are 52 for Windmill and 96 for yao-meta-skill. This is a procurement signal, not legal advice.
In Workflow Automation, both Windmill (18,618 stars) and yao-meta-skill (2,735 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: Windmill is open source, yao-meta-skill is open source.
The lead is split. Windmill is furthest ahead on fork community (100 to 78), while yao-meta-skill is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Windmill finishes ahead at 91.2 against yao-meta-skill at 87.7, a 3.5 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 | Windmill | yao-meta-skill |
|---|---|---|
| GitHub stars | 18,618 | 2,735 |
| Forks | 1,165 | 254 |
| Open issues | 889 | 3 |
| Adoption | 100 | 80 |
| Activity | 100 | 92 |
| Community | 100 | 78 |
| Issue health | 70 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 87.7 |
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.
YAO = Yielding AI Outcomes. A rigorous engineering, evaluation, governance, and portability system for reusable agent skills.
Windmill has more GitHub stars: 18,618 versus 2,735 for yao-meta-skill. The gap is 15,883 stars.
Windmill was pushed more recently: 17 November 2026 versus 09 November 2026 for yao-meta-skill. That is 8 days apart.
Yes. This catalog marks both Windmill and yao-meta-skill as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. yao-meta-skill is listed as MIT, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Windmill scores 91.2 and yao-meta-skill scores 87.7. This page calls that a narrow lead for Windmill.