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. Cloud Hosting
  4. Open Source Cloud
  5. OpenStack vs Terraform

OpenStack vs Terraform

OverviewDecisionsComparisonAlternatives

Overview

OpenStack
OpenStack
Stacks790
Followers1.2K
Votes138
Terraform
Terraform
Stacks22.9K
Followers14.7K
Votes344
GitHub Stars47.0K
Forks10.1K

OpenStack vs Terraform: What are the differences?

Key Differences between OpenStack and Terraform

Introduction

OpenStack and Terraform are two widely used tools in the field of cloud computing and infrastructure management. While OpenStack is an open-source cloud computing platform, Terraform is a tool for building, changing, and versioning infrastructure. Here are the key differences between OpenStack and Terraform:

  1. Architecture and Purpose: OpenStack is a complete cloud infrastructure platform that provides a wide range of services like compute, networking, and storage. It is designed to create and manage private and public clouds. On the other hand, Terraform is an infrastructure provisioning tool focused on managing and automating cloud infrastructure using a declarative configuration language.

  2. Language and Syntax: OpenStack primarily uses Python and XML for configuration and management. It utilizes a set of command-line tools (CLIs) and APIs to interact with its components. In contrast, Terraform uses its own declarative configuration language called HashiCorp Configuration Language (HCL). HCL allows users to define infrastructure resources and their relationships in a human-readable and consistent syntax across all supported cloud providers.

  3. Supported Cloud Providers: OpenStack is designed to be cloud provider agnostic and can work with a variety of hypervisors and storage backends. It supports multiple cloud providers like VMware, KVM, and Hyper-V. On the other hand, Terraform is compatible with a wide range of cloud providers, including major public cloud platforms like AWS, Azure, and Google Cloud. It provides a consistent provisioning experience across different providers.

  4. Scope and Extensibility: OpenStack encompasses a broad range of cloud services, including compute resources, networking, storage, and more. It allows users to build and manage an entire cloud infrastructure stack from scratch. Terraform, on the other hand, focuses on infrastructure provisioning and orchestration. It is not a full-stack cloud computing platform and does not provide services like identity management or dashboard interfaces. Instead, it focuses on integrating with existing cloud platforms to provision and manage resources.

  5. Community and Ecosystem: OpenStack has a large and active community of developers and contributors. It is backed by major technology companies and has a well-established ecosystem with a wide range of plugins and extensions. Terraform, being developed by HashiCorp, also has a strong community following and active development. It benefits from the larger HashiCorp ecosystem, which includes tools like Vault and Consul.

  6. Deployment Model: OpenStack is typically deployed on dedicated hardware infrastructure and requires significant upfront resources and expertise to set up and maintain. It is commonly used in private cloud deployments. In contrast, Terraform is a lightweight tool that can be deployed on any infrastructure and managed through version control systems like Git. It supports various deployment models, including public cloud, private cloud, and hybrid cloud environments.

In summary, OpenStack is a full-stack cloud infrastructure platform designed for creating and managing private and public clouds, while Terraform is a tool focused on infrastructure provisioning and management using a declarative configuration language. OpenStack supports multiple cloud providers and provides a wide range of services, while Terraform offers cloud agnostic provisioning and has a strong community following.

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 OpenStack, 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

OpenStack
OpenStack
Terraform
Terraform

OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface.

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.

Compute;Storage;Networking;Dashboard;Shared Services
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
790
Stacks
22.9K
Followers
1.2K
Followers
14.7K
Votes
138
Votes
344
Pros & Cons
Pros
  • 60
    Private cloud
  • 39
    Avoid vendor lock-in
  • 23
    Flexible in use
  • 7
    Industry leader
  • 5
    Robust architecture
Pros
  • 121
    Infrastructure as code
  • 73
    Declarative syntax
  • 45
    Planning
  • 28
    Simple
  • 24
    Parallelism
Cons
  • 1
    Doesn't have full support to GKE
Integrations
No integrations available
Heroku
Heroku
Amazon EC2
Amazon EC2
CloudFlare
CloudFlare
DNSimple
DNSimple
Microsoft Azure
Microsoft Azure
Consul
Consul
Equinix Metal
Equinix Metal
DigitalOcean
DigitalOcean
Google Compute Engine
Google Compute Engine

What are some alternatives to OpenStack, 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.

Apache CloudStack

Apache CloudStack

CloudStack is open source software designed to deploy and manage large networks of virtual machines, as a highly available, highly scalable Infrastructure as a Service (IaaS) cloud computing platform.

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

cPanel

cPanel

It is an industry leading hosting platform with world-class support. It is globally empowering hosting providers through fully-automated point-and-click hosting platform by hosting-centric professionals

Webmin

Webmin

It is a web-based interface for system administration for Unix. Using any modern web browser, you can setup user accounts, Apache, DNS, file sharing and much more. It removes the need to manually edit Unix configuration files.

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