Skip to content
DevUtils Online

Workflow Automation

budibase vs vagrant

vagrant leads by 11.0 · clear

A

budibase

83.6

28,420 stars · license n/a

B · leads

vagrant

94.6

27,230 stars · MIT

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

budibase has 28,420 GitHub stars to vagrant's 27,230, a gap of 1,190 (1.04×). Forks are 2,237 for budibase and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 92 versus 100.

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

budibase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for budibase and 96 for vagrant. This is a procurement signal, not legal advice.

Only vagrant is marked self-hostable here (27,230 stars, deploy score 100). budibase is not (28,420 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: budibase is unpriced in this catalog, vagrant is open source.

The lead is split. budibase is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

vagrant finishes ahead at 94.6 against budibase at 83.6, a 11.0 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.

budibase versus vagrant metrics
Signal budibase vagrant
GitHub stars 28,420 27,230
Forks 2,237 4,491
Open issues 318 760
Adoption 100 100
Activity 100 92
Community 92 100
Issue health 84 70
License 30 96
Self-hosting 35 100
Composite 83.6 94.6

Questions this page answers

Which has more GitHub stars, budibase or vagrant?

budibase has more GitHub stars: 28,420 versus 27,230 for vagrant. The gap is 1,190 stars.

Which was updated more recently, budibase or vagrant?

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

Can I self-host both budibase and vagrant?

Only vagrant is marked self-hostable. budibase is not.

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

budibase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 budibase vs vagrant score?

vagrant scores 94.6 and budibase scores 83.6. This page calls that a clear lead for vagrant.

Related comparisons