The fork of OpenTofu from Terraform following HashiCorp's license change to BSL has created a genuine choice in the infrastructure as code landscape. Both projects continue active development with diverging feature sets, and organizations must evaluate which path aligns with their operational and philosophical requirements.
Feature Divergence and Compatibility
OpenTofu has introduced client-side state encryption, a feature long requested by the community, allowing sensitive values in state files to be encrypted at rest without relying on backend-specific encryption. This capability addresses a significant security gap that Terraform addresses only through backend configuration.
Terraform continues to advance with improvements to the testing framework, enhanced import workflows, and deeper integration with HCP Terraform (formerly Terraform Cloud). Provider development benefits from Terraform's larger ecosystem and the continued investment by HashiCorp in the provider development kit.
Module and provider compatibility remains high between the two projects, with most existing Terraform modules working with OpenTofu without modification. However, as features diverge, module authors increasingly need to decide whether to support both tools or choose one, creating potential fragmentation in the ecosystem.