A · leads
trigger.dev
97.5
16,776 stars · Apache-2.0
Workflow Automation
trigger.dev leads by 6.8 · narrow
A · leads
97.5
16,776 stars · Apache-2.0
B
90.7
18,618 stars · AGPL-3.0
trigger.dev versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. trigger.dev is written mainly in TypeScript; Windmill is written mainly in Rust. The composite score is 97.5 for trigger.dev and 90.7 for Windmill.
Windmill has 18,618 GitHub stars to trigger.dev's 16,776, a gap of 1,842 (1.11×). Forks are 1,534 for trigger.dev 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 96.
Push history: trigger.dev 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 268 for trigger.dev (0.016 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
trigger.dev 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 trigger.dev and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both trigger.dev (16,776 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: trigger.dev is open source, Windmill is open source.
The lead is split. trigger.dev is furthest ahead on license flexibility (96 to 52), while Windmill is furthest ahead on adoption (100 to 99). Choose the dimension a rollout cannot compromise on.
trigger.dev finishes ahead at 97.5 against Windmill at 90.7, a 6.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 | trigger.dev | Windmill |
|---|---|---|
| GitHub stars | 16,776 | 18,618 |
| Forks | 1,534 | 1,165 |
| Open issues | 268 | 889 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 84 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.5 | 90.7 |
Trigger.dev – build and deploy durable AI agents and 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.
Windmill has more GitHub stars: 18,618 versus 16,776 for trigger.dev. The gap is 1,842 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both trigger.dev and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
trigger.dev 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.
trigger.dev scores 97.5 and Windmill scores 90.7. This page calls that a narrow lead for trigger.dev.