OpenTofu: The OSS Fork That Keeps Infrastructure as Code Truly Open

If you've been following the Terraform licensing drama, you know that HashiCorp switched from MPL 2.0 to BSL in 2023. That move left a lot of teams wondering what comes next for their IaC workflows. Enter OpenTofu: a community driven fork of Terraform that stays fully open source under the same MPL 2.0 license we all relied on.

The project is backed by the Linux Foundation and a bunch of vendors who want infrastructure provisioning to stay open, modular, and vendor neutral. No hidden gotchas. No license anxiety.

What It Does

OpenTofu is a direct drop in replacement for Terraform. It reads the same HCL configs, talks to the same providers, and manages the same state files. You write infrastructure as code, apply it, and your cloud resources (or on prem stuff) just appear.

The core workflow is identical: init, plan, apply. If you know Terraform, you already know OpenTofu.

Why It's Cool

A few things make this project stand out:

• 100% backward compatible with Terraform 1.6.x – your existing modules, state files, and workflows work without changes.
• Community governance – no single company controls the roadmap. Decisions are made in the open by maintainers and contributors.
• Additional features planned – things like richer encryption for state files, provider registry mirrors, and better remote operations are on the table. The community can prioritize what actually matters instead of corporate strategy.
• No license switching – MPL 2.0 stays. Period. That means you can fork it, embed it, or build commercial products on top without worrying about future rug pulls.

The most pragmatic angle? If you're already using Terraform, you can swap the binary and keep going. No migration cost. No "rewrite everything in Pulumi" weekend.

How to Try It

Installing OpenTofu takes about two minutes:

1. Download the binary – grab the right package for your OS from the releases page.
2. Replace your Terraform binary – rename or symlink tofu to terraform (or just use tofu directly).
3. Run your existing workflows – tofu init and tofu apply will do the exact same thing as before.

If you're on macOS with Homebrew: