HashiCorp Terraform vs. HashiCorp Vagrant

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
HashiCorp Terraform
Score 8.5 out of 10
N/A
Terraform from HashiCorp is a cloud infrastructure automation tool that enables users to create, change, and improve production infrastructure, and it allows infrastructure to be expressed as code. It codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned. It is available Open Source, and via Cloud and Self-Hosted editions.
$0
HashiCorp Vagrant
Score 10.0 out of 10
N/A
Vagrant is a tool designed to create and configure lightweight, reproducible, and portable development environments. It leverages a declarative configuration file which describes all software requirements, packages, operating system configuration, and users.N/A
Pricing
HashiCorp TerraformHashiCorp Vagrant
Editions & Modules
Open Source
$0
Team & Governance
$20/user
per user/per month
Enterprise
Contact sales team
No answers on this topic
Offerings
Pricing Offerings
HashiCorp TerraformHashiCorp Vagrant
Free Trial
NoNo
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
HashiCorp TerraformHashiCorp Vagrant
Considered Both Products
HashiCorp Terraform
Chose HashiCorp Terraform
Dbt was fine, but you end up with an extremely bloated repo/project. Often where all of the models are the same, named similarly, and generally just doesn't adhere to the concept of DRY coding.
In Terraform we're able to template a lot of this work and dynamically generate …
Chose HashiCorp Terraform
HashiCorp Terraform is much better than Cloud Formation. For one, the language is just easier to use, but more importantly, the provider ecosystem is much better in HashiCorp Terraform than in Cloud Formation.
Chose HashiCorp Terraform
HashiCorp Terraform has Cloud agnostic capability to use with different cloud vendors and the ease of creating the code with minimal effort.
Chose HashiCorp Terraform
I'm beginning to look at Pulumi. In my opinion, it looks like it would be a good replacement for HashiCorp Terraform, and it has the advantage of configuration via scripting, rather than via HCL, which is HashiCorp Terraform configuration markup language. In my opinion, the …
Chose HashiCorp Terraform
We have used Vagrant to develop our application in a virtual box environment and prepare it to be packed with Packer. The image created from these two tools will be deployed by Terraform.

We are using Consul for service discovery and as a job locking so we don't have two jobs or …
Chose HashiCorp Terraform
CloudFormation is only for AWS so if you're trying to deploy to another cloud provider then Terraform is your product. Terraform has lots of public support so you can find answers to questions by Googling. CloudFormation is easy to view the resources/services that are …
Chose HashiCorp Terraform
Terraform was more preferred over ansible as it is considerably more intutive.
Chose HashiCorp Terraform
Actually both products work very well. We use Terraform for speed and Ansible for configuration management both products work really well together
Chose HashiCorp Terraform
Terraform is a large step ahead of the previous generation of infrastructure-as-code providers. I'd never go back to, e.g. Puppet or Chef, Ansible, etc. That said I think that Pulumi has a good chance of displaying it, in no small part because the Terraform language itself …
Chose HashiCorp Terraform
AWS CloudFormation is better if you just want to stick with AWS because it's integration with AWS is better, provides auto-rollback in case of failures, and has GUI to manage and view the stacks built. Terraform is better when we want to stay cloud-agnostic. Terraform is better …
Chose HashiCorp Terraform
I can't find these applications listed, but other IaC tools I have used include: AWS CloudFormation, Azure Resource Manager Templates, and GCP Cloud Deployment Templates. For a comparable tool, I have the most experience with CloudFormation.

Compared to CloudFormation, the first …
Chose HashiCorp Terraform
Chef and Terraform are not apples to apples because Chef is more focused on config management, whereas Terraform is more focused on provisioning. However, I can say that where they do overlap in configuration management is that Terraform is the preferred tool because it has an …
Chose HashiCorp Terraform
Terraform is the solid leader in the space. It allows you to do more then just provisioning within a pre-existing servers. It is more extensible and has more providers available than it competitors. It is also open source and more adopted by the community then some of the other …
Chose HashiCorp Terraform
Terraform is open source and has strong community support. It is cloud-agnostic versus competing products like AWS cloud formation, hence has a distinct advantage. The scripts once set up are easy for developers to administer during development, hence during production …
Chose HashiCorp Terraform
  • UI design and development always sticks when it comes to multiple or say 'n' number of same configurations.
  • It's very easy to download and execute
  • Provides cross platform support and it's reliable.
