---
title: Vagrant
canonical: https://saasranked.com/software/vagrant/
category: Virtual Machine Software
points: 50
rank: 10 of 12
facts_checked: 2026-10-09
---

# Vagrant

Command-line tool that builds and manages virtual machines from a text file, using VirtualBox, Hyper-V, Docker or another provider.

50 points out of 100. #10 of 12 virtual machine programs. Vendor: HashiCorp (IBM). Website: https://developer.hashicorp.com/vagrant

- Vagrant has no price: the Business Source License 1.1 allows production use unless you resell it as a competing hosted product [15].
- It runs on Windows (.msi), macOS and Linux, and ships with VirtualBox, Hyper-V and Docker support [2][3].
- It needs a separate provider such as VirtualBox or Hyper-V to run the virtual machine [10].
- The latest stable version, 2.4.9, is dated August 21, 2025 [2][17].
- The source is public, but the Business Source License 1.1 is not an open-source licence [15].

Verdict: Vagrant suits developers who want to describe a virtual machine in a file and recreate it on demand [1]. It costs nothing for work use under its licence [15]. The catch: it is a front end that depends on another hypervisor, its source licence is not open source, and its last release is from August 2025 [10][15][17]. Best for: Developers who want repeatable, scripted virtual machines.

## Points

| Criterion | Line | Value | Points | Note |
|---|---|---|---|---|
| Systems | Guest systems | None | 0/8 | Guests run only through a provider such as VirtualBox or Hyper-V, so none count for Vagrant itself [4][10]. |
| Systems | Also runs on other hosts | macOS, Linux | 4/4 | The install page lists macOS and Linux downloads next to Windows [2]. |
| Systems | Works on Windows Home | Not published | 0/5 | Not published on the install page or installation docs [2][14]. |
| Virtual machines | Snapshots | Yes | 8/8 | The vagrant snapshot command saves and restores point-in-time states, if the provider supports it [5]. |
| Virtual machines | Virtual TPM and Secure Boot | Not published | 0/5 | Not published on the provider configuration pages [11][13]. |
| Virtual machines | Network modes | NAT, Bridged, Host-only | 6/6 | The overview describes a NAT device [6]. The VirtualBox page says private networks are host-only by default [7]. The public networks page describes a bridge option that picks the host interface to bridge to [8]. |
| Virtual machines | Nested virtualization | Not published | 0/4 | The Hyper-V provider page lists enable_virtualization_extensions ("Enable virtualization extensions for the virtual CPUs") but does not say a guest can run its own virtual machines [11]. |
| Virtual machines | Starts from a ready-made image | Yes | 4/4 | vagrant init uses a box from the public Vagrant Cloud catalog; HashiCorp publishes a basic Ubuntu box [10]. |
| Devices | 3D graphics for guests | Not published | 0/8 | Not published on the provider configuration pages [11][13]. |
| Devices | USB devices in the guest | Not published | 0/6 | Not published on the provider configuration pages [11][13]. |
| Devices | Shared folders | Yes | 6/6 | Synced folders sync a host folder to the guest; the project folder is shared at /vagrant by default [9]. |
| Devices | Shared clipboard | Not published | 0/4 | Not published on the provider configuration pages [11][13]. |
| Openness and upkeep | Open source | No | 0/6 | The repository licence is Business Source License 1.1, a source-available licence [15]. |
| Openness and upkeep | Security advisories published | Yes | 4/4 | HashiCorp's security bulletins include HCSEC-2023-31, "Vagrant's Windows Installer Allowed Directory Junction Write" (October 27, 2023, fixed in Vagrant 2.4.0) [18]. The GitHub repository has a security policy and lists no published advisories of its own [16]. |
| Openness and upkeep | Updated in the last 12 months | No | 0/4 | Latest stable version 2.4.9 is dated August 21, 2025, more than 12 months ago [2][17]. |
| Price | Free edition | Yes | 6/6 | No paid edition exists; the licence allows production use without charge [15]. |
| Price | Cheapest licence for work use | $0 | 12/12 | Free for work use under the Business Source License 1.1 grant [15]. |

