A · leads
dagster
92.5
16,433 stars · Apache-2.0
Workflow Automation
dagster leads by 2.6 · narrow
A · leads
92.5
16,433 stars · Apache-2.0
B
89.9
18,618 stars · AGPL-3.0
dagster versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dagster is written mainly in Python; Windmill is written mainly in Rust. The composite score is 92.5 for dagster and 89.9 for Windmill.
Windmill has 18,618 GitHub stars to dagster's 16,433, a gap of 2,185 (1.13×). Forks are 2,425 for dagster and 1,165 for Windmill. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 91.
Push history: dagster 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 2,630 for dagster (0.160 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 34 and 70; activity scores are 100 and 100.
dagster 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 dagster and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both dagster (16,433 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: dagster is open source, Windmill is open source.
The lead is split. dagster is furthest ahead on license flexibility (96 to 52), while Windmill is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
dagster finishes ahead at 92.5 against Windmill at 89.9, a 2.6 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 | dagster | Windmill |
|---|---|---|
| GitHub stars | 16,433 | 18,618 |
| Forks | 2,425 | 1,165 |
| Open issues | 2,630 | 889 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 91 |
| Issue health | 34 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.5 | 89.9 |
An orchestration platform for the development, production, and observation of data assets.
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.
Windmill has more GitHub stars: 18,618 versus 16,433 for dagster. The gap is 2,185 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dagster and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
dagster 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.
dagster scores 92.5 and Windmill scores 89.9. This page calls that a narrow lead for dagster.