Chose HashiCorp Terraform
Terraform has made better choices in how their product works, is used over time, and can be integrated with.
Chose HashiCorp Terraform
Centralized and standard configuration. Ease of VM provisioning.
Chose HashiCorp Terraform
- Terraform syntax is much easier to read and learn than Cloud Formation. - Terraform already supports AWS as well as several other cloud providers. - Terraform is backed by a great and supportive open-source community.
Chose HashiCorp Terraform
Terraform shares the methodology of creating configuration files for your infrastructure with tools like CloudFormation. However, Terraform is cloud-agnostic unlike CloudFormation which is AWS specific.
Terraform can be used to maintain AWS and OpenStack clusters …
Chose HashiCorp Terraform
CloudFormation is the lingua franca of AWS. You certainly can't go wrong using it, but I like the syntax and open-source nature of Terraform. That's mostly a personal preference. I have not tried any other non-Amazon tools for provisioning AWS. And, of course, the AWS tools …
Chose HashiCorp Terraform
HashiCorp Terraform has more possibilities
HashiCorp Vagrant
Chose HashiCorp Vagrant
Docker has a few advantages, especially with the disk size bloat brought on by Vagrant's hosting an entire OS and project in a VM. It relies on native tools, however, and may not support every software.
Vagrant provides uniformity, efficiency and repeatability within team work …
Chose HashiCorp Vagrant
Fast[er] to implement than Docker. Even consuming a lot of resources, consume less resources than Docker. Cheaper than Azure, since [it] is free.
Chose HashiCorp Vagrant
I liked lando better because lando seemed extremely easy to setup compared to other VM's and it seemed faster though that project was simpler. Virtualbox I ran on windows and it has a gui and has often been slow. The vagrant boxes I used did well but had slightly more …
Chose HashiCorp Vagrant
Docker feels lighter, faster, but Vagrant offers better support across platforms, which is a must in my company where there are users on Linux, Mac OS and Windows.
Chose HashiCorp Vagrant
Virtualbox and VMware were easier products to set up but did not stack up against Vagrant with the customization and the ability to specifically test and work with our code base. Virtualbox and VMware were more generic solutions that may be easier but they did not fulfill the …
Chose HashiCorp Vagrant
MAMP is a much simpler solution than Vagrant. Pretty much anyone should be able to get MAMP up and running quickly, and it's much easier to maintain. However, MAMP is fairly limited to specific versions of software and runs within macOS, so it won't always completely be an …
Chose HashiCorp Vagrant
Previously I had used MAMP and DesktopServer. MAMP was constantly giving me MySQL problems and is frustrating in that it limits how many installs you can have. DesktopServers was a little better, but broke when i switched to High Sierra OSX. Their website and support were very …
Chose HashiCorp Vagrant
I like Vagrant much more than Docker. In my opinion it's easier and more flexible to configure a Vagrant machine how i like it compared to Docker. Of course Docker executes faster, but with Vagrant only the machine creation or booting process is slower, normally you don't …
Chose HashiCorp Vagrant
There's not much that I'm aware of that really does exactly what Vagrant does. Many of its tasks could be accomplished manually or via custom scripts. However, with Vagrant, automation is within easy grasp as well as a large community of experts who have pre-built solutions …
Chose HashiCorp Vagrant
Vagrant is a little different than other options out there. It blurs the lines between the server environment and the local environment. Options like MAMP and XAMPP allow a developer to run a local version of Apache, MySQL and PHP locally, but it's all based on the local …
Chose HashiCorp Vagrant
Vagrant is more of a meta-tool compared to traditional VM software. It provides a layer on top of VMware or VirtualBox. Configurations in a Vagrantfile are so much easier to manage than complete VMs.
Chose HashiCorp Vagrant
In comparison to Docker, Vagrant is a lot easier to create its [containers] boxes, than it is with Docker. Our company already dealt with and its devops team knew somewhat well the way of Vagrant, so it was quite natural to go Vagrant when trying to choose which would be our …
Chose HashiCorp Vagrant
By default Vagrant uses VirtualBox but compared to using VirtualBox directly, I've found using Vagrant makes things easier. For one, you can commit your Vagrant configuration to GitHub and manage changes that way. I'm not sure how you'd handle updated virtual machines to all …
Features
HashiCorp TerraformHashiCorp Vagrant
Configuration Management
Comparison of Configuration Management features of Product A and Product B
HashiCorp Terraform
7.9
Ratings
2% below category average
HashiCorp Vagrant
-
Ratings
Infrastructure Automation9.00 Ratings00 Ratings
Automated Provisioning8.70 Ratings00 Ratings
Parallel Execution6.30 Ratings00 Ratings
Node Management7.70 Ratings00 Ratings
Reporting & Logging7.80 Ratings00 Ratings
Version Control8.10 Ratings00 Ratings
Best Alternatives
HashiCorp TerraformHashiCorp Vagrant
Small Businesses
HashiCorp Vagrant
HashiCorp Vagrant
Score 10.0 out of 10
HashiCorp Terraform
HashiCorp Terraform
Score 8.5 out of 10
Medium-sized Companies
Ansible
Ansible
Score 9.2 out of 10
Ansible
Ansible
Score 9.2 out of 10
Enterprises
Ansible
Ansible
Score 9.2 out of 10
Ansible
Ansible
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
HashiCorp TerraformHashiCorp Vagrant
Likelihood to Recommend
8.4
(0 ratings)
8.0
(0 ratings)
Likelihood to Renew
-
(0 ratings)
9.0
(0 ratings)
Usability
8.1
(0 ratings)
5.5
(0 ratings)
Performance
9.4
(0 ratings)
-
(0 ratings)
Support Rating
7.4
(0 ratings)
-
(0 ratings)
Ease of integration
9.2
(0 ratings)
-
(0 ratings)
User Testimonials
HashiCorp TerraformHashiCorp Vagrant
Likelihood to Recommend
8 because it's currently best-in-class and is completely essential to use in contrast to not expressing your infrastructure as code. That said, new contenders are nipping at its heels, and I expect stronger tools to emerge in the coming years. Hopefully the Terraform team is able to keep pace.
Read full review
If you're writing software, particularly software that depends on other services (web servers or databases for example) then Vagrant is great. I know some people skip Vagrant and just set up virtual machines on their own, but I've found that Vagrant streamlines the process nicely and makes it easy to update or swap out versions. If you're a web developer (which I am) it's amazing. I can have several boxes configured for my different projects and I just spin them up or down based on what I'm working on. One scenario where this might not be ideal is if you're running Vagrant on a computer that has limited resources. Since you're running a virtual machine with its own operating system and such you'll want a host computer with enough RAM, hard drive space and CPU to run the virtual machine properly without killing the performance of the host. The virtual disks can also take up a lot of space if you're not careful so if you have many virtual machines provisioned and don't clean up the old ones that you're not using, you may find that your hard drive is full. Each of my Linux servers take up about 10GB of disk space.
Read full review
Pros
  • Terraform is cloud agnostic. Just select the suitable provider for the cloud and it will do the job.
  • Templating is possible to make the Terraform templates reusable.
  • Variables can be created to make the templates generic so that it can be reused for different environments or resources.
