OpenTofu vs Terraform

Overview

OpenTofu is a fork of Terraform created in 2023 after HashiCorp relicensed Terraform under the Business Source License (BSL). Governed by the Linux Foundation, OpenTofu stays open source under MPL 2.0 and aims to be a drop-in replacement. The two tools share a heritage and remain broadly compatible, so the decision is mostly about licensing, governance, and which roadmap you prefer.

Key Differences

The license is the central distinction. Terraform's BSL restricts using the software to compete with HashiCorp's commercial products and is not OSI-approved. OpenTofu remains under the MPL 2.0, an established open-source license, and is governed by a community steering committee under the Linux Foundation rather than a single vendor. For organizations with open-source policies or concerns about vendor control, this is decisive.

Functionally, the two have diverged slightly since the fork. OpenTofu added features such as native state encryption, early variable evaluation, and provider-level iteration. Terraform has continued to evolve with capabilities like Stacks and deeper integration with HashiCorp Cloud Platform. Both still use HCL and work with the shared public provider registry, so most configurations run on either with minimal change, though the gap may widen over time.

Ecosystem and support favor Terraform on mindshare. It has the largest community, the most documentation, and first-party commercial support through HCP Terraform. OpenTofu's adoption is growing and is backed by vendors like Spacelift and Scalr, but its commercial ecosystem is younger.

When to Choose OpenTofu

Choose OpenTofu when an open-source license and neutral governance matter. It suits organizations that adopted Terraform before the relicense and want to avoid the BSL, teams that value community control, or anyone who wants features like built-in state encryption. Migration from older Terraform is typically straightforward.

When to Choose Terraform

Choose Terraform when you want first-party support from HashiCorp (now part of IBM), need the newest Terraform-only features such as Stacks, or value being on the canonical, most-documented tool. For teams already invested in HCP Terraform, staying on Terraform is the path of least resistance.

Verdict

Both are capable, and for most existing configurations they behave the same today. Pick OpenTofu for open licensing and community governance; pick Terraform for first-party support and the latest official features. Watch the roadmaps, as continued divergence may make compatibility a larger factor in the future.