Buying snapshot
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Decision point | What OpenTofu states |
|---|---|
License | Mozilla Public License v2.0 (MPL-2.0) |
Governance | Community-driven project under the Linux Foundation's stewardship; a Technical Steering Committee meets every other Tuesday |
How you run it | Command-line tool ( |
Terraform compatibility | Described as a drop-in replacement for Terraform that preserves existing workflows and configurations |
Providers and modules | 3,900+ providers and 23,600+ modules, per the OpenTofu site; searchable in the OpenTofu Registry at search.opentofu.org |
Where to get help | GitHub Discussions, GitHub issues and the #opentofu channel on the CNCF Slack |
Our take
Choose OpenTofu if your team wants its infrastructure tool under an open-source license and foundation governance, or needs OpenTofu-only features such as client-side state encryption or the -exclude flag. If you are moving from Terraform, it is a good fit when your configurations rely only on features OpenTofu also has.
Evaluate OpenTofu
Where it stands out
Open license, open governance. OpenTofu's own FAQ calls the BUSL and its additional use grant ambiguous, and says HashiCorp's definition of "competitive" or "embedding" could change. An MPL-2.0 project under the Linux Foundation removes that question for vendors and consultancies that manage infrastructure for others.
Client-side state encryption (v1.7). State can be encrypted at rest with key providers such as PBKDF2, AWS KMS, GCP KMS and OpenBao, so it stays encrypted even in a remote backend.
Features of its own. The site lists features unique to OpenTofu: the
-excludeflag (v1.9) to leave resources out of a plan or apply, provider iteration withfor_eachfor multi-region or multi-account setups, and early variable and local evaluation (v1.8) to set module versions from one variable.Plan before apply. A planning step shows what OpenTofu will change before you apply it, and a resource graph runs independent changes in parallel and shows dependencies.
Product screenshot
Trade-offs to weigh
Feature sets can differ from Terraform. The project says the community decides what features OpenTofu gets, and asks users to open an issue if a Terraform feature is missing. Check any recent Terraform feature you depend on before you migrate.
Registry access is blocked in some countries. To comply with sanctions, the OpenTofu Registry blocks access from specific countries of origin, which matters for teams that work from those places.
Public signals
About these signals
Verified factual signals from public sources. They indicate observable activity or interest, not total adoption, product quality, or cost.
240 GitHub commits 90d30.8k GitHub stars
See all signals from 2 sources
Alternatives
Terraform is the direct alternative and the project OpenTofu forked from. OpenTofu's FAQ says either tool could work for personal use, since the BUSL has no restrictions for non-commercial use. The choice matters most for companies, where the FAQ argues that staying with a project that changed its license carries more risk than switching.
Alternatives to OpenTofu
The reviewed substitutes for OpenTofu among the infrastructure as code, and what would make each one the better answer.
Direct alternatives
Reviewed substitutes: products bought for the same job, where a team picks one.
- Terraform
- OpenTofu is a fork of Terraform, created in 2023 after HashiCorp moved Terraform to the Business Source Licence, and now a Linux Foundation project under MPL-2.0. It reads the same HCL and consumes the same provider ecosystem, so the two are as directly substitutable as any pair in this catalogue, and a team runs one. The decision is licence and governance rather than capability: an OSI-approved licence with a public steering committee against a single vendor's supported stack.Applies to: Declaring and reconciling cloud infrastructure in HCL. OpenTofu stands in for Terraform when the Business Source Licence is a problem for your organisation, or when open governance of a core dependency is worth a migration; Terraform stands in when the licence poses no issue and its commercial stack and larger body of documentation decide.
Other approaches
A different approach to the same problem. Each substitutes only for the workload named beside it.
- Pulumi
- Both are answers to Terraform's licence change, reached from opposite directions: OpenTofu keeps the HCL authoring model and changes the governance, Pulumi keeps a commercial vendor and changes the authoring model. A team leaving Terraform weighs them against each other, and the choice is whether the objection was to the licence or to the language.Applies to: Choosing an infrastructure-as-code tool after leaving Terraform. OpenTofu stands in when HCL is right and the objection was licensing; Pulumi stands in when the objection was the configuration language itself and general-purpose code with tests is the goal.