BUSL 1.1 is a template, and the blanks are what matter

The workload

Evaluating a BUSL-licensed dependency is not a single lookup, because verified, the Business Source License 1.1 template published by MariaDB is only a shell. It defines the mechanism: a Licensor, a Licensed Work, an Additional Use Grant, a Change Date, and a Change License, but each adopting project fills in its own values for those blanks. The workload is reading the specific project's own attached parameters, not assuming BUSL means one fixed thing across every tool that uses it.

What the documents show

Verified: the template states that 'effective on the Change Date, or the fourth anniversary of the first publicly available distribution of a specific version of the Licensed Work under this License, whichever comes first, the Licensor hereby grants you rights under the terms of the Change License,' at which point the BUSL restrictions on that version end. Four years is the template's default outer bound; a project can set an earlier Change Date, and the Change License it converts to is likewise the project's choice. The Additional Use Grant is where production-use permissions actually live: it can permit some production use while restricting other uses, such as competing offerings. A concrete example, IBM's own published license file for Terraform, sets its Change Date as 'four years from the date the Licensed Work is published,' its Change License as 'MPL 2.0,' and its Additional Use Grant as permission for production use that does not offer Terraform 'on a hosted or embedded basis' competing with IBM's paid versions. Those three values are that project's own, not BUSL's.

The operating cost

The template itself states no fee; whatever a given project charges for use outside its Additional Use Grant is that project's own commercial term, not part of BUSL 1.1. Estimated: the real cost to a founder is the review time spent reading each BUSL-licensed dependency's specific grant before deployment, since two projects using the same template can permit different production uses entirely.

The stop condition

Per the template, the restriction on a given version ends automatically at that version's Change Date, converting it to the stated Change License; no renewal or repurchase is required to receive that later status. Until that date, the stop condition is whatever the Additional Use Grant does not permit, which is why naming a company's Change Date or grant without citing that company's own license file would misstate a term BUSL leaves open by design.

• What does this specific project's Additional Use Grant actually permit in production, not what BUSL permits in general?
• What is this version's stated Change Date, and what Change License does it convert to?
• Does the planned use fall inside the grant, or does it require a separate commercial agreement?

BUSL is a licensing mechanism, not a fixed set of rights. Its content lives in the blanks a specific project filled in, and those blanks are the only thing worth reading closely.