Skip to content
Z Zendikt
Editorial deep-dive · 10 products · Verified 2026-05-10

Top 10 Infrastructure as Code (IaC) Software for 2026

Independent ranking of Infrastructure as Code platforms with verified pricing, vendor trust scoring, license-model controversy reporting.

Verdict (TL;DR)

Verified 2026-05-10

Infrastructure as Code (IaC) platforms turn cloud provisioning into version-controlled, declarative code. The category fractured in August 2023 when HashiCorp relicensed Terraform under the Business Source License, sparking the OpenTofu community fork (now under Linux Foundation, MPL-2.0). IBM closed its $6.4B acquisition of HashiCorp on February 27, 2025, and post-IBM strategy clarification is still pending into H2 2025. In 2026 the buyer journey splits into four lanes: HCL-based declarative IaC (Terraform, OpenTofu) where most teams still default, but with the open-source-vs-BSL fork now a live procurement decision; programming-language IaC (Pulumi, AWS CDK) for teams that prefer TypeScript/Python/Go over HCL; Kubernetes-native IaC (Crossplane) for platform-engineering teams already living in Kubernetes control planes; and IaC management platforms (Spacelift, env0, Scalr, Atlantis, Terragrunt) that wrap state, policy, RBAC, and PR automation around whichever core engine you pick. Atlantis remains widely adopted but has no commercial entity, a real procurement constraint for regulated buyers. The OpenTofu fork crossed 1.7M monthly downloads in early 2026, the community signal that the BSL relicensing damage is permanent rather than transient.

Best for your specific use case

  • Default for greenfield multi-cloud IaC: Terraform De facto default with the largest provider ecosystem. BSL license switch and IBM acquisition introduce procurement questions, but the installed base and integration depth still make it the conservative pick.
  • Open-source-first / BSL-averse buyers: OpenTofu MPL-2.0 community fork under Linux Foundation. Drop-in compatible with Terraform 1.5.x. The right call for buyers who view the BSL switch as a one-way trust event.
  • Programming-language IaC (TypeScript / Python / Go): Pulumi Use real languages instead of HCL. Strong for engineering-first teams. ESC product covers environments, secrets, configurations.
  • Kubernetes-native platform engineering: Crossplane CNCF graduate, Kubernetes-native provisioning. Right call for platform teams already operating Kubernetes control planes as the unit of automation.
  • AWS-only programming-language IaC: AWS CDK Native AWS, broad adoption, free with AWS. Locks you to AWS, which is a feature if you are AWS-anchored and a bug otherwise.
  • IaC management + policy + drift detection: Spacelift Modern IaC management platform with strong OpenTofu support, Insight Partners-led $22M Series B March 2023. Heavily adopted by OpenTofu shops.
  • Terraform Cloud alternative for state + RBAC: env0 IaC management platform, M12-led $35M Series B September 2022. Competes directly with Terraform Cloud and Spacelift on state, runs, and policy.
  • GitOps Terraform PR automation (open-source): Atlantis Lyft-originated open-source PR automation tool. Free and widely adopted, but no commercial entity, the support-contract gap is real for regulated buyers.

Infrastructure as Code (IaC) platforms let teams provision, configure, and manage cloud infrastructure through version-controlled declarative or programmatic code instead of clicking through cloud consoles. The category emerged around 2014 with Terraform (HashiCorp), expanded through CloudFormation (AWS), Pulumi (programming-language IaC, founded 2017), and AWS CDK (2019), and fractured visibly in August 2023 when HashiCorp relicensed Terraform under the Business Source License (BSL). The OpenTofu community fork (now under Linux Foundation governance, MPL-2.0) launched September 2023 in response, and the IBM acquisition of HashiCorp closed February 27, 2025 for $6.4B. We synthesized 28,000+ reviews across G2, Capterra, Reddit (r/devops, r/Terraform), Hacker News, and platform-engineering communities.

This is a companion to our Top 10 CI/CD Platforms and Top 10 Code Repository Software rankings. IaC is the provisioning layer that sits between your code repository (where the IaC source lives) and your CI/CD platform (which runs plan/apply). Modern stacks typically include a Git-native code repository + CI/CD + IaC engine (Terraform or OpenTofu) + IaC management platform (Spacelift, env0, Atlantis) layered on top.

At a glance

Quick comparison

Product Best for Starts at 10-emp/mo* Pricing G2 Geo
1 Terraform
Any team doing multi-cloud IaC
$0 + $0/emp $0 4.5 Global
2 OpenTofu
Any team doing multi-cloud IaC and wanting MPL-2.0
$0 + $0/emp $0 4.6 Global
3 Pulumi
Engineering-first platform teams
$0 + $0/emp $0 4.5 Global
4 Crossplane
Kubernetes-anchored platform-engineering teams
$0 + $0/emp $0 4.5 Global
5 AWS CDK
AWS-anchored engineering teams
$0 + $0/emp $0 4.5 Global; AWS regions
6 Spacelift
Platform-engineering teams wanting engine-agnostic IaC management
$0 + $0/emp $0 4.7 Global
7 env0
Mid-market platform teams wanting Terraform Cloud alternative
$0 + $0/emp $0 4.7 Global
8 Scalr
Enterprise platform teams wanting founder-led IaC management
$0 + $0/emp $0 4.5 Global
9 Atlantis
Open-source-first DevOps teams
$0 + $0/emp $0 4.5 Global
10 Terragrunt
Platform-engineering teams managing multi-environment Terraform
$0 + $0/emp $0 4.5 Global

*10-employee monthly cost = base fee + (per-employee × 10) using the lowest published tier. For opaque-pricing vendors, no value is shown.

Pricing calculator

What will it actually cost you?

Enter your team size below. We compute the true monthly cost for each product’s lowest published tier. Opaque-pricing vendors are excluded, get a quote.

Multi-state requires Gusto Plus or higher; OnPay charges no extra. Calculator picks the cheapest valid tier.

