A · leads
airflow
96.5
47,513 stars · Apache-2.0
Workflow Automation
airflow leads by 12.2 · clear
A · leads
96.5
47,513 stars · Apache-2.0
B
84.3
18,618 stars · AGPL-3.0
airflow versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. airflow is written mainly in Python; Windmill is written mainly in Rust. The composite score is 96.5 for airflow and 84.3 for Windmill.
airflow has 47,513 GitHub stars to Windmill's 18,618, a gap of 28,895 (2.55×). Forks are 18,381 for airflow and 1,165 for Windmill. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 72.
Push history: airflow 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 1,931 for airflow (0.041 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
airflow 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 airflow and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both airflow (47,513 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: airflow is open source, Windmill is open source.
airflow is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, 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).
airflow finishes ahead at 96.5 against Windmill at 84.3, a 12.2 point clear 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 | airflow | Windmill |
|---|---|---|
| GitHub stars | 47,513 | 18,618 |
| Forks | 18,381 | 1,165 |
| Open issues | 1,931 | 889 |
| Adoption | 100 | 91 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 70 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 84.3 |
Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
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.
airflow has more GitHub stars: 47,513 versus 18,618 for Windmill. The gap is 28,895 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both airflow and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
airflow 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.
airflow scores 96.5 and Windmill scores 84.3. This page calls that a clear lead for airflow.