The License Shift That Fractured an Ecosystem
In August 2023, HashiCorp did something that surprised exactly no one who had been paying attention to open-source licensing trends over the past decade. They moved Terraform from the Mozilla Public License 2.0 to the Business Source License 1.1. The BSL is not open source by OSSD definition, which meant that any organization at a certain scale would need to either negotiate with HashiCorp or find an alternative. The company argued this was necessary to protect their commercial interests against cloud providers building on Terraform without contributing back. Whether that argument held water depends largely on your perspective on what open source actually means, but the practical effect was immediate and severe.
Within weeks, the Linux Foundation moved. By September 2023, OpenTofu had been announced as a community-driven fork backed by major infrastructure companies. The speed of this response told you something important: organizations had been waiting for permission to do this, not necessarily the technical capability. By January 2024, OpenTofu hit 1.0 stable. It was, at that point, a faithful reproduction of Terraform’s functionality. It worked. It didn’t break things. For many organizations, this was enough. The fork was no longer theoretical.
When the Fork Actually Pulled Ahead
For months after OpenTofu 1.0 shipped, the narrative was predictable: it’s a good insurance policy, a hedge against future licensing changes, but Terraform remains the reference implementation. Then, in mid-2024, OpenTofu 1.8 arrived with something the community had been requesting for years: native provider-defined functions. This was not a minor feature. The ability to define functions within a provider, rather than requiring wrapper layers or external tooling, represented a genuine capability gap that Terraform still had not addressed.
I want to be precise about what this means. For years, practitioners had worked around this limitation through a combination of Terraform modules, locals blocks, and external data sources. It was workable but inelegant. When OpenTofu shipped this, it was the first moment where the fork was not just maintaining parity with the upstream project, but actively shipping features the upstream had deprioritized. The market noticed. This was not about HashiCorp malice or OpenTofu heroics. It was about prioritization, governance, and what happens when an open-source project can move faster than a company-backed one.
The IBM Acquisition and the Acceleration
HashiCorp’s acquisition by IBM closed mid-2024 for approximately 6.4 billion dollars. On paper, this should have been good news for Terraform users. IBM is a major infrastructure player with long-standing commitments to open-source projects. In practice, the post-acquisition product roadmap updates did almost nothing to reassure the community about the licensing direction or future commitment to open development. The messaging remained cautious and corporate. The open-source community, quite rightly, began planning for the scenario where the trend continued rather than reversed.
This is the moment where migration conversations shifted from hypothetical to urgent. Organizations that had been monitoring OpenTofu as an option began running serious pilots. The combination of licensing uncertainty, the IBM ownership transition, and the technical parity of the fork created the conditions for real migration rather than theoretical hedging.
Where We Actually Are: The Production Numbers
By early 2025, the OpenTofu registry had crossed 2,000 mirrored providers. This is not hypothetical coverage. For the vast majority of organizations running infrastructure on AWS, GCP, or Azure, functional parity is essentially complete. The long tail of specialized providers is still spottier, but for mainstream infrastructure use cases, the argument about fragmentation or incomplete tooling no longer holds up. OpenTofu official documentation and changelog shows a project that is methodical about its releases and conservative about breaking changes.
A Spacelift survey from late 2024 found something worth sitting with: 38 percent of organizations using Terraform were either actively evaluating or had already migrated to OpenTofu. The drivers were consistent across respondents. Cost uncertainty and licensing questions accounted for 91 percent of the stated reasons. This is not about philosophical opposition to commercial software. It is about predictability. Organizations want to know what the rules are, and they want confidence those rules will not change in ways that require painful re-architecture later.
I have worked through enough platform migrations to know what successful ones look like. They move methodically. They start with non-critical workloads. They build tooling to smooth the transition. What I am seeing with OpenTofu adoption follows that pattern almost exactly. Organizations are not abandoning Terraform in crisis mode. They are planning migrations that will take months, testing provider behavior, and running dual-stack infrastructure during transition windows. This is how mature organizations handle platform decisions.
What This Means for Your Infrastructure
The fork is no longer a theoretical option or a political statement. It is a production-ready alternative backed by major companies, with a governance model that is explicitly open, and with a feature roadmap driven by community request rather than vendor prioritization. The quality of implementation is solid. The pace of development is steady. The risk profile has shifted significantly since August 2023.
This does not mean Terraform is obsolete or that HashiCorp’s decisions were catastrophic. Terraform remains widely used, well-maintained, and appropriate for many organizations. What it does mean is that the ecosystem now operates with genuine choice for the first time in a decade. Organizations can make decisions based on their actual constraints rather than technological lock-in. The fork has normalized this conversation in a way that benefits everyone, including those who remain on Terraform.
If you are currently on Terraform and considering your options, the honest assessment is that OpenTofu is mature enough to migrate to with proper planning. If you are building new infrastructure, the choice is more genuinely open than it has been in years. Linux Foundation OpenTofu project page provides solid grounding for understanding the governance and roadmap. Eighteen months after the fork, the infrastructure provisioning space looks different than it did. That is worth understanding clearly, without hype in either direction. I am curious what your actual experience has been. Have you evaluated OpenTofu for your infrastructure? What drove your evaluation, and what did you find?