OpenTofu: Modernizing Infra with the New Standard

22 March 2026

4 min Reading Time

IBM acquired HashiCorp for $6.4 billion. Terraform now operates under the Business Source License (BSL). And OpenTofu – the open-source fork – has seen 300% annual growth, reaching 9.8 million downloads to date. For cloud architects and DevOps teams at DACH-region enterprises, the question is no longer whether to reassess their Infrastructure-as-Code (IaC) strategy – but when. This hands-on analysis reveals what the acquisition actually changes, what a migration looks like, and when it makes sense.

TL;DR

IBM completed its acquisition of HashiCorp for $6.4 billion on February 27, 2025 (The Register).
38 percent of Terraform users are already evaluating or migrating to OpenTofu (Spacelift Survey, Q4 2024).
OpenTofu: 9.8 million downloads, 300 percent annual growth, and a CNCF member since April 2025.
Fidelity migrated over 50,000 state files containing more than 4 million resources from Terraform to OpenTofu.
The BSL does not restrict internal use – but does apply to managed services, reselling, and embedding Terraform functionality.

What the IBM Acquisition Means for Terraform Users

On February 27, 2025, IBM finalized its acquisition of HashiCorp for $6.4 billion. Terraform, Vault, Consul, and Nomad are now part of an enterprise conglomerate historically known for long-term contracts and platform lock-in.

In the short term, little changes for purely internal usage. Terraform remains fully functional, and the Community Edition stays available. But the Business Source License (BSL) – introduced by HashiCorp in August 2023 – fundamentally altered the rules: anyone embedding Terraform functionality into their own products, offering it as a managed service, or reselling it must obtain a commercial license. Under IBM’s leadership, this stance is more likely to harden than soften.

The consequence for IT leaders? If you’re using Terraform today, you need to understand your licensing exposure. Which teams use Terraform – and how? Do you operate internal platforms that deliver Terraform runs as a service? Are Terraform modules distributed to customers? Each of these scenarios could trigger BSL obligations.

38 %

of Terraform users are already evaluating or migrating to OpenTofu

Source: Spacelift Survey, Q4 2024

OpenTofu: From Fork to Serious Competitor

OpenTofu launched in September 2023 as a direct response to HashiCorp’s BSL license change. What began as a community protest has matured into a robust, production-ready project. The numbers tell the story: 9.8 million downloads, 300 percent annual growth, and official CNCF (Cloud Native Computing Foundation) sandbox-level membership since April 2025.

Its technical foundation is identical: OpenTofu uses the same HCL syntax (HashiCorp Configuration Language), the same state file structure, and maintains compatibility with most Terraform providers. In many cases, a switch at the code level amounts to a simple find-and-replace of “terraform” with “tofu” in CI/CD pipelines.

But OpenTofu goes beyond being a mere fork. Native features – including client-side state encryption (securing state files without external tools), a provider-agnostic registry, and an improved module structure – are increasingly distinguishing it from its origin.

Who Has Already Migrated – and Why

The list of early adopters reads like a who’s who of highly regulated industries. Fidelity Investments migrated over 50,000 state files across more than 2,000 applications and 4 million managed resources. Their motivation? Regulatory concerns around the BSL and overreliance on a single vendor for mission-critical infrastructure.

At Spacelift – one of the largest IaC management platforms – 50 percent of all deployments now run on OpenTofu instead of Terraform. The trend is clear: organizations with stringent compliance requirements – and those delivering IaC-based platform services – lead the migration.

For DACH-region enterprises, the sovereignty angle is especially relevant. An open-source tool licensed under MPL 2.0 offers greater control than a BSL-licensed product owned by a U.S. corporation. In regulated sectors like financial services and healthcare, that distinction can be decisive.

OpenTofu’s commitment to open-source principles reflects our shared vision of delivering accessible, reliable tools that empower the broader tech community. Chris Aniszczyk, CTO, Cloud Native Computing Foundation (CNCF)

Migration: What It Really Costs

The good news: migrating from Terraform to OpenTofu is technically straightforward. State files are compatible. HCL syntax is identical. Most providers work on both platforms.

The challenges lie in the details:

Provider Registry: OpenTofu uses its own registry, which doesn’t host every Terraform provider. Before migrating: cross-check your provider list against the OpenTofu registry. Missing providers must be manually configured – or referenced directly from the HashiCorp registry.

