BUSINESS SOURCE LICENSE
BSL License Risk Advisory
BSL license risk advisory maps where you depend on software now under the Business Source License, quantifies the exposure the competitive use restriction creates, and gives you a contained path forward. Built for enterprises running Terraform, Vault, Consul, Nomad, and Packer. Independent, buyer side, paid only by you.
Not ready to talk? Read the free open source license risk guides first.
Independent, confidential, buyer side. See how buyers contained their exposure →
As of August 2023, HashiCorp moved Terraform, Vault, Consul, Nomad, and Packer from an open source license to the Business Source License 1.1. IBM later acquired HashiCorp. The Business Source License restricts competitive production use and converts to an open license only after a delay, commonly four years. For most enterprises the headline is simple: a tool you adopted as open source now carries terms that depend on how you use it, and the change reaches versions you are likely to upgrade to.
BSL license risk advisory exists to make that exposure legible. We start by finding every place the affected products run, direct and embedded, then separate the deployments that sit comfortably inside the license from the ones that do not. The result is a clear, current picture you can take to procurement, engineering, and your board.
What the Business Source License changes for you
The Business Source License is source available, not open source. It is not approved by the Open Source Initiative. The core restriction is on competitive use: you may not offer the software as a product that competes with the licensor. For an internal platform team that line may be easy to stay behind. For a managed service provider or a vendor that embeds the tooling, the line is exactly where the risk lives. We size that distinction for your business rather than reading the worst case onto every deployment.
The advisory also accounts for the conversion clause. Each version converts to an open license after the stated delay, so the exposure on an old release differs from the exposure on a current one. We map that timeline against your upgrade cadence so you know which decisions are urgent and which can wait.
Your options: fork, license, or stay
There are three honest paths, and we weigh them on equal terms. You can move to OpenTofu, the community fork of Terraform published under an open license, where that fits your modules and providers. You can take a commercial license from the vendor where the relationship and the feature set justify it. Or you can stay on the version you have, understanding the support and conversion timeline that comes with it. Each path carries an engineering cost, a license posture, and a timeline, and we attach all three so the choice holds up under scrutiny.
For the full picture of the HashiCorp change and the fork landscape, see our pillar on HashiCorp and Terraform licensing. When the right answer is a negotiated agreement, our relicensing exposure review sizes the deal from your side of the table.
Why a buyer side advisor
We sell no tooling and take no vendor commission. We are paid only by you. That matters most when the options include a commercial license, because the advisor recommending the deal should not be the party who benefits from it. Our recommendation reflects your exposure and your leverage, nothing else. You can read more about why our independence matters.
COMMON QUESTIONS
BSL questions buyers ask.
What is BSL license risk advisory?
BSL license risk advisory maps where your organization depends on software now under the Business Source License, quantifies the exposure that the competitive use restriction creates, and sets out a contained path forward. It covers HashiCorp products such as Terraform, Vault, Consul, Nomad, and Packer, which moved to the Business Source License as of August 2023.
Who needs a BSL risk advisory?
Any enterprise running Terraform, Vault, Consul, Nomad, or Packer in production, and any vendor that builds on them. The Business Source License restricts competitive production use and converts to an open license only after a delay, so the exposure depends on how you use the software, not just that you use it.
Does the Business Source License affect software already in production?
Yes. A license change applies to new versions you adopt. Software you already run under the prior open license keeps those terms, but upgrades, new deployments, and many support paths pull you onto the Business Source License. That is why mapping current usage matters.
Is OpenTofu a safe alternative to Terraform?
OpenTofu is the community fork of Terraform created after the Business Source License change and is published under an open license. Whether it fits depends on your modules, providers, and support needs. We weigh the fork, a commercial license, and staying put on equal terms, with cost attached to each.
Is this legal advice?
No. BSL license risk advisory is commercial and licensing risk advisory, not legal advice. For interpretation of the Business Source License and compliance questions, we recommend your own counsel.
CONTAINMENT
Map your Business Source License exposure.
A confidential open source license risk assessment. Independent, buyer side, paid only by you.