OpenTofu: The Open Response to Terraform’s License Change

Actualizado: 2026-05-03

OpenTofu is the community’s organised response to Terraform’s licence change to the Business Source License. On 20 September 2023, a coalition of companies and developers published the OpenTF Manifesto^[1], forked the last MPL commit of Terraform (v1.5.5), and the project was accepted by the Linux Foundation weeks later. If you manage infrastructure with Terraform, this story defines which tool you’ll use for the next few years and under what legal terms.

Key takeaways

• OpenTofu is a fork of Terraform 1.5.5 (last MPL 2.0 commit), governed by the Linux Foundation.
• Full file compatibility: .tf, .tfstate, and .tfvars work without modification.
• AWS, Azure, GCP, and all Terraform Registry providers are reusable as-is.
• The migration decision depends on your profile: internal user vs. product/service builder on Terraform.
• A gradual strategy (isolated environment → parallel CI → pipeline by pipeline) minimises risk.

Context: What Happened With Terraform

In August 2023, HashiCorp switched its entire product suite — Terraform, Vault, Consul, Nomad, Packer — from the Mozilla Public License v2 (OSI-approved) to the Business Source License v1.1. The BSL isn’t strictly closed source, but imposes a key restriction:

• Free use permitted for any purpose that doesn’t compete with HashiCorp’s commercial offerings.
• Broad definition of competition: offering a managed service or product whose principal value derives from software under BSL.
• Automatic revert to MPL 2.0 after 4 years (today’s code returns to MPL in August 2027).

For users who only apply Terraform to their own infrastructure, the impact is nil. For the ecosystem — service providers, tools orbiting Terraform, enterprise integrations — the change was perceived as breaking the implicit open-source contract.

OpenTofu’s Birth

After six weeks of public organisation on GitHub under the OpenTF name, the project was:

• Forked from the last MPL commit of Terraform (version 1.5.5).
• Renamed to OpenTofu to avoid trademark conflicts.
• Accepted as a Linux Foundation project in September 2023, ensuring neutral governance.
• Backed by Spacelift, Gruntwork, env0, Harness, Scalr, and dozens more.

The first alpha appeared weeks after the fork. The neutral governance architecture contrasts with the single-company model controlling Terraform — and it’s the reason why projects like Vault are evaluated differently when the vendor changes its terms.

Compatibility in Practice

OpenTofu maintains full file compatibility. The tofu binary replaces terraform in commands:

tofu init
tofu plan
tofu apply

Providers (AWS, Azure, GCP, Cloudflare, etc.) are exactly the same — their licence doesn’t change, only the Terraform core’s. OpenTofu can consume any provider from the Terraform Registry without modification.

In the medium term, some divergence is expected: OpenTofu will add features the community requests but HashiCorp didn’t prioritise. That divergence will be incremental, not disruptive.

Migrate or Not?

The decision depends on usage profile.

Migrate to OpenTofu if:

• Your organisation has strict open-source licence policies (regulated sectors, public bodies).
• You build products or services on Terraform where BSL could apply to you as “competitor”.
• You’re part of the ecosystem (tool provider, consultancy) and governance neutrality carries legal weight.
• You want to bet on the community trajectory long-term.

Stick with Terraform if:

• You only use it internally to manage your own infrastructure.
• You depend on Terraform Cloud or HashiCorp-specific integrations.
• You have active enterprise contracts with HashiCorp.
• You prefer waiting for OpenTofu to reach proven stability before adopting.

Recommended Migration Strategy

For teams that decide to migrate, a gradual approach minimises risk:

1. Validate in an isolated environment. Test tofu init/plan/apply against a test environment; verify state reads correctly and plans are identical.
2. Run in parallel. In CI, compare terraform plan and tofu plan output to detect differences before switching.
3. Migrate pipeline by pipeline. No need to change everything day one. OpenTofu and Terraform can coexist while plans match.
4. Update surrounding tools. Atlantis, Terragrunt, and similar are adding explicit OpenTofu support.

Long-term Implications

This change has a broader reading: it’s one more sign of the tension between infrastructure software creators and cloud providers that monetise it. The pattern — licence change followed by community fork accepted by a neutral foundation — was already seen with Elasticsearch/OpenSearch. Neutral foundations (Linux Foundation, CNCF, Apache Foundation) protect the continuity of infrastructural projects better than individual companies. It’s a criterion worth applying when evaluating any IaC tool or observability tool for critical infrastructure.

For the next infrastructure project you adopt, the right question isn’t just “what does it do?” but “who governs the code and what incentives do they have?”.

Conclusion

OpenTofu is a technically viable option today, with full compatibility with existing Terraform, and very likely dominant medium-term in the IaC space. Neutral governance under the Linux Foundation reduces the risk of future surprises. For most organisations, the decision isn’t urgent — but it’s worth making it informed, not by default.

1. OpenTF Manifesto