Tuesday, November 17, 2026 · Week 47 DE · EN · FR · ES Dark
Guides

OpenTofu vs Terraform: choosing the right IaC tool

OpenTofu or Terraform: licensing, state protection and integrations determine how much work a switch requires for infrastructure teams.

By Alec Chizhik June 5, 2026 3 min read
OpenTofu vs Terraform: choosing the right IaC tool

OpenTofu and Terraform automate infrastructure using related configurations, though they differ in licensing and project governance. HashiCorp moved future releases to the Business Source License in 2023 and has been part of IBM since February 2025. OpenTofu emerged as an open-source fork. For infrastructure teams, the right choice depends on the specific use case, licensing terms, state protection and existing integrations.

Key takeaways

  • The licensing terms differ. OpenTofu is licensed under the MPL 2.0, while HashiCorp uses the Business Source License for newer Terraform releases.
  • OpenTofu can encrypt state and plan files itself. Teams must also plan for key management and recovery.
  • A switch requires testing the specific environment. Versions, providers, backends and platform integrations determine the effort involved.

Licensing and project governance differ

In August 2023, HashiCorp announced that it would move future product releases from the Mozilla Public License 2.0 to the Business Source License 1.1. According to HashiCorp’s licence announcement, many commercial and non-commercial uses remain permitted. Restrictions apply in particular to offerings that compete with HashiCorp products. Platform and managed service providers should assess their specific use against the applicable licensing terms.

OpenTofu emerged as a fork of the Terraform codebase previously released under the MPL 2.0 and operates under the Linux Foundation. HashiCorp is responsible for the Terraform product. IBM completed its acquisition of the company on 27 February 2025.

State protection requires a key management plan

State files record the managed state of infrastructure and can contain sensitive values. OpenTofu offers configurable encryption of state and plan files, both locally and when using a backend. Keys can be supplied through a key management system, among other options.

Encryption does not replace access controls or backups. If the required key is lost, the encrypted state can no longer be read. Teams must also plan the conversion of any existing unencrypted state. For Terraform environments, teams should check which protections the chosen backend and operating platform provide.

Migration starts with a limited test

OpenTofu aims to be compatible with Terraform configurations. In its migration guide, the project recommends first backing up code and state, then initialising OpenTofu and checking the configuration. A small test clarifies how it behaves in the team’s own environment.

Before a larger migration, teams should document the Terraform versions, providers and modules in use. They should also account for backends, automated pipelines and dependencies between multiple states. A plan before and after the switch shows whether unexpected infrastructure changes are proposed. Only after this check should teams move on to the next state.

Weighing governance and platform ties

Alongside licensing, the decision depends on who maintains updates, how security vulnerabilities are handled and which integrations operations require. Teams using a platform such as HCP Terraform should assess its features and interfaces separately before migrating. The plan should also cover a way back, including readable state backups.

For regulated companies, supply chain and third-party risks may form part of this assessment. Neither an open-source licence nor membership of a large vendor group on its own demonstrates compliance with regulatory requirements. The applicable rules and the controls actually in place in each operating environment are what matter.

Frequently Asked Questions

Can OpenTofu replace Terraform?

Many configurations can be carried over. Whether that applies to a specific environment depends on versions, providers, backends and platform features, among other factors. A backed-up state and a limited test are the starting point.

How do the licences differ?

OpenTofu uses the MPL 2.0. Newer Terraform releases are licensed under the Business Source License 1.1, whose terms restrict certain competing offerings. The specific use case determines how those terms apply.

What does OpenTofu’s state encryption protect?

It protects configured state and plan files from being read without the appropriate key. It does not prevent data loss or replace access controls or a procedure for recovering files and keys.

Image source: AI-generated (June 2026)

Translated from the German original using artificial intelligence. The German version is authoritative.

Also available in

FrançaisEspañolDeutsch
MBF Media Newsletter

The monthly briefing for decision-makers

Once a month, the MBF Media Newsletter gathers what matters from cloudmagazin, MyBusinessFuture, Digital Chiefs and SecurityToday, curated by the editorial team.

Around 23,500 IT and business decision-makers read this newsletter. Read along.

Subscribe for free
MBF Media Newsletter, aktuelle Ausgabe auf dem iPhone
A magazine by Evernine Media GmbH