Happy new year. While most of the tech world was recovering from the holidays, the OpenTofu project has been quietly building momentum toward its first stable release. For those who missed the drama: last August, HashiCorp switched Terraform from the Mozilla Public License (MPL 2.0) to the Business Source License (BSL 1.1), effectively making it non-open-source. The community’s response was swift and decisive — OpenTofu, a truly open-source fork of Terraform, is now under the Linux Foundation’s stewardship and approaching general availability.
How We Got Here#
HashiCorp’s license change in August 2023 sent shockwaves through the infrastructure-as-code community. Terraform had been the de facto standard for cloud provisioning for nearly a decade, and much of its dominance was built on the trust that comes with genuine open-source licensing. The BSL 1.1 license restricts competitive use — meaning companies that offer products competing with HashiCorp’s commercial offerings can no longer freely use the Terraform codebase.
The response was remarkably organized. Within days, a manifesto appeared with signatures from major Terraform ecosystem players including Gruntwork, Spacelift, Env0, and Scalr. By September, the fork was official and had been accepted into the Linux Foundation. The speed of this mobilization tells you something about how deeply the community values genuine open-source licensing for infrastructure tooling.
I’ve been through enough open-source licensing disputes to know that forks often start with energy and fizzle out. But OpenTofu has several things working in its favor: corporate backing from companies whose businesses depend on an open Terraform ecosystem, Linux Foundation governance providing neutrality, and a codebase that was already well-understood by hundreds of contributors.
What OpenTofu Brings#
At its core, OpenTofu is a drop-in replacement for Terraform. The initial releases have focused on maintaining compatibility — if you have existing Terraform configurations, the migration path is designed to be as simple as changing the binary you run. Same HCL syntax, same provider ecosystem, same state file format.
But the project isn’t just about maintaining the status quo. The roadmap includes features the community has long requested, with state encryption being one of the most anticipated. Terraform state files can contain sensitive information — database passwords, API keys, private IPs — and they’ve historically been stored unencrypted. State encryption in OpenTofu would address a security gap that the community has been asking HashiCorp to fix for years.
The provider registry is another area where OpenTofu is establishing independence. While maintaining compatibility with existing Terraform providers, the project is building its own registry infrastructure to ensure it isn’t dependent on HashiCorp’s services. This is crucial for long-term viability — you can’t claim independence if your tool still phones home to the company you forked from.
The Broader License Debate#
The HashiCorp situation isn’t isolated. We’ve seen similar license changes from MongoDB (SSPL), Elastic (SSPL, then a partial reversal), Redis (Commons Clause, then RSAL), and Confluent (Community License). The pattern is clear: companies that built businesses on open-source software are feeling pressure from cloud providers offering their tools as managed services, and they’re responding by restricting their licenses.
I understand the business pressure. Building and maintaining complex infrastructure software is expensive, and watching AWS or Azure offer a managed version of your product without contributing proportionally back is genuinely frustrating. But the solution of changing licenses after building a community on open-source trust feels like a betrayal, and the market is responding accordingly.
The interesting question is whether OpenTofu can maintain momentum long-term. Forks succeed when they attract a sustainable contributor community and when the ecosystem (in this case, providers and modules) supports them. The early signs are positive — major Terraform providers are compatible, and the companies backing OpenTofu have direct business incentives to keep contributing.
Practical Implications#
If you’re running Terraform in production today, here’s my practical take:
Don’t panic. The BSL license doesn’t affect most users. If you’re using Terraform to manage your own infrastructure, nothing changes for you legally. The restrictions apply to companies building competitive products.
Start evaluating OpenTofu. Even if the license change doesn’t affect you directly, there’s value in having a fully open-source option. Set up a parallel pipeline with OpenTofu and verify your configurations work. The migration cost today is minimal.
Watch the provider ecosystem. The critical dependency for any Terraform-like tool is provider support. Monitor how providers handle dual compatibility. Most major providers (AWS, Azure, GCP, Kubernetes) use the Terraform Plugin SDK, which OpenTofu supports.
Consider your CI/CD pipeline. If you’re using Terraform Cloud or Terraform Enterprise, the switch to OpenTofu would also mean changing your orchestration layer. Tools like Spacelift, Env0, and Atlantis already support or are adding OpenTofu support.
My Take#
I’ve been using Terraform since version 0.6, and I’ve watched it grow from a promising tool into the backbone of infrastructure automation at thousands of organizations. The license change genuinely disappointed me — not because I don’t understand HashiCorp’s business pressures, but because it undermined the trust relationship between the project and its community.
OpenTofu represents something important beyond just a Terraform alternative. It’s a test case for whether the open-source community can effectively fork and sustain a complex infrastructure tool when the original maintainer changes direction. If OpenTofu succeeds, it sends a clear signal to other companies considering similar license changes: the community will route around restrictions, and you might end up competing with a well-funded fork of your own software.
As we start 2024, I’m cautiously optimistic about OpenTofu’s trajectory. The governance model is sound, the backing is substantial, and the technical foundation is solid. Whether it can attract enough independent contributors to innovate beyond what Terraform offers — that’s the question that will determine if this is a footnote or a turning point for infrastructure as code.