Skip to content
DevUtils Online

Workflow Automation

automa vs vagrant

vagrant leads by 25.9 · decisive

A

automa

68.9

21,723 stars · license n/a

B · leads

vagrant

94.8

27,230 stars · MIT

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

vagrant has 27,230 GitHub stars to automa's 21,723, a gap of 5,507 (1.25×). Forks are 2,341 for automa and 4,491 for vagrant. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 92 versus 100.

Push history: automa was last pushed on 02 March 2026 (260 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 379 for automa (0.017 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 84 and 70; activity scores are 36 and 92.

automa 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 automa 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). automa is not (21,723 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: automa is unpriced in this catalog, vagrant is open source.

The lead is split. automa 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.8 against automa at 68.9, a 25.9 point decisive 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.

automa versus vagrant metrics
Signal automa vagrant
GitHub stars 21,723 27,230
Forks 2,341 4,491
Open issues 379 760
Adoption 98 100
Activity 36 92
Community 92 100
Issue health 84 70
License 30 96
Self-hosting 35 100
Composite 68.9 94.8

Questions this page answers

Which has more GitHub stars, automa or vagrant?

vagrant has more GitHub stars: 27,230 versus 21,723 for automa. The gap is 5,507 stars.

Which was updated more recently, automa or vagrant?

vagrant was pushed more recently: 12 November 2026 versus 02 March 2026 for automa. That is 255 days apart.

Can I self-host both automa and vagrant?

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

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

automa 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 automa vs vagrant score?

vagrant scores 94.8 and automa scores 68.9. This page calls that a decisive lead for vagrant.

Related comparisons