Skip to content
DevUtils Online

Workflow Automation

sim vs vagrant

sim leads by 3.3 · narrow

A · leads

sim

97.7

30,151 stars · Apache-2.0

B

vagrant

94.4

27,230 stars · MIT

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

sim has 30,151 GitHub stars to vagrant's 27,230, a gap of 2,921 (1.11×). Forks are 3,915 for sim and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 98 versus 100.

Push history: sim 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 330 for sim (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.

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

In Workflow Automation, both sim (30,151 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: sim is open source, vagrant is open source.

The lead is split. sim is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on fork community (100 to 98). Choose the dimension a rollout cannot compromise on.

sim finishes ahead at 97.7 against vagrant at 94.4, a 3.3 point narrow 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.

sim versus vagrant metrics
Signal sim vagrant
GitHub stars 30,151 27,230
Forks 3,915 4,491
Open issues 330 760
Adoption 100 99
Activity 100 92
Community 98 100
Issue health 84 70
License 96 96
Self-hosting 100 100
Composite 97.7 94.4

sim

Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, sim or vagrant?

sim has more GitHub stars: 30,151 versus 27,230 for vagrant. The gap is 2,921 stars.

Which was updated more recently, sim or vagrant?

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

Can I self-host both sim and vagrant?

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

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

sim scores 97.7 and vagrant scores 94.4. This page calls that a narrow lead for sim.

Related comparisons