A · leads
cadence
93.8
9,557 stars · Apache-2.0
Workflow Automation
cadence leads by 2.6 · narrow
A · leads
93.8
9,557 stars · Apache-2.0
B
91.2
18,618 stars · AGPL-3.0
cadence versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cadence is written mainly in Go; Windmill is written mainly in Rust. The composite score is 93.8 for cadence and 91.2 for Windmill.
Windmill has 18,618 GitHub stars to cadence's 9,557, a gap of 9,061 (1.95×). Forks are 931 for cadence and 1,165 for Windmill. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 97 versus 100.
Push history: cadence 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 220 for cadence (0.023 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
cadence 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 cadence and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both cadence (9,557 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: cadence is open source, Windmill is open source.
The lead is split. cadence is furthest ahead on license flexibility (96 to 52), while Windmill is furthest ahead on adoption (100 to 93). Choose the dimension a rollout cannot compromise on.
cadence finishes ahead at 93.8 against Windmill at 91.2, 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 | cadence | Windmill |
|---|---|---|
| GitHub stars | 9,557 | 18,618 |
| Forks | 931 | 1,165 |
| Open issues | 220 | 889 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 93.8 | 91.2 |
Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
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 9,557 for cadence. The gap is 9,061 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cadence and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
cadence 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.
cadence scores 93.8 and Windmill scores 91.2. This page calls that a narrow lead for cadence.