A · leads
bruno
96.5
48,427 stars · MIT
Workflow Automation
bruno leads by 10.0 · clear
A · leads
96.5
48,427 stars · MIT
B
86.5
18,618 stars · AGPL-3.0
bruno versus Windmill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruno is written mainly in JavaScript; Windmill is written mainly in Rust. The composite score is 96.5 for bruno and 86.5 for Windmill.
bruno has 48,427 GitHub stars to Windmill's 18,618, a gap of 29,809 (2.60×). Forks are 3,115 for bruno and 1,165 for Windmill. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 88.
Push history: bruno 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 2,002 for bruno (0.041 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
bruno is listed as MIT, 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 bruno and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 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: bruno is open source, Windmill is open source.
bruno is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
bruno finishes ahead at 96.5 against Windmill at 86.5, a 10.0 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 | bruno | Windmill |
|---|---|---|
| GitHub stars | 48,427 | 18,618 |
| Forks | 3,115 | 1,165 |
| Open issues | 2,002 | 889 |
| Adoption | 100 | 91 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 70 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 86.5 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
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.
bruno has more GitHub stars: 48,427 versus 18,618 for Windmill. The gap is 29,809 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruno and Windmill as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruno is listed as MIT, 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.
bruno scores 96.5 and Windmill scores 86.5. This page calls that a clear lead for bruno.