A · leads
conductor
97.8
32,478 stars · Apache-2.0
Workflow Automation
conductor leads by 8.4 · clear
A · leads
97.8
32,478 stars · Apache-2.0
B
89.4
18,618 stars · AGPL-3.0
conductor versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. conductor is written mainly in Java; Windmill is written mainly in Rust. The composite score is 97.8 for conductor and 89.4 for Windmill.
conductor has 32,478 GitHub stars to Windmill's 18,618, a gap of 13,860 (1.74×). Forks are 1,074 for conductor and 1,165 for Windmill. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 99 versus 100.
Push history: conductor 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 300 for conductor (0.009 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
conductor 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 conductor and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both conductor (32,478 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: conductor is open source, Windmill is open source.
The lead is split. conductor is furthest ahead on license flexibility (96 to 52), while Windmill is furthest ahead on fork community (100 to 99). Choose the dimension a rollout cannot compromise on.
conductor finishes ahead at 97.8 against Windmill at 89.4, a 8.4 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 | conductor | Windmill |
|---|---|---|
| GitHub stars | 32,478 | 18,618 |
| Forks | 1,074 | 1,165 |
| Open issues | 300 | 889 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 99 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.8 | 89.4 |
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
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.
conductor has more GitHub stars: 32,478 versus 18,618 for Windmill. The gap is 13,860 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both conductor and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
conductor 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.
conductor scores 97.8 and Windmill scores 89.4. This page calls that a clear lead for conductor.