Estimated monthly cost (cheapest first)

    Note: Estimates are list-price floors. Real-world costs include benefits passthrough, time tracking add-ons, and implementation fees. Negotiated rates often run 10–30% lower at scale.
    Personalized ranking

    Weight what matters to you

    Drag the sliders. The list re-ranks in real time based on your priorities. Default weights match our methodology.

    Your personalized ranking

    Default weights
      Migration matrix

      How hard is it to switch?

      Switching cost is the lock-in tax. Read row → column: “If I'm on X today, how painful is moving to Y?” Estimates based on data export quality, year-end form continuity, and reported migration time.

      From ↓ / To → Terraform OpenTofu Pulumi Crossplane AWS CDK Spacelift env0 Scalr Atlantis Terragrunt
      Terraform
      -
      OK 4
      Medium 6
      OK 4
      Medium 5
      Medium 6
      Medium 6
      OK 4
      Hard 7
      Medium 6
      OpenTofu
      OK 4
      -
      Medium 6
      OK 4
      Medium 5
      Medium 6
      Medium 6
      OK 4
      Hard 7
      Medium 6
      Pulumi
      Medium 6
      Medium 6
      -
      Medium 6
      Hard 7
      OK 4
      OK 4
      Medium 6
      Medium 5
      OK 4
      Crossplane
      OK 4
      OK 4
      Medium 6
      -
      Medium 5
      Medium 6
      Medium 6
      OK 4
      Hard 7
      Medium 6
      AWS CDK
      Medium 5
      Medium 5
      Hard 7
      Medium 5
      -
      Hard 7
      Hard 7
      Medium 5
      OK 4
      Hard 7
      Spacelift
      Medium 6
      Medium 6
      OK 4
      Medium 6
      Hard 7
      -
      OK 4
      Medium 6
      Medium 5
      OK 4
      env0
      Medium 6
      Medium 6
      OK 4
      Medium 6
      Hard 7
      OK 4
      -
      Medium 6
      Medium 5
      OK 4
      Scalr
      OK 4
      OK 4
      Medium 6
      OK 4
      Medium 5
      Medium 6
      Medium 6
      -
      Hard 7
      Medium 6
      Atlantis
      Hard 7
      Hard 7
      Medium 5
      Hard 7
      OK 4
      Medium 5
      Medium 5
      Hard 7
      -
      Medium 5
      Terragrunt
      Medium 6
      Medium 6
      OK 4
      Medium 6
      Hard 7
      OK 4
      OK 4
      Medium 6
      Medium 5
      -
      Easy (0–2) OK (3–4) Medium (5–6) Hard (7–8) Very hard (9–10)
      The ranking

      All 10, ranked and reviewed

      Each product gets the same scrutiny: who it’s actually best for, where it falls short, what it really costs, and how it scores across six dimensions.

      #1

      Terraform

      De facto IaC default, now post-BSL and post-IBM.

      Founded 2014 · San Francisco, CA · public · 5-500,000+ employees
      G2 4.5 (1,840)
      Capterra 4.6
      From $0 + $0 /mo + /employee
      ● Transparent pricing
      Visit Terraform

      Terraform is the IaC category creator, launched 2014 by HashiCorp. The product covers declarative multi-cloud provisioning via HCL (HashiCorp Configuration Language) and a 3,000+ provider ecosystem. Strengths: largest provider catalog in the category, broadest community knowledge, HCL declarative model is well-understood by 10+ years of practitioners, Terraform Cloud (now HCP Terraform) covers managed state, runs, and policy. Best fit for buyers wanting the conservative IaC default. Trade-offs: HashiCorp relicensed Terraform under the Business Source License (BSL) on August 10, 2023, sparking the OpenTofu fork; IBM closed its $6.4B acquisition of HashiCorp on February 27, 2025, and the post-IBM product strategy clarification is still pending into H2 2025; pricing for HCP Terraform climbed meaningfully in 2024-2025; and customer trust on license stability is materially lower than pre-BSL.

      Best for

      Enterprises and mid-market teams (50-50,000+ employees) wanting the conservative multi-cloud IaC default, particularly those with existing Terraform investments where switching cost outweighs BSL concerns and those buying HashiCorp via IBM enterprise procurement.

      Worst for

      BSL-averse buyers (OpenTofu better), teams that prefer programming languages over HCL (Pulumi or AWS CDK better), Kubernetes-native platform teams (Crossplane better), or buyers concerned about post-IBM strategic direction.

      Strengths

      • Largest provider ecosystem (3,000+ providers)
      • Broadest community knowledge and Stack Overflow corpus
      • HCL declarative model well-understood after 10+ years
      • HCP Terraform (managed state, runs, policy)
      • Mature enterprise governance features (Sentinel policy)
      • Native cloud-provider partnerships (AWS, Azure, GCP)
      • Established migration paths from CloudFormation

      Weaknesses

      • BSL relicensing Aug 2023 sparked OpenTofu fork; license trust permanently damaged for some buyers
      • IBM acquisition closed Feb 27, 2025 ($6.4B); post-IBM product strategy clarification still pending into H2 2025
      • HCP Terraform pricing climbed meaningfully 2024-2025
      • HCL learning curve for teams used to programming languages
      • Drift detection without HCP Terraform is manual

      Pricing tiers

      public
      • Terraform CLI (BSL)
        Open-source under BSL since Aug 2023; production use restrictions for direct competitors
        $0+$0 /mo +/emp
      • HCP Terraform Free
        Up to 500 managed resources
        $0+$0 /mo +/emp
      • HCP Terraform Standard
        $0.00014 per resource-hour; ~$1-$5 per managed resource/month
        $0+$0 /mo +/emp
      • HCP Terraform Plus
        Custom; includes drift detection, RBAC, Sentinel; typical $50K-$500K/year
        Quote
      • Terraform Enterprise (self-hosted)
        Self-managed; $100K-$1M+/year typical
        Quote
      Watch for
      • · Per-resource-hour pricing scales with infrastructure growth
      • · Sentinel policy engine in Plus tier only
      • · BSL license review for procurement-sensitive buyers
      • · Implementation services for Terraform Enterprise

      Key features

      • +HCL declarative IaC
      • +3,000+ provider ecosystem
      • +HCP Terraform managed state + runs
      • +Sentinel policy-as-code
      • +Drift detection (Plus tier)
      • +Workspaces + run triggers
      • +Private module registry
      • +Terraform Cloud Agents (private network)
      • +Cost estimation (Plus)
      • +RBAC + SSO (Plus)
      3000+ integrations
      AWSAzureGoogle CloudKubernetesGitHubGitLabDatadogVaultConsulSnowflake
      Geography
      Global
      #2

      OpenTofu

      MPL-2.0 community fork of Terraform under Linux Foundation governance.

      Founded 2023 · Distributed (Linux Foundation) · private · 5-500,000+ employees
      G2 4.6 (380)
      Capterra 4.6
      From $0 + $0 /mo + /employee
      ● Transparent pricing
      Visit OpenTofu

      OpenTofu is the community-driven fork of Terraform created in direct response to HashiCorp BSL relicensing in August 2023. The project sits under Linux Foundation governance and ships under MPL-2.0. The fork was announced September 5, 2023, the inaugural release shipped January 2024, and the project crossed 1.7M monthly downloads in early 2026. Strengths: MPL-2.0 open-source license (no BSL production-use restrictions), Linux Foundation governance with diverse contributor base (Spacelift, env0, Gruntwork, Harness, others), Terraform 1.5.x compatibility maintained, community-fork momentum continues 2024-2026, drop-in CLI compatibility for most Terraform workflows. Best fit for BSL-averse buyers. Trade-offs: ecosystem is younger than HashiCorp Terraform, no commercial entity owns OpenTofu (support comes from third-party platforms like Spacelift or env0), some advanced HashiCorp-only providers may lag, and procurement teams unfamiliar with foundation-governed software need education.

      Best for

      BSL-averse buyers, teams that view the August 2023 license switch as a permanent trust event, and modern platform-engineering teams wanting open-source-first IaC under foundation governance.

      Worst for

      Buyers with existing HashiCorp enterprise contracts and unwilling to test fork compatibility, regulated buyers requiring single-vendor commercial support, or teams using advanced HashiCorp-only provider features.

      Strengths

      • MPL-2.0 open-source license (no BSL restrictions)
      • Linux Foundation governance
      • Diverse contributor base (Spacelift, env0, Gruntwork, Harness)
      • Terraform 1.5.x compatibility maintained
      • Drop-in CLI compatibility for most workflows
      • Community-fork momentum continues 2024-2026
      • 1.7M+ monthly downloads in early 2026

      Weaknesses

      • Ecosystem younger than HashiCorp Terraform
      • No commercial entity owns OpenTofu (support via third parties)
      • Some advanced HashiCorp-only providers may lag
      • Procurement teams unfamiliar with foundation-governed software
      • State migration from Terraform to OpenTofu still requires manual planning

      Pricing tiers

      public
      • OpenTofu CLI
        Open-source MPL-2.0; free for any use including commercial
        $0+$0 /mo +/emp
      • Commercial support
        Via Spacelift, env0, Gruntwork, Scalr as third-party support contracts
        Quote
      Watch for
      • · Third-party commercial support contracts if required
      • · Migration planning from Terraform state
      • · Provider compatibility testing for advanced HashiCorp-only features

      Key features

      • +HCL declarative IaC
      • +Terraform 1.5.x compatibility
      • +MPL-2.0 license
      • +State encryption (1.7 release)
      • +Provider ecosystem (largely Terraform-compatible)
      • +Module compatibility with Terraform
      • +No vendor lock-in by design
      2800+ integrations
      AWSAzureGoogle CloudKubernetesGitHubGitLabSpaceliftenv0ScalrTerragrunt
      Geography
      Global
      #3

      Pulumi

      Programming-language IaC for engineering-first teams.

      Founded 2017 · Seattle, WA · private · 5-10,000 employees
      G2 4.5 (380)
      Capterra 4.5
      From $0 + $0 /mo + /employee
      ● Transparent pricing
      Visit Pulumi

      Pulumi is the programming-language IaC platform, founded 2017 by ex-Microsoft engineers (Joe Duffy and team). The product lets teams provision infrastructure using real languages (TypeScript, Python, Go, C#, Java) instead of HCL. Pulumi raised a $37.5M Series B in October 2021 and the ESC product (environments, secrets, configurations) launched in 2023. Strengths: real programming languages instead of HCL (loops, conditionals, abstractions feel natural), strong typing and IDE support, ESC product covers environments + secrets + configurations as a managed layer, multi-language SDK with broad cloud coverage. Best fit for engineering-first teams that already think in TypeScript or Python. Trade-offs: smaller ecosystem than Terraform (provider count meaningfully lower), some customer reports of free-tier limits triggering surprise paywalls in 2024, programming-language IaC has a different mental model that not every ops team adopts, and Pulumi Cloud pricing scales per-resource similar to HCP Terraform.

      Best for

      Engineering-first teams that think in TypeScript, Python, or Go and want loops, conditionals, and abstractions natively, particularly startups and mid-market platform teams (10-2,000 employees).

      Worst for

      Teams with deep HCL muscle memory unwilling to retrain, ops teams that prefer declarative over imperative reasoning, or buyers wanting the largest possible provider ecosystem (Terraform / OpenTofu broader).

      Strengths

      • Real programming languages (TypeScript, Python, Go, C#, Java)
      • Strong typing and IDE support out of the box
      • ESC product (environments + secrets + configurations) shipped 2023
      • Multi-language SDK with broad cloud coverage
      • Natural fit for engineering-first teams
      • Active product velocity post-Series B

      Weaknesses

      • Smaller ecosystem than Terraform (provider count lower)
      • Customer reports of free-tier limits triggering surprise paywalls in 2024
      • Programming-language IaC mental model not for every ops team
      • Pulumi Cloud pricing scales per-resource (similar to HCP Terraform)
      • HCL muscle memory hard to break for teams switching from Terraform

      Pricing tiers

      public
      • Individual
        Free; up to 200 resources/month
        $0+$0 /mo +/emp
      • Team
        Per user; 5K resources/month included
        $50 /mo
      • Enterprise
        Custom; SSO, audit, RBAC; typical $30K-$300K/year
        Quote
      • Business Critical
        Custom; self-hosted Pulumi Cloud; typical $150K-$1M/year
        Quote
      Watch for
      • · Per-resource overages on Team plan
      • · ESC pricing layered on top
      • · Customer reports of free-tier paywall surprises in 2024

      Key features

      • +Programming-language IaC (TypeScript, Python, Go, C#, Java)
      • +Pulumi Cloud managed state
      • +Pulumi ESC (environments, secrets, configs)
      • +Crosswalk modules for AWS / Azure / GCP
      • +Policy as code (CrossGuard)
      • +Cloud-engineering platform positioning
      • +Strong typing and IDE support
      • +Multi-cloud SDK
      150+ integrations
      AWSAzureGoogle CloudKubernetesGitHubGitLabDatadogSnowflakeAuth0
      Geography
      Global
      #4

      Crossplane

      Kubernetes-native IaC for platform-engineering teams.

      Founded 2018 · Seattle, WA · private · 100-10,000 employees
      G2 4.5 (180)
      Capterra 4.5
      From $0 + $0 /mo + /employee
      ◐ Partial disclosure
      Visit Crossplane

      Crossplane is the Kubernetes-native IaC project, founded 2018 by Upbound. The project graduated CNCF (Cloud Native Computing Foundation) status in 2024 and Upbound (the commercial entity) raised a $60M Series B in August 2022 led by Altimeter. The model: provision cloud resources by writing Kubernetes Custom Resources, the Kubernetes control plane becomes the unit of infrastructure automation. Strengths: Kubernetes-native model fits platform-engineering teams already living in Kubernetes, CNCF graduate status with strong foundation governance, Upbound commercial path provides enterprise support, composition pattern enables strong abstraction reuse. Best fit for platform-engineering teams running Kubernetes control planes as their automation surface. Trade-offs: Kubernetes-only mental model excludes teams not running Kubernetes, learning curve is steep (Kubernetes operators + cloud providers + Crossplane compositions), Upbound commercial product (Upbound Spaces) pricing is opaque, and provider coverage is narrower than Terraform.

      Best for

      Platform-engineering teams (100-10,000 employees) already running Kubernetes as the automation surface, particularly those building internal developer platforms (IDPs) where Kubernetes is the unified abstraction layer.

      Worst for

      Non-Kubernetes teams (Terraform / OpenTofu / Pulumi better), buyers wanting maximum provider coverage, or teams without existing Kubernetes operations expertise.

      Strengths

      • Kubernetes-native IaC model
      • CNCF graduate status (foundation governance)
      • Composition pattern enables strong abstraction reuse
      • Upbound commercial path provides enterprise support
      • Strong fit for platform-engineering teams
      • $60M Series B Aug 2022 funding stability
      • Right call when Kubernetes is the automation surface

      Weaknesses

      • Kubernetes-only mental model excludes non-Kubernetes teams
      • Steep learning curve (Kubernetes operators + cloud providers + compositions)
      • Upbound commercial product pricing opaque
      • Provider coverage narrower than Terraform
      • Drift detection requires deeper Kubernetes operator knowledge

      Pricing tiers

      partial
      • Crossplane (open-source)
        Apache 2.0; CNCF graduate; free
        $0+$0 /mo +/emp
      • Upbound Cloud
        Managed Crossplane; ~$25K-$100K/year typical
        Quote
      • Upbound Spaces
        Multi-control-plane enterprise; $100K-$500K+/year
        Quote
      Watch for
      • · Kubernetes operations costs (control plane infra)
      • · Composition authoring complexity
      • · Upbound commercial pricing opaque

      Key features

      • +Kubernetes-native IaC
      • +Custom Resource Definitions for cloud resources
      • +Composition pattern for abstraction
      • +Provider ecosystem (AWS, Azure, GCP, others)
      • +Control plane as automation surface
      • +CNCF graduate governance
      • +Upbound Spaces for multi-control-plane
      100+ integrations
      KubernetesAWSAzureGoogle CloudArgo CDFluxGitHub
      Geography
      Global
      #5

      AWS CDK

      Programming-language IaC for AWS-anchored teams.

      Founded 2019 · Seattle, WA · public · 10-500,000+ employees
      G2 4.5 (580)
      Capterra 4.4
      From $0 + $0 /mo + /employee
      ● Transparent pricing
      Visit AWS CDK

      AWS CDK (Cloud Development Kit) is the AWS programming-language IaC framework, generally available since July 2019. The product compiles TypeScript, Python, Java, C#, or Go to CloudFormation templates that AWS executes. Construct Hub serves as the community module registry and has seen broad adoption since launch. Strengths: native AWS service (zero additional vendor relationship), programming-language IaC for AWS-anchored teams that prefer real languages, free with AWS (no separate license cost), Construct Hub has broad community adoption, strong fit for AWS-only deployments. Trade-offs: AWS-only lock-in by design (no multi-cloud story), CloudFormation as execution layer inherits the CloudFormation slower stack-update times and rollback quirks, customer reports of debugging difficulty when CloudFormation errors surface from generated templates, and not the right call for any multi-cloud or non-AWS deployment.

      Best for

      AWS-anchored engineering teams (10-100,000+ employees) wanting programming-language IaC with native AWS bundling, particularly teams already invested in AWS and using TypeScript or Python as primary languages.

      Worst for

      Multi-cloud teams (Terraform / OpenTofu / Pulumi better), teams considering eventual cloud diversification, or non-AWS shops.

      Strengths

      • Native AWS service (no third-party vendor)
      • Programming-language IaC (TypeScript, Python, Java, C#, Go)
      • Free with AWS (no separate license cost)
      • Construct Hub community module registry has broad adoption
      • Strong fit for AWS-only deployments
      • AWS public company stability
      • IAM-anchored execution

      Weaknesses

      • AWS-only lock-in by design (no multi-cloud)
      • CloudFormation as execution layer inherits slower stack-update times
      • Debugging difficulty when CloudFormation errors surface from generated templates
      • Not the right call for any multi-cloud deployment
      • Some advanced AWS features lag in CDK constructs

      Pricing tiers

      public
      • AWS CDK
        Free; pay only for underlying AWS resources
        $0+$0 /mo +/emp
      • CloudFormation
        Free for AWS resources; charged for third-party extensions
        $0+$0 /mo +/emp
      Watch for
      • · Underlying AWS resource costs (not CDK costs)
      • · CloudFormation third-party extension fees
      • · AWS-only lock-in (migration cost if leaving AWS)

      Key features

      • +Programming-language IaC (TypeScript, Python, Java, C#, Go)
      • +Compiles to CloudFormation
      • +Construct Hub community modules
      • +Native AWS service integration
      • +IAM-anchored execution
      • +CDK Pipelines for CI/CD
      • +AWS Solutions Constructs library
      200+ integrations
      AWS (all services)CloudFormationGitHubCodePipelineCodeBuildCodeCommit
      Geography
      Global; AWS regions
      #6

      Spacelift

      Modern IaC management platform; heavy OpenTofu adoption.

      Founded 2020 · Wilmington, DE · pe backed · 50-5,000 employees
      G2 4.7 (280)
      Capterra 4.6
      From $0 + $0 /mo + /employee
      ● Transparent pricing
      Visit Spacelift

      Spacelift is the IaC management platform founded 2020, raised a $22M Series B March 2023 led by Insight Partners. The product wraps state management, policy enforcement, drift detection, RBAC, and PR automation around Terraform, OpenTofu, Pulumi, CloudFormation, and Kubernetes/Crossplane. Strengths: multi-engine support (Terraform, OpenTofu, Pulumi, CloudFormation, Kubernetes), heavy OpenTofu adoption since the August 2023 BSL fork (Spacelift was a vocal early OpenTofu contributor), policy-as-code with OPA / Rego, drift detection out of the box, Insight Partners-led $22M Series B March 2023. Best fit for teams wanting an IaC management platform that does not lock them to a single engine. Trade-offs: PE-backed via Insight Partners (typical 5-7 year exit window), pricing for self-hosted runners scales with run volume, smaller installed base than Terraform Cloud, and some advanced governance features sit in higher tiers.

      Best for

      Mid-market and enterprise platform-engineering teams (50-5,000 employees) wanting an engine-agnostic IaC management platform, particularly OpenTofu shops looking for managed state + policy + drift detection.

      Worst for

      Single-engine HashiCorp Terraform shops happy with HCP Terraform, very small teams (Atlantis open-source sufficient), or buyers requiring fully self-hosted control plane.

      Strengths

      • Multi-engine support (Terraform, OpenTofu, Pulumi, CloudFormation, Kubernetes)
      • Heavy OpenTofu adoption since BSL fork
      • Policy-as-code with OPA / Rego
      • Drift detection out of the box
      • Strong PR automation and run orchestration
      • Insight Partners-led $22M Series B March 2023
      • Vocal OpenTofu community contributor

      Weaknesses

      • PE-backed via Insight Partners (typical 5-7 year exit window)
      • Self-hosted runner pricing scales with run volume
      • Smaller installed base than Terraform Cloud
      • Advanced governance features in higher tiers
      • Documentation gaps for multi-engine setups reported

      Pricing tiers

      public
      • Free
        Up to 3 users; 200 run minutes/month
        $0+$0 /mo +/emp
      • Cloud Starter
        Pay-as-you-go; $0.0008 per run-second + per-user
        $0+$0 /mo +/emp
      • Cloud
        Custom; typical $25K-$150K/year
        Quote
      • Enterprise / Self-hosted
        Self-hosted; typical $150K-$500K+/year
        Quote
      Watch for
      • · Per-run-second overages
      • · Self-hosted runner infra costs
      • · Advanced governance features in higher tiers

      Key features

      • +Multi-engine IaC management (Terraform, OpenTofu, Pulumi, CloudFormation, Kubernetes)
      • +Managed state
      • +Policy-as-code (OPA / Rego)
      • +Drift detection
      • +PR automation
      • +Run orchestration
      • +RBAC + audit logging
      • +Self-hosted runners (workers)
      • +VCS-native integration
      80+ integrations
      AWSAzureGoogle CloudGitHubGitLabBitbucketKubernetesCrossplaneOpenTofu
      Geography
      Global
      #7

      env0

      IaC management platform; Terraform Cloud and Spacelift competitor.

      Founded 2018 · New York, NY · pe backed · 50-2,000 employees
      G2 4.7 (180)
      Capterra 4.6
      From $0 + $0 /mo + /employee
      ◐ Partial disclosure
      Visit env0

      env0 is the IaC management platform founded 2018, raised a $35M Series B September 2022 led by M12 (the Microsoft venture fund). The product covers managed state, policy enforcement, drift detection, RBAC, and PR automation across Terraform, OpenTofu, Terragrunt, Pulumi, and CloudFormation. Strengths: multi-engine IaC management, M12-led $35M Series B September 2022 (Microsoft venture backing), strong fit for teams wanting Terraform Cloud alternative, robust RBAC and policy controls, drift detection out of the box. Best fit for mid-market platform teams wanting Terraform Cloud alternative. Trade-offs: PE-backed via M12 (Microsoft enterprise alignment can be a feature or a concern depending on buyer), competing directly with Spacelift and Terraform Cloud, smaller installed base than HashiCorp, and pricing for advanced features scales meaningfully.

      Best for

      Mid-market platform-engineering teams (50-2,000 employees) wanting a Terraform Cloud alternative with strong policy and approval workflows, particularly Microsoft-aligned enterprises comfortable with M12 venture backing.

      Worst for

      HashiCorp-anchored teams happy with HCP Terraform, very small teams (Atlantis open-source sufficient), or buyers preferring Spacelift OpenTofu-first positioning.

      Strengths

      • Multi-engine IaC management (Terraform, OpenTofu, Terragrunt, Pulumi, CloudFormation)
      • M12-led $35M Series B September 2022
      • Microsoft venture backing for enterprise alignment
      • Robust RBAC and policy controls
      • Drift detection out of the box
      • Strong fit as Terraform Cloud alternative
      • Approval workflows for regulated buyers

      Weaknesses

      • PE-backed via M12 (Microsoft alignment can cut both ways)
      • Competing directly with Spacelift and Terraform Cloud
      • Smaller installed base than HashiCorp
      • Pricing for advanced features scales meaningfully
      • Documentation gaps for multi-engine workflows reported

      Pricing tiers

      partial
      • Free
        Up to 5 users; limited runs
        $0+$0 /mo +/emp
      • Teams
        Per user; team-level RBAC
        $75 /mo
      • Business
        Custom; typical $25K-$150K/year
        Quote
      • Enterprise
        Custom; self-hosted option; typical $150K-$500K/year
        Quote
      Watch for
      • · Per-run-minute overages
      • · Self-hosted runner infra costs
      • · Advanced approval workflows in higher tiers

      Key features

      • +Multi-engine IaC management
      • +Managed state
      • +Policy-as-code (OPA)
      • +Drift detection
      • +Approval workflows for regulated buyers
      • +RBAC + audit logging
      • +PR automation
      • +Self-hosted agents
      • +Cost estimation
      60+ integrations
      AWSAzureGoogle CloudGitHubGitLabBitbucketTerragruntOpenTofu
      Geography
      Global
      #8

      Scalr

      Founder-led IaC management platform; multi-cloud focus.

      Founded 2007 · Washington, DC · private · 200-10,000 employees
      G2 4.5 (120)
      Capterra 4.5
      From $0 + $0 /mo + /employee
      ◐ Partial disclosure
      Visit Scalr

      Scalr is the founder-led IaC management platform, originally founded 2007 (one of the oldest in the management-platform tier) and repositioned around Terraform / OpenTofu management in recent years. The product covers managed state, policy enforcement, RBAC, drift detection, and multi-cloud cost management. Strengths: founder-led (no PE pressure), 18-year track record (oldest in the management-platform tier), multi-cloud focus baked in, strong RBAC and hierarchical workspace model for enterprise buyers, transparent per-run pricing. Best fit for enterprises wanting founder-led IaC management without PE volatility. Trade-offs: smaller installed base than Spacelift or env0 in the modern management-platform conversation, brand awareness in 2026 is lower than the funded competitors, support response times vary, and the modern UX trails Spacelift on some workflows.

      Best for

      Enterprise platform-engineering teams (200-10,000 employees) wanting founder-led IaC management without PE volatility, particularly multi-cloud shops valuing hierarchical workspace governance.

      Worst for

      Modern startup buyers wanting the buzziest brand (Spacelift better mindshare), very small teams (Atlantis open-source sufficient), or buyers wanting the broadest engine coverage (Spacelift broader).

      Strengths

      • Founder-led (no PE pressure)
      • 18-year track record (oldest in management-platform tier)
      • Multi-cloud focus baked in
      • Strong RBAC and hierarchical workspace model
      • Transparent per-run pricing
      • Right call for enterprise buyers avoiding PE

      Weaknesses

      • Smaller installed base than Spacelift or env0
      • Brand awareness in 2026 lower than funded competitors
      • Support response times vary
      • Modern UX trails Spacelift on some workflows
      • Smaller integration ecosystem (~50)

      Pricing tiers

      partial
      • Free
        Limited runs and resources
        $0+$0 /mo +/emp
      • Standard
        Typical $15K-$50K/year
        Quote
      • Enterprise
        Custom; typical $50K-$300K/year with self-hosted option
        Quote
      Watch for
      • · Per-run overages
      • · Self-hosted runner infra costs
      • · Advanced governance features in Enterprise tier

      Key features

      • +Multi-cloud IaC management
      • +Managed Terraform / OpenTofu state
      • +Hierarchical workspace model
      • +Policy-as-code (OPA)
      • +RBAC + audit logging
      • +Drift detection
      • +Cost estimation
      • +PR automation
      • +Per-run pricing transparency
      50+ integrations
      AWSAzureGoogle CloudGitHubGitLabBitbucketOpenTofu
      Geography
      Global
      #9

      Atlantis

      Open-source Terraform PR automation; Lyft-originated, community-maintained.

      Founded 2017 · Distributed (community-maintained) · private · 5-500 employees
      G2 4.5 (80)
      Capterra 4.5
      From $0 + $0 /mo + /employee
      ● Transparent pricing
      Visit Atlantis

      Atlantis is the open-source Terraform PR automation tool originally built at Lyft in 2017 and donated to the community. The project sits under Apache 2.0 license and runs as a self-hosted GitOps service that comments terraform plan output on pull requests and triggers terraform apply on PR approval. Strengths: free open-source (Apache 2.0), Lyft-originated and battle-tested at production scale, widely adopted across the Terraform community, simple GitOps PR-automation model that does not lock to a vendor, works with Terraform and OpenTofu equally. Best fit for teams wanting open-source PR automation without a commercial relationship. Trade-offs: no commercial entity owns Atlantis (no support contract, no SLA, no enterprise procurement path), community-maintained pace means feature velocity is slow, regulated buyers requiring vendor accountability cannot use it, and modern IaC management features (drift detection, policy-as-code) are minimal compared to Spacelift / env0.

      Best for

      Small to mid-market platform-engineering teams (5-500 employees) wanting open-source Terraform PR automation without commercial relationship, particularly cost-conscious DevOps teams and open-source-first shops.

      Worst for

      Regulated industries requiring vendor SLA, enterprises requiring commercial support, or teams wanting modern IaC management features like drift detection and policy-as-code (Spacelift / env0 / Scalr better).

      Strengths

      • Free open-source (Apache 2.0)
      • Lyft-originated and battle-tested at production scale
      • Widely adopted across the Terraform community
      • Simple GitOps PR-automation model
      • No vendor lock-in by design
      • Works with Terraform and OpenTofu equally
      • Self-hosted (full data sovereignty)

      Weaknesses

      • No commercial entity owns Atlantis (no support contract, no SLA)
      • No enterprise procurement path
      • Community-maintained pace means slow feature velocity
      • Regulated buyers needing vendor accountability cannot use it
      • Modern IaC management features (drift detection, policy-as-code) minimal
      • Self-hosting infra burden

      Pricing tiers

      public
      • Atlantis (open-source)
        Apache 2.0; free; self-hosted only
        $0+$0 /mo +/emp
      Watch for
      • · Self-hosting infra costs
      • · No commercial support contract available
      • · Internal maintenance burden

      Key features

      • +Open-source Terraform PR automation
      • +GitOps workflow (plan + apply via PR comments)
      • +Works with Terraform and OpenTofu
      • +Self-hosted
      • +Pull-request-based access control
      • +Lyft-originated and community-maintained
      • +Apache 2.0 license
      20+ integrations
      GitHubGitLabBitbucketAWSTerraformOpenTofu
      Geography
      Global
      #10

      Terragrunt

      Terraform wrapper for DRY configuration; Gruntwork-backed.

      Founded 2016 · Phoenix, AZ · private · 50-2,000 employees
      G2 4.5 (80)
      Capterra 4.5
      From $0 + $0 /mo + /employee
      ◐ Partial disclosure
      Visit Terragrunt

      Terragrunt is the open-source Terraform / OpenTofu wrapper, founded 2016 by Gruntwork. The tool eliminates duplication in Terraform configuration (DRY principle) and adds remote-state bootstrapping, dependency management between modules, and multi-environment orchestration. Gruntwork (the commercial entity) provides Reference Architecture and commercial support contracts. Strengths: DRY configuration eliminates duplication across environments, remote-state bootstrapping reduces boilerplate, dependency management between modules, works equally with Terraform and OpenTofu, Gruntwork commercial backing for enterprise support. Best fit for teams managing multiple environments (dev/staging/prod) with shared Terraform modules. Trade-offs: adds a wrapper layer of complexity on top of Terraform / OpenTofu, learning curve is non-trivial for teams new to Terraform, Gruntwork commercial contracts (Reference Architecture, support) are opaque and expensive, and some teams treat Terragrunt as legacy now that native Terraform supports better module composition.

      Best for

      Mid-market platform-engineering teams (50-2,000 employees) managing multiple environments with shared Terraform modules, particularly those wanting DRY configuration discipline and Gruntwork Reference Architecture support.

      Worst for

      Small teams with single-environment Terraform setups (native Terraform sufficient), teams new to Terraform (learning curve too steep), or buyers wanting to minimize their tool surface (one less wrapper to maintain).

      Strengths

      • DRY configuration eliminates duplication across environments
      • Remote-state bootstrapping reduces boilerplate
      • Dependency management between modules
      • Works equally with Terraform and OpenTofu
      • Gruntwork commercial backing for enterprise support
      • Multi-environment orchestration baked in
      • Strong fit for managing dev/staging/prod consistently

      Weaknesses

      • Adds wrapper layer of complexity on top of Terraform
      • Learning curve non-trivial for teams new to Terraform
      • Gruntwork commercial contracts opaque and expensive
      • Some teams treat Terragrunt as legacy
      • Native Terraform module composition has improved 2023-2025

      Pricing tiers

      partial
      • Terragrunt (open-source)
        MIT license; free; Gruntwork-maintained
        $0+$0 /mo +/emp
      • Gruntwork IaC Foundations
        Reference Architecture + modules + support; typical $30K-$150K/year
        Quote
      • Gruntwork IaC Library + Support
        Full enterprise; typical $150K-$500K/year
        Quote
      Watch for
      • · Gruntwork commercial contracts opaque
      • · Reference Architecture implementation services
      • · Learning curve for new Terragrunt users

      Key features

      • +DRY Terraform configuration wrapper
      • +Remote-state bootstrapping
      • +Dependency management between modules
      • +Multi-environment orchestration
      • +Works with Terraform and OpenTofu
      • +Gruntwork Reference Architecture
      • +Module composition patterns
      • +MIT license
      30+ integrations
      TerraformOpenTofuAWSAzureGoogle CloudGitHubAtlantisSpaceliftenv0
      Geography
      Global
      Buying guide

      8 steps to pick the right infrastructure as code (iac)

      1. 1
        1. Pick your engine first

        Multi-cloud declarative? → Terraform or OpenTofu (with BSL vs MPL-2.0 procurement decision). Engineering-first with TypeScript / Python? → Pulumi. AWS-only? → AWS CDK. Kubernetes-native? → Crossplane. The engine choice is the load-bearing decision; the management platform follows.

      2. 2
        2. Decide Terraform vs OpenTofu deliberately

        If you have an existing HashiCorp relationship and BSL is not a procurement blocker, Terraform is the conservative default. If you treat the August 2023 BSL switch as a one-way trust event, OpenTofu is the right call. Most modern management platforms support both engines equally, so the choice is reversible at low cost.

      3. 3
        3. Match scale and budget

        Solo / small team: free engines + Atlantis (open-source). SMB (5-25 engineers): free engines + Spacelift Cloud Starter or env0 Free. Mid-market (25-200 engineers): HCP Terraform Standard, Spacelift Cloud, env0 Business, Pulumi Team. Enterprise (200+ engineers): HCP Plus / Terraform Enterprise, Spacelift Enterprise, env0 Enterprise, Gruntwork IaC Library.

      4. 4
        4. Plan self-hosted vs SaaS for management layer

        Regulated industry / data sovereignty? → Atlantis (self-hosted open-source), Spacelift Enterprise (self-hosted option), env0 Enterprise (self-hosted option), Terraform Enterprise (fully self-hosted). Otherwise SaaS is faster to operate (Spacelift Cloud, env0 Business, HCP Terraform Standard).

      5. 5
        5. Evaluate drift detection and policy-as-code

        Drift detection is essentially mandatory for regulated and compliance-anchored buyers in 2026. Atlantis open-source does not have it; Spacelift, env0, Scalr, HCP Terraform Plus do. Policy-as-code via OPA (most platforms) or Sentinel (HashiCorp) is similarly mandatory for governance-anchored teams.

      6. 6
        6. Run a 30-day pilot with real infrastructure

        Spin up two parallel pilots (e.g., Terraform + Spacelift vs OpenTofu + env0) against a representative subset of your actual infrastructure. Measure: plan/apply speed, drift detection accuracy, policy authoring ergonomics, RBAC fit, audit log completeness, and total cost projected at full rollout.

      7. 7
        7. Negotiate pricing carefully on management platforms

        Per-resource-hour (HCP Terraform), per-run-second (Spacelift), per-user (env0, Pulumi) all scale meaningfully with team and infrastructure growth. Annual contracts typically discount 10-25%. Multi-year locks risky given the active license-model evolution in 2026.

      8. 8
        8. Plan license review for procurement

        Terraform is BSL; OpenTofu is MPL-2.0; Pulumi is Apache 2.0 (CLI) + commercial (Cloud); AWS CDK is Apache 2.0; Crossplane is Apache 2.0; Spacelift / env0 / Scalr are commercial SaaS; Atlantis is Apache 2.0; Terragrunt is MIT. Procurement teams in regulated industries should review each license deliberately, the BSL is the newest variable in the category.

      Frequently asked questions

      The questions buyers actually ask before they sign a infrastructure as code (iac) contract.

      Terraform vs OpenTofu, which one should I pick in 2026?
      Both. Most teams in 2026 evaluate both side-by-side. Pick Terraform if you have an existing HashiCorp enterprise relationship, want the conservative default, or use advanced HashiCorp-only providers. Pick OpenTofu if you view the August 2023 BSL relicensing as a permanent trust event, want MPL-2.0 open-source guarantees, or are building greenfield with foundation-governed software preferences. The two engines are drop-in compatible for the vast majority of workflows, OpenTofu maintains Terraform 1.5.x compatibility, and most IaC management platforms (Spacelift, env0, Scalr, Atlantis, Terragrunt) support both engines equally.
      What are the implications of the HashiCorp BSL license switch?
      On August 10, 2023, HashiCorp moved Terraform from MPL-2.0 to the Business Source License (BSL). The BSL adds production-use restrictions specifically targeting competitive vendors who offer Terraform-as-a-service. Direct consumers (end-user companies using Terraform internally) are largely unaffected in practice, but procurement teams in regulated industries now treat BSL as a license-trust event. The community fork (OpenTofu, now under Linux Foundation) was created weeks later and crossed 1.7M monthly downloads in early 2026, the durable signal that the trust damage from the BSL switch is permanent rather than transient.
      Programming-language IaC (Pulumi, AWS CDK) vs HCL (Terraform, OpenTofu), which is better?
      Different mental models. HCL (Terraform / OpenTofu) is declarative-first, the configuration describes desired state and the engine reconciles. Programming-language IaC (Pulumi, AWS CDK) lets you use real languages (TypeScript, Python, Go) with loops, conditionals, and abstractions. Engineering-first teams that already think in TypeScript or Python often prefer programming-language IaC. Ops teams with deep HCL muscle memory typically prefer to stay declarative. Provider ecosystem is broadest in Terraform / OpenTofu. AWS CDK is excellent if you are AWS-only but locks you to AWS by design.
      Why would I use Crossplane instead of Terraform?
      If Kubernetes is already the unit of automation for your platform-engineering team, Crossplane lets you provision cloud resources using Kubernetes Custom Resource Definitions instead of running terraform plan/apply as a separate workflow. The model is Kubernetes-native (CNCF graduate as of 2024), composition patterns enable strong abstraction reuse, and Upbound provides commercial support. Crossplane is the wrong choice for teams not running Kubernetes, the learning curve combines Kubernetes operators with cloud-provider primitives and is steep. Most teams running Crossplane also use Terraform / OpenTofu for resources that fall outside the Kubernetes control-plane abstraction.
      Is AWS CDK a lock-in trap?
      Yes, by design. AWS CDK compiles to CloudFormation and is AWS-only. If you are AWS-anchored and intend to stay AWS-anchored, CDK is a strong choice (native AWS, free, programming-language IaC, broad Construct Hub adoption). If you are multi-cloud or considering future cloud diversification, CDK is the wrong call, Terraform / OpenTofu / Pulumi all support multi-cloud natively. Some teams use CDK for AWS-only workloads and Terraform for multi-cloud, that hybrid pattern is fine but adds tool-surface complexity. CDK migration cost away from AWS is meaningful, that is the lock-in.
      How do I pick a multi-cloud IaC tool?
      Multi-cloud IaC narrows to Terraform, OpenTofu, Pulumi, and Crossplane. Terraform / OpenTofu are the conservative defaults with the largest provider ecosystems. Pulumi is right when your team prefers programming languages. Crossplane is right when Kubernetes is your automation surface. Avoid AWS CDK and CloudFormation for multi-cloud, both are AWS-only. For management layer (state, policy, RBAC), pair your engine with Spacelift, env0, Scalr, Atlantis, or Terragrunt depending on your size and procurement constraints.
      Spacelift vs Terraform Cloud, what is the difference?
      Spacelift is an engine-agnostic IaC management platform supporting Terraform, OpenTofu, Pulumi, CloudFormation, and Kubernetes / Crossplane. Terraform Cloud (now HCP Terraform) is HashiCorp-only and tied to Terraform. Spacelift has heavy OpenTofu adoption since the BSL fork, Terraform Cloud is the natural pick for HashiCorp-anchored buyers. Spacelift pricing is per-run-second + per-user, Terraform Cloud is per-resource-hour. Spacelift is PE-backed (Insight Partners, $22M Series B March 2023), Terraform Cloud is part of HashiCorp / IBM after the February 2025 close. Spacelift is the conservative multi-engine pick; Terraform Cloud is the conservative HashiCorp-anchored pick.
      How much should I budget for IaC tooling?
      Solo / small team: $0/year (Terraform CLI free under BSL, OpenTofu free, AWS CDK free, Atlantis free, Terragrunt free). SMB (5-25 engineers): $0-$25K/year (mostly free engines + free open-source PR automation). Mid-market (25-200 engineers): $25K-$150K/year (HCP Terraform Standard, Spacelift Cloud, env0 Business, Pulumi Team). Enterprise (200+ engineers): $150K-$1M+/year (HCP Plus, Terraform Enterprise, Spacelift Enterprise, env0 Enterprise, Gruntwork IaC Library). The biggest budget lever is the management platform, not the engine, engines are mostly free.
      What is drift detection and why does it matter?
      Drift is when actual cloud-provider state diverges from what your IaC code declares (someone clicked in the console, an auto-scaling group changed, a tag was modified out-of-band). Drift detection compares actual state to declared state and surfaces the delta. Most modern IaC management platforms (Spacelift, env0, Scalr, HCP Terraform Plus) have drift detection out of the box. Atlantis open-source does not. For regulated buyers and compliance-anchored teams, drift detection is essentially mandatory in 2026.
      Does the IBM acquisition change anything for Terraform users?
      IBM closed its $6.4B acquisition of HashiCorp on February 27, 2025. Through Q2 2026 the post-IBM product strategy clarification is still pending. Public signals so far: HCP Terraform pricing has continued to climb 2024-2025, BSL licensing remains in place, IBM enterprise procurement is now an option for Terraform Enterprise buyers, and the IBM Red Hat / OpenShift positioning may shape future integration directions. For most direct Terraform users the practical impact has been minimal; for procurement-sensitive buyers the IBM ownership is a new variable to evaluate.

      Glossary

      IaC (Infrastructure as Code)
      Provisioning cloud infrastructure through version-controlled code instead of clicking through consoles. Declarative (Terraform, OpenTofu) or imperative (Pulumi, CDK).
      HCL (HashiCorp Configuration Language)
      Declarative configuration language used by Terraform and OpenTofu. Designed for human readability and machine processing.
      State file
      Local or remote file mapping declared IaC resources to actual cloud-provider IDs. Required for plan/apply reconciliation. Managed-state platforms (HCP Terraform, Spacelift, env0) handle this remotely with locking.
      Plan / apply
      Two-phase Terraform / OpenTofu workflow. Plan computes the diff between declared and actual state; apply executes the diff against the cloud provider.
      Drift
      When actual cloud-provider state diverges from declared IaC state. Caused by manual console changes, auto-scaling, or out-of-band edits. Drift detection surfaces deltas.
      GitOps
      Pattern using Git as the source of truth for infrastructure state. Pull-request-driven plan/apply workflows (Atlantis, Spacelift, env0) operationalize GitOps for IaC.
      CDK (Cloud Development Kit)
      Programming-language IaC framework. AWS CDK is the original (TypeScript / Python / Java / C# / Go compiles to CloudFormation). CDK for Terraform (CDKTF) exists for HCL.
      OPA (Open Policy Agent)
      CNCF policy-as-code engine. Used by Spacelift, env0, Scalr, and HCP Terraform (alongside Sentinel) to enforce IaC policy at plan-time.
      BSL (Business Source License)
      License HashiCorp adopted for Terraform on August 10, 2023, replacing MPL-2.0. Adds production-use restrictions targeting competitive vendors. Sparked the OpenTofu fork.
      MPL-2.0 (Mozilla Public License 2.0)
      Permissive open-source license. Used by OpenTofu and the pre-BSL Terraform 1.5.x. Allows commercial use without the BSL production-use restrictions.
      Crossplane composition
      Crossplane pattern for bundling Kubernetes Custom Resources into reusable abstractions. Enables platform teams to expose simplified APIs to internal developers.
      IaC management platform
      Layer that wraps state, policy, drift detection, RBAC, and PR automation around your IaC engine (Terraform / OpenTofu / Pulumi). Examples: Spacelift, env0, Scalr, Atlantis, Terragrunt.

      Final word

      See the full intelligence profile for any product on this page, including verified pricing, vendor trust scores, and review patterns. Browse the Infrastructure as Code (IaC) category page →

      Last updated 2026-05-10. Pricing data is reverified quarterly. Found something inaccurate? Tell us.