OpenTofu 1.9 vs. Terraform 1.10: The Fork Is Now Real Competition, and Infrastructure Teams Are Being Forced to Choose

The Fork That Became Inevitable

When HashiCorp switched Terraform to a Business Source License in August 2023, the infrastructure community didn’t just grumble into Slack channels. They forked it. The Linux Foundation picked up the torch, created OpenTofu, and basically said: “Fine, we’ll maintain this ourselves.” I’ve watched enough corporate licensing decisions tank community goodwill to recognize the moment when an open-source project becomes untethered from its corporate steward. This was that moment.

For the first year, OpenTofu existed in a kind of liminal space. It was alive, it was growing, but it felt like a backup plan rather than a credible alternative. Most teams kept their Terraform deployments running on the assumption that HashiCorp would eventually course-correct, or that the fork would remain perpetually behind the curve. We were wrong on both counts. By late 2025, OpenTofu 1.9 shipped with end-to-end state encryption as a native feature, something that still doesn’t exist in Terraform’s open-source tier. That’s not a marginal improvement. That’s a security feature that enterprise teams have been paying extra money to get through third-party tooling or expensive Terraform Cloud licenses.

The Numbers Tell a Story That Can’t Be Ignored

GitHub stars and download counts aren’t everything, but they’re not meaningless either. OpenTofu’s repository crossed 23,000 stars by January 2026, with the project reporting over 4 million weekly downloads. For context, the fork started at roughly 1.5 million downloads per week. That’s not growth, that’s momentum. The community isn’t just kicking the tires anymore.

The real signal comes from migration data. A January 2026 survey of 1,200 platform engineers found that 31% had already migrated at least one environment from Terraform to OpenTofu, up from 11% the year before. Nearly a third of the people actively managing infrastructure as code pipelines have made the leap. These aren’t theoretical discussions or blog post debates. Teams are updating their CI/CD pipelines, retraining engineers, and reorganizing their state management around this fork. That’s expensive and deliberate.

What’s particularly telling is the trajectory. Migration velocity is accelerating, not plateauing. When you see adoption curves shaped like that, it usually means the alternative wasn’t just marginally better. It was solving a genuine problem that the incumbent had stopped caring about.

IBM’s Acquisition Changed the Game (Again)

HashiCorp’s acquisition by IBM closed in April 2024 for $6.4 billion. I’ll be direct: large tech acquisitions rarely accelerate open-source innovation on the acquired product. They tend to do the opposite. The incentive structure shifts toward maximizing value extraction through premium tiers, compliance bundles, and enterprise integrations. Meanwhile, the open-source community watches and waits to see which way the wind blows.

Terraform 1.10 and subsequent releases have been substantially incremental. Performance improvements, bug fixes, minor quality-of-life enhancements. These are fine. They’re also not the kind of feature releases that make you lean forward in your chair. Meanwhile, OpenTofu has begun diverging on security features and governance model. The Linux Foundation OpenTofu project page shows that the CNCF’s Technical Oversight Committee formally accepted OpenTofu as a sandbox project in early 2025, which means it gets the same governance legitimacy pathway that Kubernetes and Prometheus used to earn enterprise trust. That’s not ceremonial. That’s a statement that this fork is here to stay and has passed institutional rigor tests.

The concern circulating through infrastructure teams isn’t paranoia. It’s pattern recognition. When IBM prioritizes Terraform as part of its broader cloud and automation strategy, the open-source tier becomes a feeder funnel rather than the primary focus. You want encryption? Use Terraform Cloud. You want advanced state management? Enterprise tier. The economics are understandable from IBM’s perspective. They’re baffling from an open-source maintainer’s perspective.

What This Actually Means for Your Team

Here’s what I think matters most: you now have a legitimate alternative with institutional backing and real competitive momentum. OpenTofu isn’t a scrappy underdog fork anymore. It’s a project with 23,000 GitHub stars, a CNCF sandbox commitment, and monthly downloads climbing toward Terraform’s levels. The OpenTofu official documentation and changelog shows a project that’s been engineering thoughtfully, not just copying code.

The practical choice for most teams won’t be binary. Some environments will stay on Terraform. Others will migrate to OpenTofu. State files can be translated. Workflows can be rewritten. The friction is real but manageable for teams that want to move. What’s changed is that the choice itself is now available without betting your infrastructure on a community fork that might evaporate.

The migration question stops being “Should we stay on the established standard?” and becomes “Which standard better aligns with our security requirements, governance model, and willingness to rely on Linux Foundation stewardship versus IBM’s enterprise cloud strategy?” For many teams, especially those that got burned by previous licensing changes or those with strict open-source requirements, that’s an easy calculation.

The Fork Won, Even If Nobody Admits It Yet

Sometimes the most important moment in open-source isn’t when a fork succeeds. It’s when the incumbent has to acknowledge that it exists as a genuine competitor rather than a temporary disruption. We’re at that moment now. HashiCorp’s own customers are publicly discussing migration strategies. Infrastructure teams are updating their deployment pipelines to account for two competing standards. The CNCF has formalized OpenTofu’s governance. Taken together, these aren’t just signals that the fork is viable. They suggest it’s reshaping how people think about infrastructure tooling choices.

I’ve seen enough technology shifts to know that they rarely feel significant when they’re happening. They feel like Friday afternoon technical discussions and Jira tickets getting reprioritized. Teams quietly migrate one environment at a time. Download counts inch upward. A governance body grants formal recognition. And then you look up and realize the thing that looked like a corporate backflip became the catalyst for genuine choice in infrastructure tooling.

If you’ve been postponing any serious look at OpenTofu, now is the time to actually read the changelog, run a test deployment, and figure out whether the native encryption features and governance model matter for your use cases. The fork isn’t a hedge anymore. It’s a legitimate platform decision. What would you prioritize if you had to choose right now?