DevOps & CI/CDIBM (HashiCorp)

HashiCorp Terraform Review 2026

4.5/ 5.0 · editorial estimate
Vendor
IBM (HashiCorp Inc.)
Pricing
CLI free; HCP Terraform from $0; Plus $0.00014/RU
Deployment
CLI (any OS), HCP Terraform SaaS, Terraform Enterprise self-hosted
Best For
Multi-cloud and hybrid infrastructure-as-code at any scale
Industries
Financial Services, Telecom, Public Sector, Retail
Implementation
Days for CLI; 1–3 months for Enterprise patterns

Overview

Terraform is the most widely used infrastructure-as-code tool, originally released by HashiCorp in 2014. The CLI describes infrastructure in HashiCorp Configuration Language (HCL) or JSON, computes a diff against the current state, and applies changes through provider plug-ins. More than 4,000 providers are published in the Terraform Registry, covering all major hyperscalers, SaaS platforms, on-premise hypervisors, and observability tooling. HashiCorp was acquired by IBM in February 2025 for approximately $6.4 billion; Terraform development continues from the same engineering organisation, now under IBM Software.

The Terraform CLI was relicensed in August 2023 from the Mozilla Public License (MPL) to the Business Source License (BSL), prompting the Linux Foundation to fork the project as OpenTofu. The CLI itself remains free of charge and most published modules and providers are compatible with both. HashiCorp's commercial offerings are HCP Terraform (SaaS, formerly Terraform Cloud) and Terraform Enterprise (self-hosted). Both add remote state, policy enforcement, dynamic credentials, run pipelines, and team-level RBAC. Pricing moved to a Resource Under Management (RUM) model in 2024, replacing the earlier per-user pricing for new customers.

Key Features

  • Declarative infrastructure-as-code in HashiCorp Configuration Language
  • 4,000+ providers covering AWS, Azure, GCP, Kubernetes, Datadog, Snowflake, and more
  • Plan and apply lifecycle with explicit, reviewable diff output
  • State management with local, remote, and HCP Terraform backends
  • Workspaces and remote runs for isolated environment management
  • Sentinel policy-as-code and Open Policy Agent integration on commercial tiers
  • Dynamic provider credentials via OIDC for AWS, Azure, GCP, and Vault
  • Drift detection and continuous validation on HCP Terraform Plus
  • Private module registry and curated provider mirror in commercial tiers
  • Cost estimation through Infracost integration or HashiCorp's native module
  • VCS integrations with GitHub, GitLab, Bitbucket, and Azure DevOps
  • Terraform Enterprise self-hosted appliance for air-gapped or sovereign environments

Pricing

TierModelCost
Terraform CLIOpen source under BSL$0 (free for any production use; competitive use restrictions apply)
HCP Terraform FreePer Resource Under Management$0 for the first 500 resources/month
HCP Terraform StandardPay-as-you-go$0.00014 per resource per hour above 500 free resources
HCP Terraform PlusAnnual contractQuote-based; adds drift detection, continuous validation, no-code modules
Terraform EnterpriseAnnual subscriptionSix-figure annual contracts typical for self-hosted Enterprise

Pricing verified May 2026 on hashicorp.com. Resource Under Management (RUM) pricing replaced per-user pricing for new HCP Terraform customers in 2024; legacy team-based pricing remains available on renewal for existing customers.

Strengths

  • Largest provider ecosystem in infrastructure-as-code by a wide margin
  • Single language (HCL) covers compute, networking, IAM, observability, and SaaS
  • Plan/apply workflow gives reviewable, auditable changes — well suited to change control
  • Strong commercial governance: Sentinel policy, RBAC, audit log, dynamic credentials
  • Skills are widely available — Terraform is a near-default IaC skill in DevOps hiring

Limitations

  • BSL relicensing has unsettled some buyers; review competitive-use clauses with legal
  • State file management at scale is a persistent operational burden without HCP Terraform
  • RUM pricing can scale unexpectedly for organisations with many small resources (e.g., DNS records, IAM roles)
  • HCL has limitations for complex programmatic logic compared to Pulumi or CDK
  • Module ecosystem quality varies widely; vetted private modules require ongoing maintenance

Alternatives

Linux Foundation MPL-licensed Terraform fork
4.3
IaC in TypeScript, Python, Go, C#, Java
4.4
Native AWS IaC in TypeScript or Python, compiles to CloudFormation
4.3
IaC orchestration platform supporting Terraform, OpenTofu, Pulumi
4.5
Terraform automation platform with policy and cost controls
4.4

Compare Terraform

Terraform vs OpenTofu → Terraform vs Pulumi → Terraform vs AWS CDK →

Frequently Asked Questions

Does the BSL relicensing affect our right to use Terraform?
For the vast majority of enterprise users — those running Terraform to manage their own infrastructure — the BSL has no practical impact. The licence restricts use of the Terraform source code by direct competitors offering a competing commercial product. Most legal teams have reviewed and cleared continued use. Buyers concerned about future licence changes commonly evaluate OpenTofu in parallel.
How does HCP Terraform RUM pricing actually scale?
RUM counts each distinct resource in Terraform state every hour. A typical mid-market estate (3,000 resources across dev, staging, production) consumes roughly 2.5 million resource-hours per month, costing approximately $350 at the $0.00014/hour rate. Estates heavy in low-cost resources like DNS records or IAM policies can scale higher than expected; modelling RUM consumption before contract is essential.
Should new projects pick Terraform or OpenTofu?
OpenTofu is a credible drop-in replacement and the right choice for organisations with strong open-source preferences or that want to avoid BSL exposure. Terraform remains the right pick when HCP Terraform's commercial features (drift detection, policy, no-code modules, dynamic credentials) are needed and the BSL is acceptable. Module and provider compatibility between the two is broad but not guaranteed indefinitely.
What is the right way to manage Terraform state at scale?
Local state files do not scale beyond single-developer prototypes. The standard pattern uses remote state — HCP Terraform, Terraform Enterprise, S3 with DynamoDB locking, or an alternative such as Spacelift or env0. State should be split across many small workspaces (typically by environment, region, and application) rather than maintained in a small number of monolithic state files.
Published: · Last updated:

Get a free, independent vendor shortlist

Tell us what you're evaluating and we'll send a tailored shortlist of vendors that actually fit — no vendor funding, no pay-to-play.

6,000+ vendors · 893 comparisons · 48 country guides · Independent & vendor-neutral

Get a Free Shortlist →