Manufacturer right sizes a commercial open source license.

Situation

The company was a global industrial manufacturer with a large engineering organization spread across plants and product lines. It had standardized on an infrastructure tool years earlier under an open source license and deployed it widely, from production automation pipelines to small internal utilities maintained by individual teams. The tool was woven through the estate, but no one held a precise account of where it ran or how each instance was used.

The exposure that triggered the work

A relicensing event moved the tool from an open source license to the Business Source License 1.1, which restricts competitive production use and converts to an open license only after a delay, commonly four years. Source available is not open source, and the Business Source License is not approved by the Open Source Initiative. The vendor approached the manufacturer with a commercial license to continue using current versions without restriction. The opening quote was substantial and was sized to the company's total deployment count, which the vendor had estimated from the outside. Procurement had no independent basis to challenge the figure, because the company did not yet know its own usage well enough to push back.

Approach

We started by building a usage baseline. Software composition analysis and deployment discovery produced an accurate count of every instance, with each one classified by how it was used: production automation, internal tooling, or dormant. The baseline showed that a large share of the deployments the vendor had counted were internal or inactive, sitting well outside the competitive production use the license actually restricted. The in scope footprint that genuinely warranted a commercial license was a fraction of the total.

We also established a credible alternative. The community fork created after the license change offered an open license path for the deployments that did not need the commercial version, which gave the manufacturer real leverage rather than a take it or leave it choice. With the usage baseline and the fork alternative in hand, the negotiation shifted from the vendor opening number to the evidence. The conversation moved to what the company actually ran in scope, on what term, and at what volume.

Outcome

The agreement closed at a fraction of the opening quote, sized to the in scope production usage rather than the company's total footprint. Deployments that did not need the commercial version moved to the open fork, which removed them from the licensed count for good. The manufacturer secured a multi year term that fixed pricing against future increases, and it walked away with a usage baseline it now maintains, so the next renewal will start from its own evidence rather than a vendor estimate. The combination of a right sized license and a documented baseline turned a recurring surprise into a managed, predictable cost.

Lessons for buyers

Three lessons carry to other buyers. First, a vendor quote is an opening position, not a measurement, and the only way to challenge it is with your own usage evidence. Second, a credible fork is leverage, because it lets you remove out of scope deployments from the licensed count rather than paying to license them. Third, the usage baseline outlives the deal. The same evidence that right sized this agreement will anchor every renewal that follows, which is where much of the lasting value sits.

Right sizing a license like this is the work of our open source commercial license negotiation service. For the wider context, see our pillar on HashiCorp and Terraform under the Business Source License and our guide to quantifying open source license exposure.