CI/CD Pipelines: Terraform Cloud and Terraform Enterprise are incompatible with OpenTofu. Users relying on them will need alternatives: Spacelift, env0, Scalr, or a custom-built platform. This is often the most time-consuming part of the migration.

Team Training: Minimal. Syntax is identical; tooling differs only in subtle ways. Most teams require just half a day of onboarding.

Total Effort: For a team managing 20-50 state files: 2-4 weeks. For enterprise-scale setups like Fidelity’s (50,000+ state files): 3-6 months – with a dedicated migration team.

Terraform, OpenTofu or Pulumi? Decision Matrix

Your choice hinges on three factors: licensing risk, ecosystem needs, and team expertise.

Terraform still makes sense if: Your internal usage falls squarely within BSL allowances, your team is deeply embedded in the HashiCorp ecosystem (Vault, Consul), and you rely on Terraform Cloud or Enterprise. IBM won’t let Terraform fade – it’s too valuable.

OpenTofu is the right choice if: You offer IaC-based managed services, face regulatory demands for open-source transparency, worry about BSL clauses, or aim to minimize vendor lock-in by design.

Pulumi deserves consideration if: Your team prefers writing infrastructure in TypeScript, Python, or Go rather than HCL; you favor Infrastructure-as-Software over Infrastructure-as-Code; or you’re starting from scratch. Migrating from Terraform or OpenTofu to Pulumi is labor-intensive, requiring full rewrites of infrastructure definitions. Best suited for greenfield projects.

Fidelity Investments Migration

50,000+

State files migrated from Terraform to OpenTofu

Source: IDE.com / Fidelity, 2025

What IT Leaders Should Do Now

1. Conduct a license audit. How do your teams use Terraform? Internally? As a platform service? In customer projects? Understand the BSL boundaries precisely.

2. Build a state inventory. How many state files? How many resources? Which providers? This forms the baseline for effort estimation.

3. Test OpenTofu in a sandbox. Migrate a non-critical workload and let your team use it for two weeks. Verify compatibility firsthand.

4. Evaluate CI/CD alternatives. If you use Terraform Cloud: test Spacelift, env0, or Scalr. This is often the real bottleneck.

5. Document your decision. Whether you stay with Terraform or migrate – your rationale must be clear, defensible, and auditable. Regulators will ask.

Conclusion

IBM’s acquisition of HashiCorp has fractured the IaC landscape. OpenTofu is no longer a protest fork – it’s a credible alternative backed by the CNCF, validated by enterprise references, and growing its ecosystem rapidly. For DACH-region enterprises facing regulatory scrutiny or significant BSL exposure, evaluation is overdue. Technically, migration is manageable; the heaviest lift lies in retooling CI/CD pipelines. Teams that map their licensing exposure today – and test OpenTofu in a sandbox – are prepared for whatever direction IBM steers Terraform.

Frequently Asked Questions

Is OpenTofu truly compatible with Terraform?

Yes – at the state file and HCL syntax level. Most Terraform providers work unchanged. Incompatibilities arise only with Terraform Cloud/Enterprise-specific features and some newer provider versions available exclusively in the HashiCorp registry.

Do I need to worry about the BSL for internal Terraform use?

No – purely internal usage is unaffected. Risk arises when you offer Terraform functionality as a service, embed it into your own products, or resell it to customers. Boundaries aren’t always clear-cut, so a license audit is worthwhile.

How long does a migration to OpenTofu take?

For small teams managing 20-50 state files: 2-4 weeks. For enterprise-scale deployments: 3-6 months. The biggest effort isn’t rewriting code (often just find-and-replace), but adapting CI/CD pipelines and reconciling provider registries.

What happens to Vault and Consul under IBM?

Both Vault and Consul also fall under the BSL. IBM will continue developing them – but pricing is expected to shift toward enterprise licensing models. An open-source fork of Vault, OpenBao, exists; the situation for Consul is less definitive.

Is Pulumi a viable alternative to both?

Pulumi uses general-purpose programming languages instead of HCL. That’s a strength for developer-heavy teams – but a hurdle for operations teams without coding experience. Migrating from Terraform or OpenTofu to Pulumi is intensive, requiring full rewrites of infrastructure definitions. Best suited for greenfield projects.

OpenTofu vs. Terraform: IBM Acq. Impact on Your Infrastructure