A · level
leon
94.6
17,690 stars · MIT
Workflow Automation
Too close to call · 94.6 to 94.8
A · level
94.6
17,690 stars · MIT
B · level
94.8
27,230 stars · MIT
leon versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. leon is written mainly in TypeScript; vagrant is written mainly in Ruby. The composite score is 94.6 for leon and 94.8 for vagrant.
vagrant has 27,230 GitHub stars to leon's 17,690, a gap of 9,540 (1.54×). Forks are 1,484 for leon and 4,491 for vagrant. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 87 versus 100.
Push history: leon 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 118 for leon (0.007 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 84 and 70; activity scores are 100 and 92.
Both leon 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 leon (17,690 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: leon is open source, vagrant is open source.
The lead is split. leon is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on fork community (100 to 87). Choose the dimension a rollout cannot compromise on.
Composite score: leon 94.6, vagrant 94.8. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | leon | vagrant |
|---|---|---|
| GitHub stars | 17,690 | 27,230 |
| Forks | 1,484 | 4,491 |
| Open issues | 118 | 760 |
| Adoption | 96 | 100 |
| Activity | 100 | 92 |
| Community | 87 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.6 | 94.8 |
🧠 Leon is your open-source personal assistant.
Vagrant is a tool for building and distributing development environments.
vagrant has more GitHub stars: 27,230 versus 17,690 for leon. The gap is 9,540 stars.
leon was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both leon and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.
leon 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.
Neither tool clears a one-point margin. leon scores 94.6 and vagrant scores 94.8.