OpenTofu in 2026: Evaluating the Switch from Terraform Amidst IBM Acquisition and License Changes

The year 2026 marks a pivotal moment for organizations managing infrastructure with Terraform, as the long-standing question of whether to transition to OpenTofu has gained a much clearer answer. The primary drivers behind this re-evaluation are two significant shifts: the ownership of Terraform and its licensing model. In early 2025, IBM finalized its acquisition of HashiCorp in a multi-billion dollar deal, effectively making Terraform an IBM product. This change in ownership, while potentially offering stability, also places Terraform under the purview of a single corporate entity. Concurrent with the acquisition, HashiCorp had already moved Terraform's licensing from the permissive Mozilla Public License (MPL) 2.0 to the more restrictive Business Source License (BSL) 1.1 in August 2023. The BSL 1.1 is a source-available license, not truly open source, as it imposes limitations on using Terraform to develop competing products. While this license change might not immediately impact most teams using Terraform internally, it carries significant implications for those building tooling around Terraform or prioritizing vendor-neutral governance. Each BSL release only reverts to MPL four years after its initial shipment, creating a delayed open-source availability. In contrast, OpenTofu, born from the fork of Terraform, operates under the MPL 2.0 license and is governed by the Cloud Native Computing Foundation (CNCF). This ensures a vendor-neutral stewardship, preventing any single company from controlling its direction. The project has matured considerably since its inception, moving beyond a mere 'protest vote' to become a robust, working tool with its own distinct roadmap and feature set. OpenTofu v1.12, released in May 2026, has notably shipped several features that are currently absent from Terraform's open-source command-line interface. These include native state encryption, which enhances security by encrypting sensitive state data, and the `-exclude` flag, offering more granular control over resource operations. Furthermore, OpenTofu now supports `provider for_each`, allowing for more dynamic and flexible provider configurations, and early variable evaluation, which can streamline complex deployments. These additions provide tangible benefits and capabilities that Terraform's open-source users do not have access to. The migration path from Terraform to OpenTofu is surprisingly straightforward for many teams. The underlying state format remains identical, simplifying the transition. The process typically involves swapping the `terraform` binary for `tofu`, running `tofu init`, and validating changes with `tofu plan`. This initial migration is largely reversible, allowing organizations to experiment without immediate commitment. However, the true 'lock-in' begins when teams start leveraging OpenTofu-only features, such as native state encryption. Once these specialized functionalities are adopted, reverting to Terraform without significant re-engineering becomes considerably more complex. For organizations grappling with this decision in 2026, the picture is clearer than ever. The choice hinges not on syntax differences, but on fundamental considerations of ownership, licensing, and desired feature sets. Teams prioritizing open governance, vendor neutrality, and access to the latest community-driven features might find OpenTofu to be the more compelling option. Conversely, those deeply integrated into the HashiCorp ecosystem under IBM's stewardship, and for whom the BSL restrictions are not a concern, might opt to remain with Terraform. A pragmatic approach for larger organizations might involve a dual-engine strategy, running both tools, while smaller teams might consider a 'big bang' switch if the benefits of OpenTofu's new features outweigh the migration effort. The key takeaway is that the 'wait and see' period is over; the fork has established itself as a viable and feature-rich alternative.