The Fork That Became Inevitable
When HashiCorp announced the Business Source License shift in August 2023, most of us in infrastructure automation expected the usual open-source theater. Companies change licenses. Projects fork. Noise happens. Then everyone moves on. This time feels different. The Linux Foundation-backed OpenTofu fork has crossed from “interesting alternative” into genuine competitive territory, and if you’re running infrastructure at any meaningful scale, you need to understand why.
The catalyst was simple: HashiCorp needed to protect its cloud business from vendors building competitive offerings on top of open-source Terraform. The BSL made sense from their vantage point. But it broke the social contract with thousands of teams who had built their entire infrastructure automation stack on the assumption of true open-source freedom. OpenTofu emerged as the response, backed by the Linux Foundation and a coalition of enterprise infrastructure leaders who understood the long-term risk of a single company controlling the canonical version of infrastructure-as-code tooling.
State Encryption Changes the Playing Field
Here’s where things get concrete. OpenTofu 1.9, released in late 2025, shipped with native end-to-end state encryption built directly into the open-source tier. This is not a minor feature addition. Terraform state files contain your infrastructure’s DNA: database passwords, API keys, private IPs, resource IDs. You absolutely do not want those sitting unencrypted on disk or in shared storage. Terraform Enterprise has offered state encryption for years, but the open-source version? You had to bolt on external tooling, manage keys separately, or pay for the hosted service. OpenTofu’s approach is cleaner. It’s the kind of feature that makes infrastructure teams sleep better at night, and it’s available to everyone without license restrictions.
Terraform 1.10 remains largely incremental. The HashiCorp team has focused on performance improvements and bug fixes, which are valuable. But they haven’t addressed the encryption gap in the open-source tier. Whether that’s a strategic decision or a resource allocation issue at IBM, the effect is the same: OpenTofu is now offering capabilities that Terraform’s free version simply doesn’t have.
The Numbers Tell a Story
Growth metrics matter because they signal where the community is placing its bets. OpenTofu’s GitHub repository crossed 23,000 stars by early 2026, with over 4 million weekly downloads according to their public transparency dashboard. Compare that to the roughly 1.5 million downloads the project saw at launch. The growth rate is steep, but more importantly, it shows sustained momentum rather than the typical fork decline curve where everyone eventually drifts back to the original project.
The migration data is even more telling. A January 2026 survey by Pulumi of 1,200 platform engineers found that 31% had already moved at least one production environment from Terraform to OpenTofu. That’s up from 11% the year prior. These aren’t academic discussions anymore. Real teams are running real infrastructure on OpenTofu and reporting it back as a viable path forward. Nearly a third of platform engineers surveyed have actual migration experience, which means the tooling has cleared the “proof of concept” threshold.
OpenTofu’s acceptance as a sandbox project by the CNCF’s Technical Oversight Committee in early 2025 matters for governance legitimacy. The same body that shepherded Kubernetes and Prometheus through their early stages is now formally standing behind OpenTofu’s development pathway. That’s not marketing. That’s institutional credibility.
IBM’s Acquisition and the Question of Velocity
HashiCorp’s acquisition by IBM closed in April 2024 for $6.4 billion. IBM is a responsible steward of open-source projects, and Terraform continues receiving investment and support. But IBM is also an enterprise software company with different commercial incentives than a startup. The concern floating through infrastructure circles is whether future Terraform innovation will move at startup velocity or enterprise velocity. When your parent company makes money from premium support contracts and hosted services, there’s less urgency to keep pushing the open-source version forward aggressively.
This isn’t an accusation. It’s how incentives work at scale. OpenTofu, by contrast, has no commercial service layer to defend. The Linux Foundation-backed model means innovation benefits flow directly to the open-source project without the drag of protecting adjacent commercial products. If you’re placing long-term bets on your infrastructure tooling, that structural difference matters.
Making the Choice Your Organization Needs
The fork is real. Both projects are well-maintained, both have substantial community support, and both can run your infrastructure reliably. Terraform still has advantages: more third-party provider support in some niches, deeper documentation in places, and existing integrations with enterprise tooling that took years to build. OpenTofu has momentum, native encryption, and the governance assurance of Linux Foundation backing.
The honest answer for most teams is that you don’t need to pick a winner. You can run Terraform for critical production infrastructure and experiment with OpenTofu on new projects. You can adopt OpenTofu’s state encryption approach while keeping your existing Terraform workflows intact. The tooling is compatible enough that migration, while not trivial, is manageable for teams that want it. Check the OpenTofu official documentation and changelog for specific migration guidance, and review the Linux Foundation OpenTofu project page for the formal governance structure.
What matters most is that you’re making an active choice instead of a passive assumption. The fork has become real competition, and competition in infrastructure tooling is good for everyone. It forces both projects to defend their ground through better features, faster response times, and genuine attention to what teams actually need. Your job is to understand what your infrastructure team values most and build your strategy accordingly. Having that choice, hard as it sometimes feels, beats the alternative.
