Introduction

Terraform Cloud plans This article explains what Terraform Cloud is, the core problems it addresses, and how its different plans map to team size, governance needs, and automation requirements. You’ll also find a concise comparison between self-hosted Terraform and Terraform Cloud to help you decide which model fits your organization. Terraform Cloud is a managed platform for running Terraform that centralizes state management, secures sensitive data, enables team collaboration, and standardizes workflows and policy across organizations. It provides remote runs, stores state securely, shares variables and secrets, and integrates with VCS and CI/CD systems to enforce consistent provisioning practices. Each Terraform Cloud plan targets different levels of team maturity and operational requirements—ranging from individuals and small teams to large enterprises requiring advanced policy enforcement, SSO, and high-volume automation. Plans vary in concurrency limits, governance controls, audit logging, self-service modules, and support. Self-hosted Terraform (running the Terraform CLI and managing state yourself) offers maximum control and customization, useful for strict compliance, bespoke integrations, or air-gapped environments. Terraform Cloud reduces operational overhead by offering a managed control plane for state, runs, and collaboration, and is often preferable for teams that want to focus on infrastructure rather than managing tooling.

​

What is Terraform Cloud?

Terraform Cloud is HashiCorp’s SaaS offering that centralizes Terraform operations. Key capabilities include:

• Remote execution of Terraform plans and applies to remove sensitive credentials from local machines.
• Secure remote state storage with state locking and history.
• Encrypted variable and secret storage with granular workspace access controls.
• VCS integration (GitHub, GitLab, Bitbucket, Azure Repos) to drive runs from pull requests and commits.
• Policy enforcement with Sentinel or policy as code frameworks.
• Team collaboration features like role-based access control (RBAC), audit logs, and notifications.

​

Terraform Cloud Plans (Overview)

Below is a high-level comparison of the common Terraform Cloud plans and their target use cases. Note: Exact feature names, limits, and plan branding can change—refer to the official Terraform Cloud plans page for the latest details.

​

Feature highlights by capability

• State & runs: centralized state storage, locking, and remote execution.
• Secrets & variables: workspace-level variables, environment variables, and integrations with secret managers.
• Collaboration: workspace access controls, team management, and audit logs.
• Governance & policy: policy-as-code enforcement for compliance and security.
• Integrations: VCS providers, CI/CD tools, and provider plugins.

​

Self-hosted Terraform vs Terraform Cloud

The following table summarizes differences to help you evaluate which approach fits your needs:

​

When to choose each option

• Choose Terraform Cloud if:
  • You want a managed control plane for remote runs and central state.
  • Your team benefits from VCS-driven workflows, policy enforcement, and a private module registry.
  • You prefer reduced operational overhead and built-in collaboration.
• Choose self-hosted Terraform if:
  • You require full control over infrastructure, storage, and network isolation.
  • You need to run in environments with no external connectivity or strict data residency.
  • You plan extensive custom integrations or bespoke CI/CD flows not supported by Terraform Cloud.

​

Further reading and references

• Terraform Cloud documentation
• Terraform CLI documentation
• Using VCS with Terraform Cloud
• Terraform Enterprise overview