StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Infrastructure as a Service
  4. Virtual Machine Management
  5. Terraform vs Vagrant

Terraform vs Vagrant

OverviewDecisionsComparisonAlternatives

Overview

Vagrant
Vagrant
Stacks11.9K
Followers7.8K
Votes1.5K
Terraform
Terraform
Stacks22.9K
Followers14.7K
Votes344
GitHub Stars47.0K
Forks10.1K

Terraform vs Vagrant: What are the differences?

Terraform and Vagrant are both tools used in the realm of infrastructure provisioning and management. Terraform focuses on infrastructure as code and automating the creation of resources, while Vagrant simplifies development environments setup. Here are the key differences between Terraform and Vagrant:

  1. Infrastructure Provisioning vs. Development Environments: Terraform is primarily used for provisioning and managing infrastructure resources in cloud environments. It helps define and automate the creation of resources like virtual machines, networks, and storage. Vagrant, on the other hand, is specifically designed to create and manage development environments, allowing developers to quickly set up local virtual machines for testing and development purposes.

  2. Infrastructure as Code vs. Development Environment Configuration: Terraform follows the infrastructure as code (IAC) approach, enabling users to define infrastructure resources using a declarative language. Vagrant focuses on configuring development environments using scripts and configuration files, providing a standardized setup for development teams.

  3. Cloud-Agnostic vs. Virtualization: Terraform supports multiple cloud providers and can be used to provision resources in various cloud platforms. Vagrant is more focused on virtualization, creating local development environments using tools like VirtualBox or Docker.

  4. Resource Creation vs. Environment Replication: Terraform's main goal is to create and manage infrastructure resources like servers, databases, and networking components. Vagrant's primary purpose is to replicate development environments, ensuring consistency across team members and improving collaboration.

  5. Use Case and Audience: Terraform is suitable for DevOps and infrastructure teams that need to manage and automate cloud resources at scale. Vagrant targets developers who want to create reproducible development environments quickly and efficiently.

  6. Workflow Integration: Terraform is often integrated into continuous integration and continuous deployment (CI/CD) pipelines to ensure consistent infrastructure changes. Vagrant's integration is more focused on providing a consistent development environment across team members' local machines.

In summary, Terraform is centered around provisioning and managing infrastructure resources in cloud environments using an infrastructure as code approach, while Vagrant simplifies the setup of consistent development environments for individual developers using virtualization technology.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Vagrant, Terraform

Sung Won
Sung Won

Nov 4, 2019

DecidedonGoogle Cloud IoT CoreGoogle Cloud IoT CoreTerraformTerraformPythonPython

Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

Check Out My Architecture: CLICK ME

Check out the GitHub repo attached

2.25M views2.25M
Comments
Timothy
Timothy

SRE

Mar 20, 2020

Decided

I personally am not a huge fan of vendor lock in for multiple reasons:

  • I've seen cost saving moves to the cloud end up costing a fortune and trapping companies due to over utilization of cloud specific features.
  • I've seen S3 failures nearly take down half the internet.
  • I've seen companies get stuck in the cloud because they aren't built cloud agnostic.

I choose to use terraform for my cloud provisioning for these reasons:

  • It's cloud agnostic so I can use it no matter where I am.
  • It isn't difficult to use and uses a relatively easy to read language.
  • It tests infrastructure before running it, and enables me to see and keep changes up to date.
  • It runs from the same CLI I do most of my CM work from.
385k views385k
Comments
Daniel
Daniel

May 4, 2020

Decided

Because Pulumi uses real programming languages, you can actually write abstractions for your infrastructure code, which is incredibly empowering. You still 'describe' your desired state, but by having a programming language at your fingers, you can factor out patterns, and package it up for easier consumption.

426k views426k
Comments

Detailed Comparison

Vagrant
Vagrant
Terraform
Terraform

Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.

With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Boxes;Up And SSH;Synced Folders;Provisioning;Networking;Share;Teardown;Rebuild;Providers
Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.;Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.;Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.;Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what Terraform will change and in what order, avoiding many possible human errors
Statistics
GitHub Stars
-
GitHub Stars
47.0K
GitHub Forks
-
GitHub Forks
10.1K
Stacks
11.9K
Stacks
22.9K
Followers
7.8K
Followers
14.7K
Votes
1.5K
Votes
344
Pros & Cons
Pros
  • 352
    Development environments
  • 290
    Simple bootstraping
  • 237
    Free
  • 139
    Boxes
  • 130
    Provisioning
Cons
  • 2
    Multiple VMs quickly eat up disk space
  • 2
    Can become v complex w prod. provisioner (Salt, etc.)
  • 1
    Development environment that kills your battery
Pros
  • 121
    Infrastructure as code
  • 73
    Declarative syntax
  • 45
    Planning
  • 28
    Simple
  • 24
    Parallelism
Cons
  • 1
    Doesn't have full support to GKE
Integrations
Amazon EC2
Amazon EC2
Microsoft Azure
Microsoft Azure
DigitalOcean
DigitalOcean
HP Cloud Compute
HP Cloud Compute
Joyent Cloud
Joyent Cloud
Rackspace Cloud Servers
Rackspace Cloud Servers
SoftLayer
SoftLayer
VirtualBox
VirtualBox
Heroku
Heroku
Amazon EC2
Amazon EC2
CloudFlare
CloudFlare
DNSimple
DNSimple
Microsoft Azure
Microsoft Azure
Consul
Consul
Equinix Metal
Equinix Metal
DigitalOcean
DigitalOcean
OpenStack
OpenStack
Google Compute Engine
Google Compute Engine

What are some alternatives to Vagrant, Terraform?

Ansible

Ansible

Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.

Chef

Chef

Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.

Capistrano

Capistrano

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

Puppet Labs

Puppet Labs

Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.

Salt

Salt

Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.

boot2docker

boot2docker

boot2docker is a lightweight Linux distribution based on Tiny Core Linux made specifically to run Docker containers. It runs completely from RAM, weighs ~27MB and boots in ~5s (YMMV).

Fabric

Fabric

Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution.

AWS OpsWorks

AWS OpsWorks

Start from templates for common technologies like Ruby, Node.JS, PHP, and Java, or build your own using Chef recipes to install software packages and perform any task that you can script. AWS OpsWorks can scale your application using automatic load-based or time-based scaling and maintain the health of your application by detecting failed instances and replacing them. You have full control of deployments and automation of each component

Otto

Otto

Otto automatically builds development environments without any configuration; it can detect your project type and has built-in knowledge of industry-standard tools to setup a development environment that is ready to go. When you're ready to deploy, otto builds and manages an infrastructure, sets up servers, builds, and deploys the application.

libvirt

libvirt

It is an open-source API, daemon and management tool for managing platform virtualization. It can be used to manage KVM, Xen, VMware ESXi, QEMU and other virtualization technologies.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana