HashiCorp Terraform

Name: HashiCorp Terraform
Brand: HashiCorp
Rating: 4.6 (304 reviews)

Leader

Do cloud right

Est 2012|Valuation $7.1B|Raised $1.6B

LinkedIn 325K|Website|Web traffic 892K|FTEs 2,000|HQ San Francisco, California, US

MarketsCloud-Native Application Protection Platform (CNAPP)Cloud Infrastructure Providers (IaaS/PaaS)Application Hosting Platforms Container Management Cloud Infrastructure Providers (IaaS/PaaS)Infrastructure as Code (IaC)

01Competitive Landscape

Narrative analysis

Direct competitors and differentiators - Pulumi competes on the ability to express infrastructure with general-purpose languages, which can reduce the need for inline scripting in complex scenarios. - Scalr, Spacelift, and env0 compete as Terraform automation platforms and are often considered alternative control planes to Terraform Cloud offering different pricing mechanics and operational models. - OpenTofu focuses on licensing and community governance following vendor license changes. Pricing comparison (caution) - Vendor hosted pricing uses a managed-resources model that can be complex to forecast for ephemeral or high-churn environments. - Competitors use different meters (e.g., tiered plans and vendor-defined resource usage metrics, qualifying runs), and direct comparison should be performed with organization-specific usage patterns. Customer perspectives comparing products - Community discussions contrast Terraform with cloud-native IaC (e.g., CloudFormation) where native services manage state, and with Pulumi where general-purpose languages address complex logic needs.

	HashiCorp Terraform (CLI + HCP/TFE)	Pulumi	Scalr (Terraform automation)
Starting Price	CLI: self-managed; HCP/TFE: published vendor pricing available	No-cost individual tier; paid team and enterprise tiers with published vendor pricing	No-cost tier available; usage-based billing based on qualifying runs per vendor terms
Typical Use Case	Multi-provider IaC standardization; broad provider and module ecosystem; governance via HCP/TFE	Teams preferring IaC in general-purpose programming languages and closer developer ergonomics	Platform teams seeking Terraform automation with alternative pricing models
Key Strength	Broad provider ecosystem; common industry skills; plan/apply workflow	Programming-language expressiveness; integration of app and infra workflows	Alternative commercialization model; different billing units and pricing mechanics
Key Weakness	Hosted pricing concerns; licensing controversy; operational complexity for self-managed state/workflows	Some users raise concerns about SaaS pricing and perceived value for teams with specific requirements	Feature parity with vendor-hosted Terraform flows and enterprise requirements should be validated case-by-case

01Competitive Landscape

Narrative analysis

Direct competitors and differentiators

Pulumi competes on the ability to express infrastructure with general-purpose languages, which can reduce the need for inline scripting in complex scenarios.
Scalr, Spacelift, and env0 compete as Terraform automation platforms and are often considered alternative control planes to Terraform Cloud offering different pricing mechanics and operational models.
OpenTofu focuses on licensing and community governance following vendor license changes.

Pricing comparison (caution)

Vendor hosted pricing uses a managed-resources model that can be complex to forecast for ephemeral or high-churn environments.
Competitors use different meters (e.g., tiered plans and vendor-defined resource usage metrics, qualifying runs), and direct comparison should be performed with organization-specific usage patterns.

Customer perspectives comparing products

Community discussions contrast Terraform with cloud-native IaC (e.g., CloudFormation) where native services manage state, and with Pulumi where general-purpose languages address complex logic needs.

	HashiCorp Terraform (CLI + HCP/TFE)	Pulumi	Scalr (Terraform automation)
Starting Price	CLI: self-managed; HCP/TFE: published vendor pricing available	No-cost individual tier; paid team and enterprise tiers with published vendor pricing	No-cost tier available; usage-based billing based on qualifying runs per vendor terms
Typical Use Case	Multi-provider IaC standardization; broad provider and module ecosystem; governance via HCP/TFE	Teams preferring IaC in general-purpose programming languages and closer developer ergonomics	Platform teams seeking Terraform automation with alternative pricing models
Key Strength	Broad provider ecosystem; common industry skills; plan/apply workflow	Programming-language expressiveness; integration of app and infra workflows	Alternative commercialization model; different billing units and pricing mechanics
Key Weakness	Hosted pricing concerns; licensing controversy; operational complexity for self-managed state/workflows	Some users raise concerns about SaaS pricing and perceived value for teams with specific requirements	Feature parity with vendor-hosted Terraform flows and enterprise requirements should be validated case-by-case