Terraform vs OpenTofu — what it means for your career
If you're learning infrastructure as code, you've probably seen both names and wondered which to bet on. Short version: the skills transfer — so learn the fundamentals and the tool choice mostly takes care of itself.
The 30-second answer
- • Same language (HCL), same core workflow (
init → plan → apply), same idea of state. - • They split over licensing, not over how the tool works.
- • What you learn here — the reconciliation loop, state, modules — applies to both.
What actually happened
In 2023, HashiCorp changed Terraform's license from the open-source Mozilla Public License (MPL 2.0) to the Business Source License (BSL) — a source-available license with restrictions on competing commercial use. In response, a group from the community created OpenTofu: a fork of Terraform that stays open source (MPL 2.0) and is governed under the Linux Foundation.
The disagreement was about licensing and governance — who controls the project and on what terms — not about a better or worse way to write infrastructure as code.
How different are they, really?
OpenTofu began as a drop-in compatible fork, so the things you spend your time learning are shared: the HCL syntax, resources and data sources, variables and outputs, the dependency graph, the plan/apply workflow, and the state model (including remote state and locking).
Over time the two can diverge — each may add features the other doesn't have, and version compatibility isn't guaranteed forever. But the day-to-day mental model is the same, and moving between them is closer to switching editors than learning a new language.
What it means for your career
Employers use both, and many job descriptions still say "Terraform" generically to mean "infrastructure as code with HCL." What gets you hired isn't which binary you typed — it's whether you genuinely understand state and drift, can read a plan, structure reusable modules, and wire it into CI/CD. Those transfer cleanly.
Practical advice: learn the concepts first, install whichever the job in front of you uses, and mention that you understand the split. Being able to explain it calmly in an interview signals that you follow the ecosystem.
What we teach
This platform is concept-first on purpose. You build the reconciliation-loop mental model, write real HCL, and break and recover state by hand — fundamentals that hold whichever tool your team standardises on.
Start with the fundamentals
No signup for lesson 1.
This explainer is general guidance, not legal advice. Licenses and project roadmaps change — check each project's official site for the current details.