Skip to content
DevUtils Online

Workflow Automation

InstaPy vs vagrant

vagrant leads by 8.5 · clear

A

InstaPy

86.3

18,414 stars · GPL-3.0

B · leads

vagrant

94.8

27,230 stars · MIT

InstaPy versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. InstaPy is written mainly in Python; vagrant is written mainly in Ruby. The composite score is 86.3 for InstaPy and 94.8 for vagrant.

vagrant has 27,230 GitHub stars to InstaPy's 18,414, a gap of 8,816 (1.48×). Forks are 3,896 for InstaPy and 4,491 for vagrant. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 98 versus 100.

Push history: InstaPy was last pushed on 26 October 2026 (21 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 586 for InstaPy (0.032 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 70 and 70; activity scores are 78 and 92.

InstaPy 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 InstaPy and 96 for vagrant. This is a procurement signal, not legal advice.

In Workflow Automation, both InstaPy (18,414 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: InstaPy is open source, vagrant is open source.

vagrant is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is license flexibility at 32 points (64 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

vagrant finishes ahead at 94.8 against InstaPy at 86.3, a 8.5 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

InstaPy versus vagrant metrics
Signal InstaPy vagrant
GitHub stars 18,414 27,230
Forks 3,896 4,491
Open issues 586 760
Adoption 96 100
Activity 78 92
Community 98 100
Issue health 70 70
License 64 96
Self-hosting 100 100
Composite 86.3 94.8

Questions this page answers

Which has more GitHub stars, InstaPy or vagrant?

vagrant has more GitHub stars: 27,230 versus 18,414 for InstaPy. The gap is 8,816 stars.

Which was updated more recently, InstaPy or vagrant?

vagrant was pushed more recently: 12 November 2026 versus 26 October 2026 for InstaPy. That is 16 days apart.

Can I self-host both InstaPy and vagrant?

Yes. This catalog marks both InstaPy and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, InstaPy or vagrant?

InstaPy 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.

Who wins the InstaPy vs vagrant score?

vagrant scores 94.8 and InstaPy scores 86.3. This page calls that a clear lead for vagrant.

Related comparisons