A
argo-events
87.4
2,718 stars · Apache-2.0
Workflow Automation
Windmill leads by 3.8 · narrow
A
87.4
2,718 stars · Apache-2.0
B · leads
91.2
18,618 stars · AGPL-3.0
argo-events versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. argo-events is written mainly in Go; Windmill is written mainly in Rust. The composite score is 87.4 for argo-events and 91.2 for Windmill.
Windmill has 18,618 GitHub stars to argo-events's 2,718, a gap of 15,900 (6.85×). Forks are 848 for argo-events and 1,165 for Windmill. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 96 versus 100.
Push history: argo-events was last pushed on 16 November 2026 (0 days ago), and Windmill was last pushed on 17 November 2026 (0 days ago). Open issues stand at 154 for argo-events (0.057 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
argo-events 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 argo-events and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both argo-events (2,718 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: argo-events is open source, Windmill is open source.
The lead is split. argo-events is furthest ahead on license flexibility (96 to 52), while Windmill is furthest ahead on adoption (100 to 80). Choose the dimension a rollout cannot compromise on.
Windmill finishes ahead at 91.2 against argo-events at 87.4, a 3.8 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 | argo-events | Windmill |
|---|---|---|
| GitHub stars | 2,718 | 18,618 |
| Forks | 848 | 1,165 |
| Open issues | 154 | 889 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 52 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 87.4 | 91.2 |
Event-driven Automation Framework for Kubernetes
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 2,718 for argo-events. The gap is 15,900 stars.
Both were last pushed on 16 November 2026.
Yes. This catalog marks both argo-events and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
argo-events 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.
Windmill scores 91.2 and argo-events scores 87.4. This page calls that a narrow lead for Windmill.