A
LoopForge
78.4
2,919 stars · license n/a
Workflow Automation
Windmill leads by 12.8 · clear
A
78.4
2,919 stars · license n/a
B · leads
91.2
18,618 stars · AGPL-3.0
LoopForge versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. LoopForge is written mainly in Go; Windmill is written mainly in Rust. The composite score is 78.4 for LoopForge and 91.2 for Windmill.
Windmill has 18,618 GitHub stars to LoopForge's 2,919, a gap of 15,699 (6.38×). Forks are 423 for LoopForge and 1,165 for Windmill. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 86 versus 100.
Push history: LoopForge 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 176 for LoopForge (0.060 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for LoopForge and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both LoopForge (2,919 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: LoopForge is unpriced in this catalog, Windmill is open source.
Windmill is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 22 points (30 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
Windmill finishes ahead at 91.2 against LoopForge at 78.4, a 12.8 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 | LoopForge | Windmill |
|---|---|---|
| GitHub stars | 2,919 | 18,618 |
| Forks | 423 | 1,165 |
| Open issues | 176 | 889 |
| Adoption | 81 | 100 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 52 | 70 |
| License | 30 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 78.4 | 91.2 |
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
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,919 for LoopForge. The gap is 15,699 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both LoopForge and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 LoopForge scores 78.4. This page calls that a clear lead for Windmill.