Terraform vs OpenTofu: What the Fork Means for the Exam and Your Career

If you are studying for the Terraform Associate and keep seeing "OpenTofu" mentioned, you are right to wonder what it is and whether it changes your plan. The short version: OpenTofu is an open-source fork of Terraform born from a 2023 licence change. The certification exam is still 100% Terraform, so it does not change what you study. But the fork is worth understanding, because it shapes the tools you may actually use on the job. This guide explains the split honestly, what it means for the exam, and how to think about both tools for your career.

Why OpenTofu exists: the licence change

For most of its life Terraform was licensed under the Mozilla Public License (MPL) 2.0, a permissive open-source licence. In August 2023 HashiCorp relicensed Terraform (from version 1.6 onward) to the Business Source License (BSL) 1.1. The BSL is "source available" rather than open source: you can read and use the code, but you cannot use it to build a product that competes with HashiCorp. Each release converts to MPL only four years after it ships.

That restriction landed hardest on vendors who had built businesses around Terraform. A coalition of them and community members forked the last MPL-licensed release (Terraform 1.5) and launched what became OpenTofu. Early backers included Spacelift, env0, Gruntwork, Harness, Scalr, and Cloud Posse. The project was donated to the Linux Foundation, and it uses the MPL 2.0 that Terraform left behind. In April 2025 it was accepted into the Cloud Native Computing Foundation (CNCF) as a sandbox project.

One more piece of context: IBM completed its $6.4 billion acquisition of HashiCorp in February 2025. That did not reverse the BSL, but it renewed questions about long-term stewardship, which is part of why OpenTofu's independent, foundation-run governance appeals to some teams.

Where the two projects stand today

Both tools are alive and actively developed. Terraform (now at the 1.12 line, which the exam targets) remains the market leader by a wide margin and carries the larger provider and module ecosystem, HCP Terraform (formerly Terraform Cloud), and commercial support. OpenTofu has grown quickly and now ships some features ahead of Terraform's open binary, such as built-in state encryption, early variable evaluation, and provider-level for_each.

Adoption figures vary by source and should be read as directional, not precise. Community surveys and vendor write-ups through 2026 put OpenTofu somewhere in the low double digits of practitioner usage, with Terraform still dominant. Treat any single percentage you see (including here) as an estimate.

Does the fork affect the certification?

No. The current exam, the HashiCorp Certified: Terraform Associate (004), tests Terraform 1.12 and its workflow. There is no OpenTofu certification. Nothing in the eight objective domains, from IaC concepts and the core workflow to state, modules, and HCP Terraform capabilities, changes because OpenTofu exists.

One domain is worth flagging precisely because of who owns what: HCP Terraform capabilities are new emphasis in the 004 and are a HashiCorp product. That material has no OpenTofu equivalent, so study it as HashiCorp documents it. If your day job uses OpenTofu, do not let the muscle memory of the tofu binary or a third-party platform trip you up on HCP-specific questions.

The good news for anyone who uses OpenTofu at work: because the two tools share HCL and the plan/apply workflow, almost everything you practise transfers. The exam-relevant differences are naming and platform, not core concepts.

What this means for your career

The practical reality is that these are not rival skills you must choose between. Learning one gets you most of the way to the other. Here is how to think about it:

• Certify on Terraform. It is the credential employers recognise, the exam is stable on the 1.12 line, and the concepts are the foundation for both tools.
• Know OpenTofu exists and why. Being able to explain the licence change, the governance model, and the trade-offs is exactly the kind of context that makes you sound current in an interview.
• Use whatever your team uses. If an employer has migrated to OpenTofu, your Terraform knowledge applies directly; migration is often as simple as swapping the binary. If they are on Terraform and HCP, your cert maps cleanly.
• Watch for divergence. The projects still track closely, but they are drifting. Over time, features unique to each side may matter more. Keep an eye on release notes rather than assuming perfect parity forever.

In hiring terms, "Terraform" is still the phrase in most job postings, and the certification signals competence in the whole IaC workflow regardless of which binary you run. OpenTofu literacy is a complement, not a substitute.

Bottom line

OpenTofu is a genuine, well-governed open-source fork that exists because of a real licence change, and it is worth understanding. But it does not complicate your certification path: the exam is Terraform, the concepts are shared, and the skills transfer both ways. Study Terraform, learn the story behind the fork, and you are covered whichever tool you end up using.

Ready to start? Our Terraform Associate overview guide maps the full 004 exam, and the study planner turns it into a week-by-week schedule. When you want to test yourself, head to the practice exams.