Terraform, HashiCorp's infrastructure as code CLI owned by IBM, has been under the Business Source License since version 1.6.0. Pages here cover moving to OpenTofu, the open-source fork.
Terraform under the BSL against OpenTofu under MPL 2.0: configuration and provider compatibility, features added after the fork such as state encryption, provider for_each and -exclude, registry size, governance under the Linux Foundation and CNCF, and how far the two may diverge.
Switching the CLI from Terraform to OpenTofu: backing up state, installing tofu, re-initializing against the same backend, verifying with a no-change plan, handling terraform_remote_state dependencies, CI changes, and which Terraform version to move from.
What Terraform's Business Source License allows, since 1.6.0: internal production use, the definition of a competitive offering, embedding, paid support arrangements and the four-year change date, so legal and platform teams can decide whether to stay on Terraform or move to OpenTofu.
Terraform state can hold secrets in plain text. OpenTofu adds client-side encryption of state and plan files with PBKDF2, AWS KMS, GCP KMS, OpenBao or Azure keys. This page covers enabling it during a migration, key rotation and what it means for tools that read state.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.