If you've been pulled onto cloud or platform engineering reqs lately, you've probably noticed the skills line reads differently than it did two years ago. It used to say Terraform, full stop. Now you'll see Terraform/OpenTofu, HCL-based IaC experience, or Terraform or equivalent open-source alternative. That phrasing is not an accident and it is not sloppy copywriting. It reflects a real licensing fight that reshaped how enterprises buy and standardize on infrastructure as code tooling.
If you're deciding where to spend your next certification hours or lab time, you need to understand the mechanism behind that split, not just the headline that HashiCorp changed its license. The reqs are quietly testing whether you understand it too.
The BSL mechanics, not just the headline
In August 2023, HashiCorp moved Terraform and several other products from the Mozilla Public License 2.0 to the Business Source License 1.1, starting with Terraform 1.6. MPL is a standard open-source license. BSL is source-available but restricts certain commercial uses — specifically, it bars third parties from offering a competing managed service built directly on the licensed code. Each BSL-covered release converts to MPL again after a set delay, which HashiCorp has described as roughly four years per version.
That distinction matters for your resume because it matters for your client's legal and procurement teams. Companies that resell Terraform-adjacent SaaS products, or that simply wanted zero license ambiguity going forward, had a decision to make. Companies that only ever run Terraform internally, inside their own infrastructure, were largely unaffected in practice — but their platform teams still had to evaluate the change, because that's what governance and compliance functions do.
Where OpenTofu actually fits
The Linux Foundation announced the OpenTofu project in September 2023, forked from the last MPL-licensed Terraform codebase. It reached a 1.0 general-availability release in early 2024 and has continued independent releases since, adding features like native state encryption and provider-defined functions that didn't exist in the forked baseline. Governance runs through an open technical steering committee under Linux Foundation rules, with contributions from multiple vendors rather than one company controlling the roadmap.
That governance model is the actual selling point for the platform teams who adopted it — not a feature checklist, but a structural guarantee that no single vendor can change the license terms again unilaterally. If you're asked in an interview why a client chose OpenTofu, that's the answer worth giving, not just it's free.
How requisition language actually shifted
Across the reqs we see move through contract staffing pipelines, the practical change looks like this:
- Tool-agnostic phrasing is now common. Terraform/OpenTofu or HCL-based IaC has replaced flat Terraform required in a meaningful share of cloud and SRE postings.
- HashiCorp Enterprise shops kept Terraform-specific language. If a client is paying for Terraform Cloud or Terraform Enterprise, Sentinel policy as code, or private module registries, their req still says Terraform by name, because their tooling investment is tied to that product.
- Platform-as-a-service vendors mention both explicitly. Orgs using Spacelift, env0, Scalr, or similar third-party orchestration layers are more likely to list both tools, since those platforms support either backend.
- Nobody is advertising a ban on either tool. You won't see Terraform not accepted language in a lawful posting — what you'll see is broader skill framing that lets a hiring manager evaluate either background equally.
Who moved, who didn't, and why
The pattern isn't random. Three factors tend to predict a client's posture, and they're worth asking about directly in a screening call:
- Sunk cost in HashiCorp's commercial layer. Teams with existing Terraform Enterprise contracts, VCS-driven workspaces, and Sentinel guardrails have real switching costs. Expect them to stay put, at least through their current contract cycle.
- Regulatory and legal sensitivity. Highly regulated industries — finance, healthcare, government contractors — tend to move slower on any license change, not because OpenTofu is risky, but because re-approving a new tool through vendor risk review takes time regardless of which direction they're headed.
- Greenfield platform builds. New platform engineering teams building from scratch, especially ones without existing HashiCorp licensing, are the segment most likely to pilot OpenTofu from day one, since there's no migration cost to weigh.
Don't assume adoption curves have settled. Check the CNCF and Linux Foundation release notes and HashiCorp's own developer documentation before you commit lab time to one over the other — the governance story is stable, but the market share numbers move, and you should verify current adoption data at the source rather than trust a secondhand claim.
What the state management and module design question really probes
When an interviewer asks how do you handle state in a multi-environment setup, they are rarely testing whether you memorized backend syntax. They're testing whether you understand the failure modes: state locking under concurrent runs, drift between what's in the state file and what's actually deployed, and how sensitive values end up stored in plaintext state unless you've addressed it. OpenTofu's native state encryption and Terraform's existing backend options both solve pieces of that problem differently — know which one your target client runs before the call.
A module design question works the same way. They're not asking if you can write a resource block. They're asking whether you design for reuse: versioned modules in a private registry, variable validation blocks that fail fast instead of deploying bad input, and whether you default to for_each over count for anything that might be reordered. If you've only ever copy-pasted modules from a public registry without versioning them, that's the gap the question is designed to surface.
Quick comparison for your next 90 days
| Dimension | Terraform | OpenTofu |
|---|---|---|
| License | Business Source License 1.1 (converts to MPL after a delay per release) | Mozilla Public License 2.0 |
| Governance | HashiCorp, single vendor | Linux Foundation, multi-vendor technical steering committee |
| Enterprise tooling | Terraform Cloud/Enterprise, Sentinel policy as code | Third-party orchestration layers (Spacelift, env0, Scalr, Atlantis) |
| State encryption | Via backend configuration | Native state encryption feature |
| Typical client profile | Existing HashiCorp commercial contracts, regulated industries | Greenfield platform builds, cost-sensitive or license-averse teams |
What to actually do tonight
Don't pick a side to bet your career on — the brief here isn't to predict a winner, and anyone who tells you confidently which tool wins is guessing. Instead, make sure your HCL fundamentals transfer cleanly to either CLI, since the syntax is nearly identical. Spend an hour reading OpenTofu's latest release notes and HashiCorp's current licensing FAQ directly from their sites, so you can speak to the mechanism accurately in an interview instead of repeating a headline. And when a recruiter sends you a req that says Terraform/OpenTofu, ask which backend the client actually runs before your first call — it tells you which commercial ecosystem, and which screening questions, you're walking into.
If you want a second set of eyes on how your IaC background maps to what clients are actually asking for right now, the team at Josh Pros LLC reviews this kind of req language every day. Reach out at contact@joshpros.com or visit https://joshpros.com.
#Terraform #OpenTofu #InfrastructureAsCode #CloudConsultant #SRE #DevOps #PlatformEngineering #ITContracting #TechContractJobs #HCL #CloudSkills #ITStaffing
Talk to a real recruiter, not a bot.
We'll tell you the rate, the client, and the terms before you interview. And if we're not the right fit, we'll say so.