The Golden Age of Open Infrastructure
Before the controversy, Terraform existed in a state of grace. Governed by a permissive Mozilla Public License (MPL 2.0), it was free to use, modify, and even embed into commercial products. This open approach was its superpower. A massive community of developers
and companies adopted it as the standard for Infrastructure as Code (IaC), creating a rich ecosystem of tools and expertise. You could use it to manage your company’s internal servers or build a whole new business on top of it without friction. This frictionless adoption made Terraform the bedrock of modern cloud operations, a tool so foundational that its license was something most users never had to think about.
The Day the License Changed
In August 2023, HashiCorp announced it was switching Terraform and other core products from the open-source MPL 2.0 to the Business Source License (BSL 1.1). While the code remained “source-available,” meaning you could still see it, the BSL was not a true open-source license. It came with a crucial restriction: you could no longer use Terraform to create a product that competed with HashiCorp's own commercial offerings, like Terraform Cloud. For the average developer using Terraform for their own company's infrastructure, nothing changed immediately. But for the many companies that had built services on top of Terraform, the ground had just shifted beneath their feet. The move was a legal tripwire, turning a technical tool into a source of business risk.
A Business Decision, Not a Technical One
HashiCorp's reasoning was straightforward: it needed to protect its business. The company, which had gone public in 2021, was facing financial pressure. Competitors were using Terraform's open-source code to build rival platforms that directly challenged HashiCorp’s paid services, essentially profiting from their work without contributing back. The switch to BSL was a defensive move designed to wall off this competitive use and ensure HashiCorp could monetize the ecosystem it had built. It was a clear signal that while the company valued its community, it had to prioritize its own sustainability, even if it meant alienating a portion of that community.
The Community Strikes Back: The Birth of OpenTofu
The backlash from the open-source world was swift and decisive. A coalition of companies and developers, feeling that the spirit of the project had been betrayed, published the "OpenTofu Manifesto." They asked HashiCorp to reverse its decision; when the company refused, they did what open-source communities do best: they forked the project. They took the last version of Terraform released under the MPL license (v1.5) and created a new, truly open-source version called OpenTofu. Housed under the prestigious Linux Foundation, OpenTofu promised to be a community-driven, impartial, and legally unambiguous alternative—a drop-in replacement for anyone wary of Terraform's new restrictions.
A Fork in the Road for Developers
The license change fractured the once-unified Terraform landscape. Suddenly, developers and organizations faced a choice. Do they stick with HashiCorp's Terraform, accepting the new license and the potential for future changes, or migrate to the community-led OpenTofu? This decision wasn't about features, as the two were nearly identical at the start. It was about philosophy and risk. The saga proved that for critical infrastructure tools, the legal framework and governance model can be more consequential than any single feature. A tool's code defines what it can do, but its license defines the trust, freedom, and predictability of the ecosystem built around it. In the end, that's what mattered most.
