A
skyvern
91.0
23,434 stars · AGPL-3.0
Workflow Automation
vagrant leads by 3.8 · narrow
A
91.0
23,434 stars · AGPL-3.0
B · leads
94.8
27,230 stars · MIT
skyvern versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. skyvern is written mainly in Python; vagrant is written mainly in Ruby. The composite score is 91.0 for skyvern and 94.8 for vagrant.
vagrant has 27,230 GitHub stars to skyvern's 23,434, a gap of 3,796 (1.16×). Forks are 2,246 for skyvern 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: skyvern 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 301 for skyvern (0.013 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 84 and 70; activity scores are 100 and 92.
skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for skyvern and 96 for vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both skyvern (23,434 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: skyvern is open source, vagrant is open source.
The lead is split. skyvern is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
vagrant finishes ahead at 94.8 against skyvern at 91.0, a 3.8 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | skyvern | vagrant |
|---|---|---|
| GitHub stars | 23,434 | 27,230 |
| Forks | 2,246 | 4,491 |
| Open issues | 301 | 760 |
| Adoption | 98 | 100 |
| Activity | 100 | 92 |
| Community | 92 | 100 |
| Issue health | 84 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.0 | 94.8 |
Automate browser based workflows with AI
Vagrant is a tool for building and distributing development environments.
vagrant has more GitHub stars: 27,230 versus 23,434 for skyvern. The gap is 3,796 stars.
skyvern was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both skyvern and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.
skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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.
vagrant scores 94.8 and skyvern scores 91.0. This page calls that a narrow lead for vagrant.