Terraform Cloud
By HashiCorp
Terraform Cloud is HashiCorp's managed service for running Terraform infrastructure-as-code workflows, providing remote state storage, remote plan and apply execution, and collaboration features like policy enforcement and approval…
Definition
Terraform Cloud is HashiCorp's managed service for running Terraform infrastructure-as-code workflows, providing remote state storage, remote plan and apply execution, and collaboration features like policy enforcement and approval workflows. It removes the need for teams to self-manage Terraform state files and execution environments manually. It runs on top of the open-source Terraform CLI rather than replacing it, adding the collaboration, governance, and remote-execution layer that a team of more than one person typically needs once infrastructure-as-code moves beyond a single developer's laptop.
Overview
Terraform Cloud addresses the coordination problems that appear once infrastructure-as-code moves from a single developer's laptop to a team. Running the open-source Terraform CLI locally works fine for one person, but as soon as multiple engineers need to apply changes to the same infrastructure, questions arise about where the shared state file lives, how to prevent two people from applying conflicting changes at once, and how to keep cloud credentials from being scattered across individual machines. Terraform Cloud is HashiCorp's managed answer to those questions, layered on top of the same Terraform configuration language rather than replacing it. Mechanically, Terraform Cloud centralizes the state file with locking, so that a plan or apply operation from one workspace blocks conflicting concurrent operations rather than risking two engineers overwriting each other's changes, and it executes plan and apply runs remotely on HashiCorp's infrastructure rather than on an individual's machine, which also means cloud credentials used for provisioning do not need to be distributed to every developer's laptop. Work is organized into workspaces, typically one per distinct piece of infrastructure, which can be connected directly to a version control repository so that a pull request automatically triggers a plan. Compared to a self-managed alternative, such as storing Terraform state in an Amazon S3 bucket with a DynamoDB lock table, Terraform Cloud adds governance features that a purely storage-based backend does not provide: policy-as-code checks through Sentinel or Open Policy Agent that can block an apply violating organizational rules, and approval workflows requiring review before a change reaches production. Third-party alternatives like Spacelift or env0 aim at a similar space but are not built by HashiCorp itself. In practice, teams use Terraform Cloud to centralize state for a distributed group of engineers, automate infrastructure changes triggered by pull requests, enforce compliance policies automatically, and share reusable infrastructure modules through its private module registry, all without exposing sensitive cloud credentials to individual developer machines. The tradeoff is a degree of dependency on HashiCorp's own commercial platform and licensing decisions; some organizations, wary of that dependency or of licensing changes around Terraform itself, have moved toward the OpenTofu fork or a self-managed remote state backend instead, reserving Terraform Cloud for teams already comfortable operating within HashiCorp's broader product ecosystem. The practical choice for a team is usually between accepting HashiCorp's own hosted governance layer or assembling an equivalent set of capabilities from a self-managed backend plus a separate CI system, a tradeoff that generally favors Terraform Cloud once policy enforcement and approval workflows become organizational requirements rather than nice-to-haves.
Key Features
- Remote state storage with locking to prevent concurrent conflicts
- Remote execution of Terraform plan and apply operations
- Workspace-based organization tied to version control repositories
- Policy-as-code enforcement via Sentinel or OPA
- Approval workflows requiring review before infrastructure changes apply
- Private module registry for sharing reusable Terraform modules
- Free, team, and business pricing tiers with varying governance features
Use Cases
Alternatives
Frequently Asked Questions
From the Blog
AI Cloud Services: How Cloud Platforms Power Modern AI
AI cloud services let teams train, deploy, and scale machine learning models without owning specialized hardware. This guide explains what these platforms offer, how they differ, and how to choose the right one for a given project.
Read More Cloud & CybersecurityCloud Computing for Beginners: A Complete Guide
A comprehensive guide to cloud computing for beginners: a complete guide — written for learners at every level.
Read More Cloud & CybersecurityAWS vs Azure vs Google Cloud: Which to Learn?
A comprehensive guide to aws vs azure vs google cloud: which to learn? — written for learners at every level.
Read More Cloud & CybersecurityInfrastructure as Code Explained: Terraform Basics
Clicking through cloud consoles doesn't scale. Infrastructure as Code (IaC) lets you define, version, and automate your cloud resources in code. This guide explains IaC concepts and walks you through Terraform — the most widely used IaC tool.
Read More