Summary
OpenTofu is an open-source infrastructure-as-code (IaC) tool for defining, provisioning, and managing cloud and on-premises infrastructure in declarative configuration files. It originated as a community fork of Terraform after Terraform moved to the Business Source License, and is now governed by the Linux Foundation under the MPL 2.0 license.
What is OpenTofu?
Like Terraform, OpenTofu lets teams describe their desired infrastructure—servers, networks, databases, DNS records, and more—in HCL configuration, then plans and applies the changes needed to reach that state. It tracks managed resources in a state file and works across many providers through a shared provider ecosystem.
Because OpenTofu forked from Terraform, existing configurations and the provider model remain largely compatible, which makes migration straightforward for many teams. As an independent, community-governed project it has continued to add its own capabilities. For organisations pursuing an open-source-first strategy or seeking to reduce dependence on a single vendor's licensing decisions, OpenTofu offers a vendor-neutral path for infrastructure as code—compatibility for a specific setup should still be validated rather than assumed.
Why is OpenTofu relevant?
- Open-source IaC: Linux Foundation governance and an OSI-approved license reduce vendor lock-in
- Terraform compatibility: Existing configurations and the provider ecosystem largely carry over
- Declarative and reproducible: Infrastructure defined as code is versionable, reviewable, and repeatable
- Sovereignty hedge: A predictable open path for teams wary of proprietary licensing changes