The Fork That Nobody Expected to Survive
I remember August 2023 like it was yesterday. HashiCorp announced they were moving Terraform to the Business Source License, and suddenly every infrastructure engineering team I knew was in a group chat asking variations of the same question: “Wait, we have to pay now?” The BSL announcement wasn’t technically a betrayal—licenses change, companies pivot, that’s business—but it felt like watching a friend you trusted make a decision that left you standing in the parking lot wondering if you’d been reading the same relationship.
Enter OpenTofu. The Linux Foundation got involved. A fork happened. And here we are in early 2026, staring at a scenario I genuinely did not expect to write about: OpenTofu isn’t the scrappy underdog project anymore. It’s become a credible, feature-leading alternative with development velocity that’s actually outpacing HashiCorp’s Terraform in several metrics. The decision matrix has shifted. The fork has matured. If you’re still on pure Terraform without even glancing at what’s happening across the fence, you might be leaving real capability on the table.
Where the Technical Lead Gets Interesting
Let me ground this in specifics, because general statements about forks are boring and usually wrong. OpenTofu shipped version 1.9 in late 2025 with provider-defined functions and native state encryption. Terraform’s current releases don’t have either of those features. Full stop. That’s not marketing spin—that’s a capability gap you can actually use right now.
The provider ecosystem has also reached critical mass. OpenTofu’s registry had crossed 2,000 mirrored providers by the beginning of this year. The GitHub repository sits north of 23,000 stars. More tellingly, contributor velocity metrics show OpenTofu committing code at a higher frequency than Terraform for several consecutive months through late 2025. This matters because it signals momentum, but also because bugs get fixed faster and features ship faster. When you’re managing infrastructure at scale, that velocity difference compounds.
What really tipped the scales for me personally was talking to three separate enterprises in the last six months who’d actually completed full migrations from Terraform to OpenTofu. Not pilots. Not test environments. Complete migrations. A Spacelift survey from 2025 found that 34% of infrastructure teams evaluating OpenTofu had finished full migrations, with another 28% partway through. That’s not marginal adoption. That’s material market movement.
The IBM Factor Nobody’s Talking About Enough
HashiCorp sold to IBM for 6.4 billion dollars in mid-2024. On the surface, that’s just a headline. Dig deeper and it’s a narrative inflection point. IBM’s product roadmap communications in the months since acquisition have been careful, measured, and conspicuously light on explicit commitments to maintaining Terraform’s open-source independence. When your major vendor gets acquired by a company known for monetizing enterprise software differently than startups do, infrastructure teams notice.
This is where licensing uncertainty enters the conversation. Pulumi released their State of Cloud Infrastructure report in 2025, and 41% of platform engineers cited IaC tool licensing uncertainty as a top-three risk factor for their 2025-2026 toolchain planning. That’s nearly half the market explicitly worried about stepping on a licensing landmine. OpenTofu, governed by the Linux Foundation and backed by the open-source community, doesn’t carry that risk profile. It can’t. That’s the entire reason it exists.
The Honest Trade-offs You Actually Need to Know
I’m not here to tell you OpenTofu is objectively better. That would be stupid and wrong. Terraform still has deeper market penetration, which means more third-party tooling integration, more blog posts when you’re stuck at 2 AM, and more people on call who already know how to operate it. Enterprise support, if you want to pay for it, is clearer with Terraform. Module ecosystem depth still favors Terraform, though that gap is narrowing monthly.
OpenTofu’s documentation is solid but not enterprise-brochure-level polished. The OpenTofu official documentation and changelog are genuinely comprehensive and well-maintained, but they read like documentation written by engineers for engineers. Terraform’s docs feel slightly more curated toward beginner audiences. If your team spans from infrastructure specialists to developers who touch Terraform once a quarter, that difference matters.
Ecosystem tooling like Terragrunt, Atlantis, and cloud-specific integrations are more mature on Terraform’s side simply because Terraform has had more years and more enterprise deployments. But none of these differences are permanent moats. In a fast-moving ecosystem, six months changes things. In a year, it changes everything.
What the Ground Truth Says
I’ve been in enough architectural decisions to know that the honest answer in early 2026 is this: if you’re greenfield, if you’re starting fresh, the calculus between Terraform and OpenTofu is not lopsided anymore. It genuinely depends on whether your risk tolerance leans toward “vendor stability” or “license stability.” Both are legitimate concerns. They’re just different concerns now.
If you’re on existing Terraform, you don’t need to panic-migrate. Your code works. Your team knows the tool. Moving for the sake of moving is cargo-cult engineering. But running a limited pilot migration with a new workload or a team that’s building fresh infrastructure? That’s legitimate experimentation. The fork has matured to the point where that experiment actually yields useful data instead of just producing frustration.
The maturation of OpenTofu means your answer to “Terraform or OpenTofu?” in 2026 is no longer “obviously Terraform.” It’s “what are your constraints and what does your risk matrix look like?” That’s more work to think through than a simple answer, sure. But it’s also more honest. The fact that we’re even having this conversation is proof that the fork succeeded in doing what it set out to do: create a real alternative.
If you’ve got experiences from the trenches with either tool, or if you’ve been through a migration yourself, I’d genuinely like to hear what you’ve learned. The landscape is shifting fast enough that data from real deployments matters more than analyst reports right now.