Reading a new source available license carefully.

Reading a new source available license carefully is a skill worth building, because the wave of relicensing since 2023 has put these documents in front of buyers who never expected to parse them. The instinct is to react to the name. A team hears Business Source License or Server Side Public License and assumes the worst, or assumes nothing has changed because the code is still visible. Both reactions skip the only step that matters: reading the specific terms against your specific use. Source available licenses are not interchangeable, and even within one family the operative clauses differ by project. The exposure lives in a handful of provisions, and the careful reader goes straight to them.

This article is part of the pillar on open source relicensing, and builds on the core distinction in source available is not open source and why it matters.

Find the use restriction first

The first clause to locate is the one that limits what you may do. In the Business Source License this is the restriction on competitive production use, the provision that bars using the software to offer a product or service that competes with the licensor. In the Server Side Public License it is the obligation that attaches when you make the software available to others as a service, which can require releasing the source of the surrounding service stack. These are the clauses that turn a routine dependency into an exposure. Read them slowly, and read them against what you actually do with the component, not against a general impression of what the license is for. The gap between the two is where most misjudgment happens. The mechanics of each are set out in the Business Source License explained and the Server Side Public License explained.

Read the additional use grant for the specific project

The Business Source License is a framework rather than a fixed license. The base text leaves a blank that the licensor fills in with an additional use grant, and that grant is where the real boundary sits. Two projects can both use the Business Source License and permit very different things, because each writes its own grant. So reading the base license is not enough. You have to find the project's specific grant and read what it permits before the conversion date. A use that is fine under one project's grant may be restricted under another's. This is the single most common place where a careful read diverges from a casual one, and it is why you cannot reason about the Business Source License in the abstract.

For HashiCorp's products under the Business Source License as of August 2023, the grant defines what counts as competitive, and reading it against your use is the heart of any exposure judgment.

Check the conversion date and the version scope

Next, find the time dimension. The Business Source License converts to an open license after a delay set by the licensor, commonly four years, after which that specific version becomes openly available. The Server Side Public License and the Elastic License do not convert in that way. Knowing whether a conversion applies, and when, changes the calculus of waiting versus acting. A version that converts in eighteen months is a different proposition than one that never will. The four year mechanism and what it means in practice is covered in the four year delay in the BSL explained. Pair the conversion read with the version scope: the license applies to releases from a certain point, so confirm which versions you run fall inside the new terms and which predate them.

Mine the definitions, then call your counsel

The definitions section is where careful readers spend their time, because the operative clauses are only as clear as the terms they use. Words like competitive, production, distribute, and offering the software as a service all carry precise meanings defined elsewhere in the document, and your exposure turns on whether your use falls inside those definitions. A restriction that looks broad narrows once you read how its key terms are defined, and one that looks narrow can widen the same way. Read the definitions before you conclude anything about the restriction, not after. This disciplined read produces something valuable: a clear list of the questions your use actually raises. That list is what you hand to your own counsel, whose interpretation is the binding one. Reading a new source available license carefully is how you arrive at the right questions, not how you answer the legal ones yourself.

This article is commercial and licensing risk advisory, not legal advice. For interpretation of a specific clause against your use and your binding compliance position, your own counsel is the right place to turn.