Terraform vs Pulumi: Which Infrastructure as Code Tool in 2026?

Terraform's HCL versus Pulumi's TypeScript, Python, Go, C# and Java: how the two leading infrastructure-as-code tools differ on workflow, state, pricing and licensing in 2026.

The Pulumi logo, with a cube-shaped icon in yellow, pink and purple beside the wordmark, on a white background
The Pulumi logo. Image: Pulumi.

Terraform and Pulumi both let you define cloud infrastructure in code and apply it repeatably, but they take opposite approaches to the "code" part: Terraform describes resources in HashiCorp Configuration Language (HCL), a declarative, infrastructure-specific syntax, while Pulumi lets you write the same declarations in TypeScript, Python, Go, C#, Java or other general-purpose languages, using real loops, functions and package managers. Neither tool is objectively "better" in 2026 — Terraform has the larger ecosystem, more mature state tooling and the bigger provider registry, while Pulumi suits teams that want to reuse existing software engineering practices and avoid a second, infrastructure-only language. The right pick depends on your team's skills, your governance needs and how much you're willing to pay for a managed control plane.

Quick facts

  • Terraform: HashiCorp; HCL (declarative) and a JSON variant; latest stable release v1.17.2 (November 11, 2026); Business Source License 1.1 since v1.6, converting to MPL 2.0 four years after each release.
  • Pulumi: Pulumi Corporation; TypeScript/JavaScript, Python, Go, .NET (C#/F#/VB), Java, plus Pulumi YAML and HCL as config options; latest stable release v3.276.0 (November 12, 2026); core CLI and SDKs are Apache License 2.0.
  • Pricing: HCP Terraform starts at $0.10 per managed resource per month (Essentials); Pulumi's paid Essentials plan starts at $40/month for up to 500 IaC resources, with a free tier for individuals.
  • State: Terraform defaults to a local terraform.tfstate file and recommends HCP Terraform or a remote backend for teams; Pulumi defaults to the managed Pulumi Cloud backend but also supports self-managed backends (S3, Azure Blob, GCS, Postgres, local).

What Is Terraform?

Terraform is HashiCorp's infrastructure-as-code tool: you describe the cloud resources you want — virtual machines, networks, databases, DNS records — in HCL, and Terraform computes a plan to create, change or destroy real infrastructure to match that description. It has been the default choice for multi-cloud IaC since its 2014 launch, and it remains the tool most job postings and certification tracks assume you already know. If you need a primer on the basics before diving into this comparison, Pandromeda's explainer on what Terraform is and how infrastructure as code works covers the fundamentals.

What Is Pulumi?

Pulumi is a newer (2018) infrastructure-as-code platform built on the same core idea — desired-state resources, a plan/apply-style workflow, and provider plugins for AWS, Azure, Google Cloud and hundreds of other services — but it swaps HCL for general-purpose programming languages. A Pulumi program is a normal TypeScript, Python, Go, Java or .NET project: you import a cloud provider's SDK, call functions to declare resources, and use the host language's own conditionals, loops, classes and package managers (npm, pip, Go modules, NuGet, Maven) instead of a Terraform-style module system. Under the hood, Pulumi's CLI still builds a resource graph and calculates diffs the same way Terraform does; the difference is almost entirely in the authoring language and developer experience.

Language and Workflow: HCL vs Real Code

This is the core decision point. Terraform's HCL is purpose-built for describing infrastructure: it's declarative, has a small, learnable grammar, and is easy for reviewers to read even if they've never touched the language before. Its limits show up when you need genuine programming logic — loops, conditionals and reusable abstractions exist in HCL (for_each, count, dynamic blocks, modules) but they feel bolted onto a configuration language rather than native to a programming one.

Pulumi's pitch is that your infrastructure code should be able to do anything your application code can do, because it's written in the same language. You can write unit tests with your existing test framework, share logic through ordinary libraries instead of a bespoke module registry, and lean on your IDE's autocomplete and type checking against the actual provider SDK types. The tradeoff is that Pulumi programs can become as complex — and as hard to reason about — as any other software project, which is exactly the complexity HCL was designed to avoid.

Both tools follow a broadly similar command-line workflow: write configuration, preview the planned changes (terraform plan or pulumi preview), then apply them (terraform apply or pulumi up).

State Management and Backends

Terraform tracks the infrastructure it manages in a state file. By default that's a local JSON file named terraform.tfstate, with a backup kept alongside it; HashiCorp's own documentation recommends moving to HCP Terraform or another remote backend for any team setup, both for locking (to stop two people applying at once) and for secure, shared access.

Pulumi defaults to its own hosted Pulumi Cloud backend, which can also be self-hosted for organizations that want to run it on their own infrastructure. If you'd rather not use Pulumi Cloud at all, Pulumi supports "DIY" backends — Amazon S3, Azure Blob Storage, Google Cloud Storage, S3-compatible object stores such as MinIO or Ceph, a self-managed PostgreSQL database, or the local filesystem. Regardless of backend, Pulumi encrypts secret values in state using a per-stack encryption provider (Pulumi Cloud defaults to a server-side key), and cloud credentials themselves are never written to state.

Providers, Ecosystem and Registry

Terraform's biggest structural advantage is the size and maturity of its provider ecosystem. The public Terraform Registry lists thousands of providers and modules covering essentially every major cloud and SaaS API, built up over a decade of community and vendor contributions. Pulumi covers the same major clouds (AWS, Azure, Google Cloud, Kubernetes) with its own native providers, and it also ships a "bridged" mechanism that automatically generates Pulumi providers from existing Terraform providers — which gives Pulumi broad coverage without needing an independent provider for every API, at the cost of occasionally lagging a Terraform-native provider's newest features.

DimensionTerraformPulumi
Authoring languageHCL (declarative), plus a JSON variantTypeScript, JavaScript, Python, Go, .NET (C#/F#/VB), Java; also Pulumi YAML and HCL
Core licenseBusiness Source License 1.1 (source-available, converts to MPL 2.0 after 4 years per release)Apache License 2.0 (OSI-approved open source)
Latest stable release (Nov 2026)v1.17.2 (Nov 11, 2026)v3.276.0 (Nov 12, 2026)
Default state backendLocal terraform.tfstate fileManaged Pulumi Cloud
Self-managed state optionsRemote backends (community/partner-maintained) or HCP TerraformS3, Azure Blob, GCS, S3-compatible stores, PostgreSQL, local filesystem, or self-hosted Pulumi Cloud
Policy as codeSentinel (HashiCorp's own policy language) and Open Policy Agent, via HCP TerraformCrossGuard — policies in TypeScript, Python, JavaScript or OPA/Rego; core framework is open source
Managed cloud offeringHCP Terraform (formerly Terraform Cloud)Pulumi Cloud

What About CDK for Terraform?

If you're specifically weighing "Terraform CDK vs Pulumi" rather than plain HCL versus Pulumi, there's an important wrinkle: CDK for Terraform (CDKTF) was HashiCorp's own answer to Pulumi's pitch, letting you write Terraform configuration in TypeScript, Python, Java, C# or Go instead of HCL while still using the standard Terraform provider and module ecosystem underneath. However, HashiCorp's own CDKTF documentation now carries a deprecation notice stating it "is deprecated as of December 10, 2025" and that HashiCorp "no longer supports or maintains" it. In practice, that collapses the "general-purpose language on top of Terraform" niche back down to one actively maintained option — Pulumi — if writing infrastructure in a full programming language rather than HCL is a hard requirement for your team.

Pricing: HCP Terraform vs Pulumi Cloud

If you're comparing the vendors' own hosted platforms rather than running either tool entirely yourself, the pricing models look different on paper but land in a similar place for small teams. Per HashiCorp's pricing page, HCP Terraform's Essentials tier starts "at $0.10 per month per resource" (listed alongside an equivalent $0.00013 hourly rate), Standard starts at $0.47 per resource per month, and Premium at $0.99 per resource per month; new accounts get a $500 HCP trial credit, and HashiCorp sells a custom-priced, self-managed Enterprise edition on top. HashiCorp's own FAQ on that page asks "Is there still a free version of HCP Terraform?" — free-tier availability for hosted IaC platforms has shifted more than once over the past couple of years, so confirm the current answer directly on hashicorp.com before you plan around it.

Pulumi's pricing page lists four editions: a $0 Free tier (one user, 500 workflow minutes, 25 secrets, 10,000 API calls per month, and no charge for managed resources), Essentials at $40/month (40 credits, up to 500 IaC resources, unlimited users, with overage billed per resource at roughly $0.1825/month), Pro at $400/month (400 credits, up to 2,000 IaC resources, with volume-discounted overage from about $0.365/month per resource), and a custom-priced Enterprise tier. Both vendors bill usage-based add-ons hourly in practice, so the monthly figures above are full-month equivalents — treat all of these as vendor-published list prices, not independent benchmarks, and check both pricing pages for your actual resource counts before choosing.

License and Open-Source Status

Terraform's CLI has been licensed under the Business Source License 1.1 since version 1.6 in 2023 — a source-available license that lets you read, modify and use Terraform for non-competing purposes, but restricts building a competing managed-Terraform offering; each release converts to the fully open MPL 2.0 four years later. Pulumi's core engine and language SDKs, by contrast, ship under the OSI-approved Apache License 2.0, making the CLI and SDKs unambiguously open source, while Pulumi Cloud itself remains a proprietary hosted product. HashiCorp's licensing change is also what prompted the Linux Foundation-backed OpenTofu fork; if that history — or whether to use OpenTofu instead of either tool here — is what you're trying to untangle, Pandromeda's comparison of Terraform and OpenTofu covers that fork in detail rather than this piece, which focuses on Terraform versus Pulumi's actual technical differences.

Policy as Code and Testing

Both ecosystems offer a way to enforce organizational rules on infrastructure before it's applied. HCP Terraform supports Sentinel, HashiCorp's own policy-as-code language, as well as Open Policy Agent (OPA) policies, with checks run against the generated plan and enforcement levels ranging from advisory to hard-mandatory. Pulumi's equivalent is CrossGuard, which lets you write policies in TypeScript, JavaScript, Python or OPA/Rego; Pulumi describes CrossGuard's core framework as open source and available on every edition, including the free Individual tier, with centralized policy management reserved for Enterprise customers. For testing infrastructure code itself, Pulumi's advantage is being able to reuse the host language's own unit-testing tools directly against your infrastructure program, while Terraform ships its own, HCL-native terraform test framework for writing assertions against plans and applies.

Release Cadence and Community

Both projects ship frequently. Terraform's GitHub releases show point releases roughly every one to three weeks through late 2026 (v1.17.2 on November 11, following v1.17.1 on October 28 and v1.16.7 on October 22), and the hashicorp/terraform repository has accumulated roughly 50,000 GitHub stars over its decade of public development. Pulumi ships on a similarly fast cadence — v3.276.0 landed November 12, 2026, one day after Terraform's latest patch, with multiple point releases most weeks — and Pulumi's own blog noted its open-source repository passing 20,000 GitHub stars in 2024, with third-party trackers reporting continued growth since. Terraform's larger, older community generally means more Stack Overflow answers, tutorials and third-party modules; Pulumi's is smaller but skews toward teams already comfortable in a general-purpose language.

Which Should You Use in 2026?

Choose Terraform if your team already knows HCL or is building from scratch with no strong language preference, if you need the widest possible provider and module coverage, or if your organization has standardized on HashiCorp's stack (Vault, Consul, Nomad) and wants consistent tooling across it. Choose Pulumi if your engineers are strongest in TypeScript, Python, Go, Java or C# and would rather write infrastructure in that language than learn HCL, if you want to unit-test infrastructure code with the same tools you already use for application code, or if you want an Apache-2.0-licensed core without HashiCorp's BSL terms. Neither choice is permanent or exclusive — Pulumi can consume Terraform-derived providers, and teams migrating off Terraform for licensing reasons also have the option of OpenTofu rather than switching languages entirely. Whichever you pick, verify current pricing, license terms and provider coverage directly against terraform.io and pulumi.com before committing, since both have changed meaningfully within the past year.

Frequently asked questions

Is Terraform still open source?

Not in the OSI sense. Since version 1.6 (2023), the Terraform CLI has been licensed under the Business Source License 1.1, a source-available license that permits reading, modifying and most non-competing uses, but restricts offering a competing managed Terraform service; each release converts to the fully open MPL 2.0 four years after it ships. Pulumi's core engine and SDKs, by comparison, use the OSI-approved Apache License 2.0.

Can Pulumi use Terraform's providers?

Yes, indirectly. Pulumi has native providers for major clouds, and it also uses a bridging mechanism that generates Pulumi providers from existing Terraform providers, which extends Pulumi's coverage to much of the same ecosystem Terraform supports.

Which tool is better if my team doesn't know TypeScript, Python, Go, Java or C#?

Terraform is usually the easier starting point in that case, since HCL is a small, purpose-built configuration language rather than a general-purpose one, and most IaC tutorials, certifications and job listings still assume HCL knowledge.

Does Pulumi support writing infrastructure in HCL?

Pulumi's documentation lists HCL as one of its supported configuration languages alongside TypeScript, JavaScript, Python, Go, .NET and Java, plus Pulumi's own YAML format, though most Pulumi users write in a general-purpose language to get the full programming-language benefits.

What happened to CDK for Terraform (CDKTF)?

HashiCorp deprecated CDK for Terraform as of December 10, 2025, according to its own documentation, and no longer supports or maintains it. That removes HashiCorp's own general-purpose-language option for writing Terraform configuration, leaving Pulumi as the main actively maintained alternative for teams that want to avoid HCL.

Which is cheaper, HCP Terraform or Pulumi Cloud?

It depends on your resource count and team size. Pulumi offers a $0 Free tier for individuals with no charge for managed resources, and its paid Essentials tier starts at $40/month for up to 500 IaC resources. HCP Terraform has no advertised perpetual free tier as of late 2026 and prices usage from $0.10 per resource per month on its Essentials tier. Both vendors' numbers are list prices that can change, so check hashicorp.com and pulumi.com directly for your situation.

Sources

More on Terraform →TerraformPulumiInfrastructure as CodeDevOpsCloud EngineeringHCP Terraform
Felix Moreau
Written byFelix Moreau

Felix Moreau writes Pandromeda's software coverage and how-to guides. He covers Windows, macOS and Linux updates, the apps people rely on, emulators and developer tools, and turns official documentation into clear, numbered steps that work on the current version.

More from Software & Guides

See all