Skip to content
DevUtils Online

Workflow Automation

prefect vs vagrant

Too close to call · 95.2 to 94.8

A · level

prefect

95.2

24,170 stars · Apache-2.0

B · level

vagrant

94.8

27,230 stars · MIT

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

vagrant has 27,230 GitHub stars to prefect's 24,170, a gap of 3,060 (1.13×). Forks are 2,668 for prefect and 4,491 for vagrant. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 94 versus 100.

Push history: prefect 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 876 for prefect (0.036 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 70 and 70; activity scores are 100 and 92.

prefect is listed as Apache-2.0, 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. License scores in this pair are 96 for prefect and 96 for vagrant. This is a procurement signal, not legal advice.

In Workflow Automation, both prefect (24,170 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: prefect is open source, vagrant is open source.

The lead is split. prefect is furthest ahead on recent activity (100 to 92), while vagrant is furthest ahead on fork community (100 to 94). Choose the dimension a rollout cannot compromise on.

Composite score: prefect 95.2, 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.

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.

prefect versus vagrant metrics
Signal prefect vagrant
GitHub stars 24,170 27,230
Forks 2,668 4,491
Open issues 876 760
Adoption 99 100
Activity 100 92
Community 94 100
Issue health 70 70
License 96 96
Self-hosting 100 100
Composite 95.2 94.8

Questions this page answers

Which has more GitHub stars, prefect or vagrant?

vagrant has more GitHub stars: 27,230 versus 24,170 for prefect. The gap is 3,060 stars.

Which was updated more recently, prefect or vagrant?

prefect was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.

Can I self-host both prefect and vagrant?

Yes. This catalog marks both prefect 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, prefect or vagrant?

prefect is listed as Apache-2.0, 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.

Who wins the prefect vs vagrant score?

Neither tool clears a one-point margin. prefect scores 95.2 and vagrant scores 94.8.

Related comparisons