A
lowdefy
89.2
3,025 stars · Apache-2.0
Workflow Automation
Windmill leads by 2.0 · narrow
A
89.2
3,025 stars · Apache-2.0
B · leads
91.2
18,618 stars · AGPL-3.0
lowdefy versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lowdefy is written mainly in JavaScript; Windmill is written mainly in Rust. The composite score is 89.2 for lowdefy and 91.2 for Windmill.
Windmill has 18,618 GitHub stars to lowdefy's 3,025, a gap of 15,593 (6.15×). Forks are 188 for lowdefy and 1,165 for Windmill. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 74 versus 100.
Push history: lowdefy 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 15 for lowdefy (0.005 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
lowdefy 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 lowdefy and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both lowdefy (3,025 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: lowdefy is open source, Windmill is open source.
The lead is split. lowdefy is furthest ahead on license flexibility (96 to 52), while Windmill is furthest ahead on fork community (100 to 74). Choose the dimension a rollout cannot compromise on.
Windmill finishes ahead at 91.2 against lowdefy at 89.2, a 2.0 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 | lowdefy | Windmill |
|---|---|---|
| GitHub stars | 3,025 | 18,618 |
| Forks | 188 | 1,165 |
| Open issues | 15 | 889 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 74 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 89.2 | 91.2 |
Build apps that AI can generate, humans can review, and teams can maintain. Config that works between code and natural language.
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 3,025 for lowdefy. The gap is 15,593 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both lowdefy and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
lowdefy 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 lowdefy scores 89.2. This page calls that a narrow lead for Windmill.