A · leads
bruno
95.9
48,427 stars · MIT
Workflow Automation
bruno leads by 2.9 · narrow
A · leads
95.9
48,427 stars · MIT
B
93.0
27,230 stars · MIT
bruno versus vagrant 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; vagrant is written mainly in Ruby. The composite score is 95.9 for bruno and 93.0 for vagrant.
bruno has 48,427 GitHub stars to vagrant's 27,230, a gap of 21,197 (1.78×). Forks are 3,115 for bruno and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 96 versus 100.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 70 and 70; activity scores are 100 and 92.
Both bruno and vagrant are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 stars) and vagrant (27,230 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, vagrant is open source.
The lead is split. bruno is furthest ahead on recent activity (100 to 92), while vagrant is furthest ahead on fork community (100 to 96). Choose the dimension a rollout cannot compromise on.
bruno finishes ahead at 95.9 against vagrant at 93.0, a 2.9 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 | bruno | vagrant |
|---|---|---|
| GitHub stars | 48,427 | 27,230 |
| Forks | 3,115 | 4,491 |
| Open issues | 2,002 | 760 |
| Adoption | 100 | 95 |
| Activity | 100 | 92 |
| Community | 96 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.9 | 93.0 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
Vagrant is a tool for building and distributing development environments.
bruno has more GitHub stars: 48,427 versus 27,230 for vagrant. The gap is 21,197 stars.
bruno was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both bruno and vagrant 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. vagrant 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
bruno scores 95.9 and vagrant scores 93.0. This page calls that a narrow lead for bruno.