A
Obtainium
85.4
21,625 stars · GPL-3.0
Workflow Automation
vagrant leads by 9.4 · clear
A
85.4
21,625 stars · GPL-3.0
B · leads
94.8
27,230 stars · MIT
Obtainium versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Obtainium is written mainly in Dart; vagrant is written mainly in Ruby. The composite score is 85.4 for Obtainium and 94.8 for vagrant.
vagrant has 27,230 GitHub stars to Obtainium's 21,625, a gap of 5,605 (1.26×). Forks are 704 for Obtainium and 4,491 for vagrant. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 78 versus 100.
Push history: Obtainium was last pushed on 01 November 2026 (16 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 403 for Obtainium (0.019 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 84 and 70; activity scores are 78 and 92.
Obtainium is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. License scores in this pair are 64 for Obtainium and 96 for vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both Obtainium (21,625 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: Obtainium is open source, vagrant is open source.
The lead is split. Obtainium is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on license flexibility (96 to 64). Choose the dimension a rollout cannot compromise on.
vagrant finishes ahead at 94.8 against Obtainium at 85.4, a 9.4 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 | Obtainium | vagrant |
|---|---|---|
| GitHub stars | 21,625 | 27,230 |
| Forks | 704 | 4,491 |
| Open issues | 403 | 760 |
| Adoption | 98 | 100 |
| Activity | 78 | 92 |
| Community | 78 | 100 |
| Issue health | 84 | 70 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 85.4 | 94.8 |
Get Android app updates straight from the source.
Vagrant is a tool for building and distributing development environments.
vagrant has more GitHub stars: 27,230 versus 21,625 for Obtainium. The gap is 5,605 stars.
vagrant was pushed more recently: 12 November 2026 versus 01 November 2026 for Obtainium. That is 11 days apart.
Yes. This catalog marks both Obtainium and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.
Obtainium is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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.
vagrant scores 94.8 and Obtainium scores 85.4. This page calls that a clear lead for vagrant.