What critical change happened
to Terraform’s license?
In August 2023, HashiCorp switched Terraform from MPL 2.0 (open source) to BSL 1.1 (Business Source License), a “source-available” license with commercial restrictions.
In practice, the code is visible, but you may not use it to build competing services/products (e.g., embed/host it as an alternative to Terraform Cloud/Enterprise). This triggered a community split and led to the OpenTofu fork under the Linux Foundation.

Practical implications for teams
  • Legal risk for vendors/integrators who want to sell managed Terraform services or SaaS around it.
  • Community response: creation of OpenTofu under the LF, positioned as a free/open alternative; compatibility with existing Terraform configs makes migration easier.
  • Compatibility today: most Terraform configurations run on OpenTofu without changes; feature divergence may grow over time.
  • 🔴 Do you fear state loss or drift if you switch tools?
    We plan and rehearse backend and state migration safely.
  • 🔴 Are modules duplicated and tied to Terraform specifics?
    We convert, standardize and publish shared modules.
  • 🔴 Will CI break across repos?
    We retool pipelines with tests and policies.
🔴 Still postponing migration because production risk is unclear?
We stage, test and cut over with rollbacks ready.
🔴 Are policies and guardrails missing from your IaC?
We add policy-as-code and drift detection.
💯 Practice Areas
ADG OpenTofu Factory audits IaC and modules, migrates backends and state, converts modules, rebuilds CI pipelines and adds policy-as-code.

You keep uptime, gain governance and reduce vendor risk while teams keep shipping.

🔸 No-downtime migration plan and execution.
🔸 Governed modules with reuse and speed.
🔸 CI pipelines that keep shipping.
🔸 Reduced vendor and license risk.
🔸 Clear documentation and training.
🔸 Optional support for new modules.
How It Works
Inventory
List TF versions, backends, modules and envs. Identify state risks and module snowflakes early.
☑️ Migrate with ADG
Plan & guardrails
Define backend moves, state rekeys and conversion order. Prepare rollbacks and shadow plans.
Dry runs
Rehearse in non-prod, fix module quirks, add tests so plan/apply diffs are clean.
CI retool
Swap pipelines to OpenTofu, add policy-as-code and drift checks. Make governance a byproduct of migration.
Cutover
Migrate state with a tight window, validate resources and dependencies, keep uptime intact.
Enablement
Publish converted modules to a registry with examples, so teams ship next day.
Post-care (optional)
Patch modules, watch drift, help teams until the platform is steady.
Documentation & Reporting (optional)
We produce lean, engineer-first artifacts that can scale to audit grade if needed - diagrams, IaC refs, runbooks, SLO dashboards, and change logs. Evidence packs are versioned and reproducible: links point to live systems or CI exports, not slides. Scope is tailored per client - from a 1-page ops sheet to a full compliance bundle with test replays and data lineage. If you prefer, we keep it minimal and focus on code and metrics only.
What you pay for
  • Assessment
    IaC inventory, module map, state and backend review.
  • Migration
    State cutover, module conversion, CI rebuild, validation.
  • Policy and CI add-on
    Guardrails, drift detection, approval workflows.
  • Support
    Post-migration fixes and module upkeep.

General transparency note

Pricing reflects two components where applicable:
✅ Expert work
Architecture, implementation, monitoring, reporting.
✅ Resources
Compute, storage, network and third-party tooling used to meet your SLAs
We keep these components itemized so you see exactly what delivers the outcome.