All three are Infrastructure as Code tools: you declare the cloud resources you want and the tool makes reality match. They share a model β but differ on language, licence and governance, and those differences are exactly what the 2023 Terraform licence change threw into sharp relief. This is how to tell them apart and pick one.
The 15-second version.Terraform is the incumbent (HCL, huge ecosystem, now source-available BSL licence). OpenTofu is the open-source (MPL) fork of Terraform β a near drop-in replacement under the Linux Foundation. Pulumi takes a different path: write your infra in a real programming language (TypeScript, Python, Go, C#β¦). New to IaC? Start with what IaC is first.
Common ground The shared model
Despite the differences, all three work the same way underneath β learn this once and it transfers:
Declarative
Desired state
You describe the end result, not the steps. The tool diffs your code against reality and reconciles.
Providers
Cloud plugins
The same provider plugins (AWS, GCP, Azure, Kubernetes, β¦) β Pulumi and OpenTofu both build on Terraform's provider ecosystem.
State
A record of reality
A state file maps your code to real resources so the tool can compute an accurate diff and safely delete what you removed.
Plan β apply
Preview, then act
Show the diff (create/change/destroy), review it, then apply. Dependencies resolve as a graph (DAG).
Key insight: because Pulumi and OpenTofu reuse Terraform's provider model, the concepts (resources, state, plan/apply, modules) are portable. The real choice is how you express the config and who governs the tool β not a different mental model.
The incumbent Terraform
π£ Terraform (HashiCorp, 2014)
Strengths The de-facto standard: the largest provider & module ecosystem (Terraform Registry), the most jobs, docs, examples and Stack Overflow answers. Declarative HCL is purpose-built for config and easy to read. Mature tooling (Cloud/Enterprise, Sentinel policy, workspaces).
Trade-offs HCL is a domain-specific language β loops (for_each), conditionals and abstraction can feel awkward vs a real language. Since Aug 2023 it's under the BSL (source-available, not open source), which alienated some users and vendors.
Licence flag: Terraform β€ 1.5.5 was open source (MPL 2.0); from 1.6 it's BSL 1.1. Fine for the vast majority of users β the restriction targets companies offering a competing Terraform-as-a-service. This change is what spawned OpenTofu.
The fork OpenTofu
π OpenTofu (Linux Foundation, 2023)
Strengths A community fork of Terraform 1.5.5 created in response to the BSL change β open source (MPL 2.0), vendor-neutral, governed by the Linux Foundation. Aims to be a near drop-in replacement: same HCL, same providers, state-compatible; often you just swap the terraform command for tofu. It's now adding features of its own (e.g. client-side state encryption, provider-defined functions, early variable evaluation).
Trade-offs Younger, with a smaller (fast-growing) community; it is diverging from Terraform over time, so 100% parity isn't guaranteed forever. Some managed platforms and modules still assume the terraform binary.
Mental model: OpenTofu is to Terraform roughly what a community fork is to its upstream β same language and workflow, different licence & steward. If the BSL licence is a blocker for you, OpenTofu is the low-friction escape hatch.
The different path Pulumi
𧬠Pulumi (2018)
Strengths Write infrastructure in a general-purpose language β TypeScript, Python, Go, C#, Java β so you get real loops, functions, classes, packages, IDE autocomplete and unit tests. Great when infra is dynamic or your team already lives in that language. Apache 2.0 licensed; reuses Terraform providers under the hood.
Trade-offs A real language means real complexity β you can write tangled, imperative infra if undisciplined. Smaller ecosystem and talent pool than Terraform/HCL. State defaults to the hosted Pulumi Cloud (self-managed backends exist, e.g. object storage).
The core trade: HCL constrains you toward simple, declarative config (a feature and a limit). Pulumi gives you a full language (power and the rope to hang yourself). Pick based on how much programmability your infra genuinely needs.
At a glance Head-to-head
Terraform
OpenTofu
Pulumi
Language
HCL (DSL)
HCL (DSL)
TS Β· Python Β· Go Β· C# Β· Java
Licence
BSL 1.1 (source-available)
MPL 2.0 (open source)
Apache 2.0 (open source)
Governance
HashiCorp (IBM)
Linux Foundation
Pulumi Corp
Providers
Terraform Registry
Terraform providers (own registry)
Terraform providers + native
State
File / TF Cloud / remote backends
Same + client-side encryption
Pulumi Cloud / self-managed
CLI
terraform
tofu
pulumi
Testing
Limited (native test framework, Terratest)
Same lineage
Native unit tests in your language
Ecosystem / hiring
Largest
Growing fast
Moderate
Best whenβ¦
You want the standard & the BSL is fine
You want Terraform, open source
You want a real language & programmability
Show me Same stack, three ways
The exact same resource β a Google Cloud Storage bucket β in each tool. Note that Terraform and OpenTofu HCL are identical.
Terraform & OpenTofu β main.tf (identical HCL)
resource"google_storage_bucket""assets" {
name = "shop-prod-assets"
location = "US"
}
Pulumi β TypeScript
import * as gcp from"@pulumi/gcp";
const assets = new gcp.storage.Bucket("assets", {
name: "shop-prod-assets",
location: "US",
});
Pulumi β Python
import pulumi_gcp as gcp
assets = gcp.storage.Bucket("assets",
name="shop-prod-assets",
location="US")
The commands
# Terraform # OpenTofu # Pulumi
terraform init tofu init pulumi stack init
terraform plan tofu plan pulumi preview
terraform apply tofu apply pulumi up
Where a real language pays off: creating ten buckets is a for loop and an array in Pulumi; in HCL it's for_each over a map β doable, but the more logic you need (conditionals, computed names, shared helpers), the more a general-purpose language starts to feel natural.
The context The licence story
You can't understand this landscape without the 2023 timeline β it's why OpenTofu exists and why the choice is now partly about governance, not just tech.
When
What happened
2014
HashiCorp releases Terraform under the open-source MPL 2.0.
Aug 2023
HashiCorp relicenses Terraform (and its other tools) to the BSL 1.1 β source-available, restricting competing commercial use.
Sep 2023
The community forks Terraform 1.5.5 as OpenTofu; it joins the Linux Foundation, staying MPL 2.0.
2024β
IBM acquires HashiCorp. OpenTofu ships features Terraform lacks (state encryption); the two diverge.
Does the BSL affect you? For almost all end users building their own infrastructure β no. It restricts offering a competing Terraform-as-a-service product. Still, some organisations choose OpenTofu on principle (open-source governance) or to avoid future licence risk. That's a policy call, not a technical one.
Decide How to choose
Pick
π£ Terraform
You want the industry standard, the biggest ecosystem & talent pool, and the BSL licence isn't a concern. The safe default.
Pick
π OpenTofu
You want everything Terraform offers but need a truly open-source licence & vendor-neutral governance β or want its extras like state encryption.
Pick
𧬠Pulumi
Your team prefers a general-purpose language, your infra needs real programmability, or you want first-class unit testing in-language.
Rules of thumb. Greenfield & pragmatic β Terraform. Same, but open-source matters to you β OpenTofu (trivial to switch, HCL is identical). Devs who want code, loops & tests over config files β Pulumi. And whichever you choose, apply the IaC best practices: remote locked state, plan-in-CI, no secrets in code.
Can I migrate later?
Terraform β OpenTofu is usually near-trivial today (same HCL & state) but gets harder as they diverge. Terraform/OpenTofu β Pulumi is a bigger lift (different language), though Pulumi provides converters and can adopt existing state. As always, the state file β not the code β is the thing you must migrate carefully.
Cheat sheet
Question
Short answer
What do all three share?
Declarative desired-state, providers, state files, planβapply, a dependency graph.
Terraform language / licence?
HCL Β· BSL 1.1 (source-available since v1.6).
What is OpenTofu?
Open-source (MPL) fork of Terraform under the Linux Foundation; near drop-in, CLI tofu.
What makes Pulumi different?
Write IaC in a real language (TS/Python/Go/C#/Java); Apache 2.0.
Why does OpenTofu exist?
The Aug 2023 Terraform BSL relicence prompted a community fork.
Does BSL affect most users?
No β it targets competing TF-as-a-service, not your own infra.
Safe default?
Terraform. Want open source? OpenTofu. Want a real language? Pulumi.
Knowledge check
Six questions. Pick an answer for each, then check your score.