The Fork That Became a Movement
When HashiCorp flipped the license switch on Terraform in August 2023, moving to the Business Source License, most of us figured we’d see a brief protest, maybe some grumbling in Slack channels, and then everyone would quietly move on. We were wrong. The Linux Foundation backed a proper fork called OpenTofu, and roughly eighteen months later, we’re staring at something that actually matters: real competition in the infrastructure-as-code space.
I’ve been in this industry long enough to know that open-source forking usually ends one of two ways. Either the fork dies quietly because maintaining a parallel codebase is brutal, or it succeeds because the original genuinely lost the plot. OpenTofu is looking increasingly like the latter scenario. With over 23,000 GitHub stars and north of 4 million weekly downloads as of January 2026, the project has moved well past the “protest fork” phase into something with actual momentum and serious institutional backing.
OpenTofu 1.9 Changes the Game: Native State Encryption
The real inflection point arrived with OpenTofu 1.9 in late 2025. The headline feature is end-to-end state encryption baked directly into the open-source tier. If you’ve ever managed Terraform state files and lost sleep over the fact that your secrets were sitting in S3 or a remote backend with encryption that might or might not be properly configured, this addresses that anxiety directly. You’re not buying an enterprise tier. You’re not bolting on third-party tooling. The encryption is native, and it just works.
Terraform 1.10, by comparison, landed with what can only be described as a shrug. The releases have been incremental, measured, the kind of thing you deploy on a Tuesday afternoon without canceling your standup. This matters less because Terraform suddenly got bad and more because OpenTofu is demonstrably moving faster on features that practitioners actually care about. That’s a shift. Check the OpenTofu official documentation and changelog if you want to see the specifics, but the velocity is real.
IBM’s Acquisition Changed the Calculus
Let’s be direct: HashiCorp’s $6.4 billion sale to IBM in April 2024 reframed the entire conversation. IBM doesn’t acquire companies to keep them scrappy. They acquire them to integrate them into enterprise stacks and extract value. That’s not a moral judgment. It’s just how public companies work. But it means the open-source Terraform project is no longer the strategic center of gravity. The strategic center is now wherever IBM sees the most margin, which is decidedly not the free tier.
The infrastructure community noticed. A January 2026 survey of 1,200 platform engineers from Pulumi found that 31 percent had already migrated at least one environment from Terraform to OpenTofu. That’s up from 11 percent just a year earlier. Those aren’t theoretical numbers. Those are teams making active decisions to jump ship, which means friction, testing, risk management, and real work. People don’t do that casually. They do it when they’ve concluded the alternative is better.
Institutional Legitimacy and Long-Term Viability
The Linux Foundation formally accepted OpenTofu as a sandbox project under the CNCF in early 2025. This is the same governance pathway that Kubernetes, Prometheus, and other projects have used to build enterprise trust. It matters because legitimacy in infrastructure is not optional. Companies need to know they’re not betting on a side project that will vanish when founders get bored or funding dries up. The Linux Foundation backing says: this is here to stay, governed by transparent rules that everyone can audit.
That matters more than you might think. Enterprise procurement teams, security reviews, vendor evaluation committees, these are all places where “backed by the Linux Foundation” carries real weight. OpenTofu just moved from “interesting fork” to “credible long-term platform” on that single decision. It’s the infrastructure equivalent of getting your Series A from a tier-one VC. The fact of it changes the trajectory.
What This Means for Your Team Right Now
So what do you actually do with this information? If you’re running a small operation and Terraform works fine, you don’t need to panic. The ecosystem isn’t collapsing tomorrow. But if you’re building new infrastructure projects, evaluating tooling, or running large teams that depend on open-source stability, you need to be thinking seriously about OpenTofu. The fork has moved from “protest vote” to “legitimate alternative,” and pretending otherwise is just willful blindness.
The migration story is real but not trivial. The projects are largely compatible, but state file formats have diverged, and you’ll need to plan transitions carefully. Smaller teams might have that conversation and decide to stick with what works. Larger teams with multiple environments, particularly those that care deeply about security practices and feature velocity, are increasingly concluding that the jump is worth the effort.
What we’re actually watching is the open-source IaC market fracturing in a way that creates genuine choice. That’s not bad. That’s what’s supposed to happen when a vendor tries to monetize something the community values as a public good. The fork succeeds, the community gets agency back, and the market sorts itself out. I’m genuinely curious which way your team will go. What’s the decision tree looking like in your shops right now? The Linux Foundation OpenTofu project page is the right place to start if you’re kicking the tires seriously.