## Plans

| Plan | Price | Per month (USD) |
|---|---|---|
| Vagrant | Free [15] | $0 |

The GitHub licence names IBM as licensor and lets you use Vagrant in production, except as a competing hosted or embedded offering [15]. Providers such as VMware must be bought separately and are not priced here [3].

## Strengths

- No charge; the licence grants production use unless you offer Vagrant as a competing hosted product [15].
- The snapshot command saves, lists and restores machine states when the provider supports them [5].
- Documents NAT, host-only and bridged-style networks, and synced folders that share a host folder with the guest [6][7][8][9].
- Boxes from a public catalog let vagrant init start a machine without hunting for an installer [10].

## Limits

- Vagrant cannot run a machine alone; you must install a provider such as VirtualBox first [10].
- The Business Source License 1.1 limits use that competes with IBM's paid versions, so it is not open source [15].
- The newest release is 2.4.9 from August 21, 2025 [2][17].
- With the Hyper-V provider, Vagrant cannot create or configure networks and ignores Vagrantfile network settings [12].
- The provider configuration pages do not list TPM, Secure Boot, USB, 3D graphics or clipboard sharing [11][13].

## Sources

1. [Vagrant by HashiCorp](https://developer.hashicorp.com/vagrant), HashiCorp, accessed 2026-10-09
2. [Install Vagrant](https://developer.hashicorp.com/vagrant/install), HashiCorp, accessed 2026-10-09
3. [Providers](https://developer.hashicorp.com/vagrant/docs/providers), HashiCorp, accessed 2026-10-09
4. [Machine settings](https://developer.hashicorp.com/vagrant/docs/vagrantfile/machine_settings), HashiCorp, accessed 2026-10-09
5. [vagrant snapshot](https://developer.hashicorp.com/vagrant/docs/cli/snapshot), HashiCorp, accessed 2026-10-09
6. [Networking overview](https://developer.hashicorp.com/vagrant/docs/networking), HashiCorp, accessed 2026-10-09
7. [VirtualBox provider networking](https://developer.hashicorp.com/vagrant/docs/providers/virtualbox/networking), HashiCorp, accessed 2026-10-09
8. [Public networks](https://developer.hashicorp.com/vagrant/docs/networking/public_network), HashiCorp, accessed 2026-10-09
9. [Synced folders](https://developer.hashicorp.com/vagrant/docs/synced-folders), HashiCorp, accessed 2026-10-09
10. [Boxes](https://developer.hashicorp.com/vagrant/docs/boxes), HashiCorp, accessed 2026-10-09
11. [Hyper-V provider configuration](https://developer.hashicorp.com/vagrant/docs/providers/hyperv/configuration), HashiCorp, accessed 2026-10-09
12. [Hyper-V provider limitations](https://developer.hashicorp.com/vagrant/docs/providers/hyperv/limitations), HashiCorp, accessed 2026-10-09
13. [VirtualBox provider configuration](https://developer.hashicorp.com/vagrant/docs/providers/virtualbox/configuration), HashiCorp, accessed 2026-10-09
14. [Installation](https://developer.hashicorp.com/vagrant/docs/installation), HashiCorp, accessed 2026-10-09
15. [hashicorp/vagrant LICENSE](https://raw.githubusercontent.com/hashicorp/vagrant/main/LICENSE), GitHub, accessed 2026-10-09
16. [hashicorp/vagrant security](https://github.com/hashicorp/vagrant/security), GitHub, accessed 2026-10-09
17. [Vagrant CHANGELOG](https://raw.githubusercontent.com/hashicorp/vagrant/main/CHANGELOG.md), GitHub, accessed 2026-10-09
18. [HCSEC-2023-31 - Vagrant's Windows Installer Allowed Directory Junction Write](https://discuss.hashicorp.com/t/hcsec-2023-31-vagrant-s-windows-installer-allowed-directory-junction-write/59568), HashiCorp, accessed 2026-10-09