Of all the texts on this shelf, the Business Source License has the most elegant structure. It is a license with a clock inside it. The code is published immediately, readable and usable for almost everything except the one commercial use the author reserves, usually offering the software as a competing hosted service. Then, on a date written into the license itself, typically three or four years after release, the text converts automatically into a true open source license, usually the GPL or Apache.

Restricted now, open on a stated date. The BSL is the only major license that ends itself.

The grammar of reserved uses and windows is not unique to code; a stock footage archive manages the same logic of which rights are held back and for how long on every clip it licenses.

The mechanism on the page

The license has three moving parts. The Additional Use Grant names the restricted activity, the thing you may not do without paying, written narrowly so that ordinary use stays free. The Change Date sets the deadline after which the restriction expires. And the Change License names the open license the code falls into when the date arrives. After conversion, the file is simply open source, forever.

MariaDB adopted the model in 2016, and HashiCorp ran a version of it until 2023. Each release under the BSL carries its own date, so a project accumulates a rolling archive of code that opens up version by version, like a glacier of freedom advancing a few years behind the present. The archive grows whether or not anyone remembers to announce it, because the conversion is written into the license itself rather than into a promise.

Why the delay exists at all

The BSL is the cloud era's answer to a problem copyleft could not reach. If a cloud provider can take your open code, host it, and sell the service without contributing anything, the company that wrote the code funds the provider's product. The BSL buys the authors a window of protection in which only they can sell the hosted service, then keeps its promise by releasing each version into the commons.

It is the contribute-or-pay instinct again, expressed as a calendar rather than a royalty. The same grammar of rights and windows appears in other fields that license creative work, where time-bound and use-bound rights are managed with the same underlying logic of which uses are reserved and for how long.

The mechanism also produces an unusual kindness. Because the conversion is automatic, a company cannot quietly decide not to release the old versions. The date is already in the license, and the license is already in the file.

Not open source, and honest about it

The BSL's authors are unusually candid that the license is not open source during its restricted window. The text discriminates against a field of endeavor, which fails the definition. But because it converts to an open license automatically, it is the one restricted license that schedules its own admission to the open shelf. The Open Source Initiative and the license's defenders argue about whether the conversion promise is worth the wait; the compromise is that the debate happens at all, in public, over a text that says plainly what it is.

What conversion means in practice

When the change date passes, no signature is needed and nothing is announced. The license text on the old version simply stops restricting, and the file becomes governed by the change license from then on. A version released under the BSL in 2023 might convert to Apache in 2027, joining the open archive while the current release remains under the window. Projects that adopt the BSL commit to an endless, scheduled donation of their past work.

Where the model is argued

There is also a subtler question the license raises: whether a promise written into a file is the same as a promise made to a community. The BSL answers by making the promise self-executing, which is the strongest form it can take, because it does not depend on the company still existing or still meaning it when the date arrives.

The arguments are practical. Critics note that the restricted window can outlast the commercial relevance of a version, making the open conversion a donation of code nobody needs anymore. Defenders reply that the rolling archive is still a real commons, better than permanent closure. The license also puts pressure on the company to keep shipping, since each new version restarts its own clock while the old ones keep converting underneath it.

The tidy ending on the shelf

Filed in the binder, the BSL is the license that most resembles a contract with time inside it: a bargain struck now whose restrictive half dissolves on a date certain. It is the source-available family's most disciplined member, and the closest anyone has come to reconciling the need to be paid with the promise to be open.

The BSL is also the license that most respects the reader's time. Three clauses carry the whole mechanism, the conversion is automatic, and the text says plainly what it is during the window. On a shelf full of instruments that blur their own edges, the license that ends itself is the one that reads most like a contract.

What the text grants

Immediate source access for most uses, with one commercial use reserved, then automatic conversion to open source on the change date.

What a reader should check

The additional use grant, the change date, and the change license named for the conversion.

The limit of this reading

During the window the license is restricted, and the open conversion applies to the version, not the project forever.