HashiCorp's License Change Sparks the OpenTofu Fork
HashiCorp's 2023 Terraform license change triggered the OpenTF fork, soon renamed OpenTofu and placed under Linux Foundation stewardship.
HashiCorp switched Terraform’s license from the open-source Mozilla Public License v2.0 to the Business Source License (BUSL) 1.1 on August 10, 2023 — a source-available but not open-source license explicitly restricting use by direct HashiCorp competitors. Within weeks, the resulting community fork became a Linux Foundation project.
What the license change actually restricted
BUSL 1.1 permitted most existing uses to continue, but prohibited companies competing directly with HashiCorp’s own commercial offerings from incorporating, embedding, or redistributing versions of Terraform released after the change — a meaningful shift from MPL v2’s unrestricted permissions for any user, competitor or not.
The community’s fast, organized response
The reaction was unusually rapid and well-coordinated: on August 25, 2023, the “OpenTF” initiative announced its intention to fork the last MPL-licensed version of Terraform. By September 5, the fork’s manifesto repository had gathered more than 33,000 GitHub stars, with roughly 140 companies and 700 individuals publicly pledging support. On September 20, 2023, the Linux Foundation formally accepted the project, and OpenTF became OpenTofu.
What OpenTofu actually is
OpenTofu forked from the final Terraform code available under MPL 2.0 in the 1.5.x line and initially emphasized a straightforward migration path for existing configurations and state. OpenTofu’s own 1.6 release then added features under its community governance; it should not be confused with Terraform 1.6, which followed HashiCorp’s license change. Compatibility is a tested migration property, not a promise that the two projects can never diverge.
A fork includes an ecosystem, not only source code
Infrastructure tooling depends on providers, modules, registries, state formats, automation integrations, documentation, security response, releases, and maintainers. Copying a repository creates code; sustaining an alternative requires all of those surrounding systems. The pledges, Linux Foundation home, and early release work mattered because they addressed credibility and continuity, not merely compilation.
Providers and modules are especially important because most real configurations use them. Teams evaluating migration need to test provider resolution, lock files, state backends, automation, policy tooling, and plans—not assume command-line similarity proves operational equivalence. State contains sensitive infrastructure mappings and should be backed up and protected before any migration trial.
Neutral governance was the central proposition
OpenTofu’s manifesto emphasized an open-source license, community-driven development, impartial stewardship, and compatibility. A foundation can provide legal and institutional continuity, but governance quality still depends on transparent decisions, diverse maintainers, sustainable funding, security processes, and user participation.
The fork also showed how license risk becomes supply-chain risk. Organizations adopting foundational tools need to track not only vulnerabilities and release support, but also licensing, trademarks, artifact distribution, provider ecosystems, and the authority controlling future versions.
What this means for current users
Terraform and OpenTofu now require separate, current compatibility evaluations. Do not alternate binaries against production state casually. Pin the selected CLI and providers, commit dependency locks, read migration and release notes, run read-only or refresh-aware plans in a controlled environment, and explain every proposed change before apply.
The historical event was a rapid response to a license change; the ongoing engineering question is whether each project meets a team’s requirements for features, support, governance, providers, security, and state safety. That decision should rest on current evidence rather than the assumption that a 2023 fork froze both tools in permanent equivalence.
Why this fork happened so much faster than most
Most open-source license disputes take much longer to produce a viable, well-supported fork — OpenTofu’s speed reflected both the sheer scale of Terraform’s existing user base (motivated to act quickly to avoid being caught by a license change affecting their own tooling) and the direct availability of a neutral home (the Linux Foundation) already experienced hosting exactly this kind of community-governed infrastructure project.
Related:
Sources: