Is Your Terraform Use Competitive Under the BSL?

When HashiCorp changed the Terraform license, many teams assumed the worst: that any continued use was now restricted. That reading is too broad and leads to wasted migration effort. The Business Source License is permissive in most respects and narrow in its restriction. Understanding exactly where the restriction bites is what separates a calm, evidence based decision from a costly overreaction. The question is not whether you use Terraform. It is whether your specific use falls inside the competitive carveout.

What the Business Source License actually restricts

As of August 2023, HashiCorp moved Terraform, Vault, Consul, Nomad, and Packer from an open source license to the Business Source License 1.1. The Business Source License grants broad rights to use, copy, modify, and run the software, then carves out a single significant restriction: production use that competes with the licensor's commercial offerings. After a delay, commonly four years, each version converts to an open license. The structure means most use is permitted and a defined slice is not. Source available is not open source, and the Business Source License is not approved by the Open Source Initiative, but neither fact changes the shape of the restriction. The general mechanics are set out on the HashiCorp and Terraform pillar.

Why most internal Terraform use is not competitive

An enterprise that uses Terraform to provision and manage its own cloud infrastructure is doing the thing the license was designed to permit. Running pipelines, managing state, and deploying your own systems are internal uses, not the offering of a competing product or service. For the large majority of Terraform users this is the whole story, and the appropriate response to the license change is to confirm that posture rather than to scramble. The risk of treating all use as competitive is a migration program no one needed, with its own cost and disruption. The way to size whether any move is justified is covered in relicensing and cloud and managed service use.

Where Terraform use can become competitive

The exposure concentrates in a smaller set of patterns. A software vendor that embeds Terraform inside a product it sells, a platform that offers Terraform functionality to its own customers as a managed capability, or a service that wraps Terraform and resells the result are the patterns most likely to fall inside the competitive carveout. The dividing line is whether you are offering something that competes with what HashiCorp sells, not whether Terraform happens to be in your stack. Independent software vendors face this question most directly, and it is covered in HashiCorp BSL for software vendors and ISVs. Edge cases such as recovery environments are covered in HashiCorp BSL and disaster recovery environments.

How to test your own deployment

The test has three steps. First, identify which Terraform versions you run and whether they predate the August 2023 change, because pre change versions remain under the prior license. Second, classify each use: internal infrastructure management, embedded in a product you ship, or offered to others as a service. Third, test the offered patterns against the competitive restriction and flag anything ambiguous for your counsel. Where a pattern is competitive, size the cost to cure across the usual paths, including moving to the OpenTofu fork, which is covered in the OpenTofu and Valkey fork story. A relicensing exposure review produces this analysis end to end.

We are independent and buyer side. We take no vendor fees and resell no software, so our read of whether your Terraform use is competitive reflects your risk and nothing else, including when the honest finding is that your use is fine and needs no change. This is commercial and licensing risk advisory, not legal advice. For interpretation of the Business Source License and your compliance position, engage your own counsel.