Read full review
  • Easy to create machines with different OS's, list of them can be found from Vagrant's website with configuration details.
  • Flexible configuration, user can determine what software will be pre-installed to machine. Saves time because it doesn't need to be done manually every time.
  • Easily manage full environments, not just single machines, with single command.
Read full review
Cons
  • The errors generated by the plan and preview commands are pretty cryptic, it can be hard for newcomers to the scripting language to understand how to address problems.
  • Access controls around workspaces is limited which makes it harder to secure reduce the scope of teams ability.
  • Analytics around user usage, applies and plans would be helpful for managemenet.
Read full review
  • Learning curve is steep - It can be challenging for someone to set up initially. After some coaching, the basics come pretty quickly though.
  • Relies on external Virtual Machine applications - It would be great if Vagrant itself could run the virtual machine instead of leaning on other virtualization software. This is a small detail, but would make setup simple.
  • Better support for running
Read full review
Likelihood to Renew
No answers on this topic
Vagrant is fast, versatile and does exactly what we need it to do: spin up virtual servers for local development fast and without trouble.
Read full review
Usability
I love Terraform and I think it has done some great things for people that are working to automate their provisioning processes and also for those that are in the process of moving to the cloud or managing cloud resources. There are some quirks to HCL that take a little bit of getting used to and give picking up Terraform a little bit of a learning curve, thus the rating
Read full review
A GUI would be nice for entry level users.
Read full review
Performance
Terraform's performance is quite amazing when it comes to deployment of resources in AWS. Of course, the deployment times depend on various parameters like the number of resources to deploy and different regions to deploy. Terraform cannot control that. The only minor drawback probably shows up when a terraform job is terminated mid way. Then in many cases, time-consuming manual cleanup is required.
Read full review
No answers on this topic
Support Rating
Terraform is community driven but does offer support for it's Enterprise product. When contacting the team at HashiCorp we have always gotten resolution to our issues. They have been very responsive in returning our calls and answering our questions as they come up. We are currently using the open source model.
Read full review
No answers on this topic
Alternatives Considered
dbt was fine, but you end up with an extremely bloated repo/project. Often where all of the models are the same, named similarly, and generally just doesn't adhere to the concept of DRY coding. In Terraform we're able to template a lot of this work and dynamically generate assets based on variables instead.
Read full review
Docker has a few advantages, especially with the disk size bloat brought on by Vagrant's hosting an entire OS and project in a VM. It relies on native tools, however, and may not support every software. Vagrant provides uniformity, efficiency and repeatability within team work and for deployment and testing.
Read full review
Return on Investment
  • Using code, we are able to build and deploy cloud resources faster and more consistently than producing the same resources in the console manually.
  • For applications that share architectures, we can reuse code to expedite development. We can also do the same with modules that are shared across the organization.
  • By defining all of our resources as code, we can deploy complete environments with "batteries included." For example, we can use code that spins up servers in a cloud provider and at the same time, creates monitors with in our monitoring provider. Likewise, when the servers are decommissioned, the monitors are decommed along with them. In the past, the creation and decom of the monitors would have been a disjointed, manual step. With Terraform we get it all with one "terraform apply."
Read full review
  • Saved lots of time by being able to set up a local env quickly
  • Occasionally made troubleshooting bugs harder than it would have been using native Linux
  • Clients had issues setting it up, which may have provided us some security in keeping their business
Read full review
ScreenShots

HashiCorp Terraform Screenshots

Screenshot of Terraform StateScreenshot of Terraform RunsScreenshot of Terraform VariablesScreenshot of Terraform WorkspacesScreenshot of Terraform Cost Estimation