This page is general information, not legal advice. Have a lawyer read any license before you adopt or publish it.
How it works
Publishing code and licensing it as open source are two different things. The Open Source Initiative’s definition begins: “Open source doesn’t just mean access to the source code.” Its criteria include free redistribution, source code included, and no discrimination against fields of endeavor. On that last point it says the license must not restrict anyone from using the program in a specific field, and gives the example that it may not restrict use in a business.
A license that says “free for personal use, paid for commercial use” fails that test, however open the repository is. Such code is source-available: visible, often modifiable, but with limits on use. A source-available license usually restricts one or more of these:
- Commercial or production use.
- Offering the software as a competing hosted service.
- Redistribution of modified versions.
An example license: the Business Source License
The Business Source License (BSL) 1.1, as published by MariaDB, shows a common shape. Per its text, it grants the right to copy, modify, create derivative works, redistribute and make non-production use. The licensor may add an Additional Use Grant that permits limited production use. On a stated Change Date, or the fourth anniversary of the first public distribution of that version, whichever comes first, the work becomes available under a Change License, which the licensor must choose as GPL version 2.0 or later, or a license compatible with it. Until then, production use outside the grant needs a commercial license.
A worked timeline, with made-up dates: version 5 is released on 1 March 2026 under the BSL with a Change Date of 1 March 2029. A company that wants to run it in production before that date and falls outside the Additional Use Grant buys a commercial license. On 1 March 2029 version 5 becomes available under the Change License, and the production limit ends.
Source-available versus open core
Open core keeps a genuinely open-source core and sells extra proprietary features. Everything in the core is open source by the OSI’s definition. Source-available covers the whole product with a restricted license. Both can charge money; they differ in what a buyer can do with the code. Dual licensing is another route: the same code offered under an open-source license and a paid commercial license.
How Clavem handles it
License keys work under either approach. A source-available product can sell a commercial license for production use and issue a key for each purchase through Stripe, with Clavem validating it.
The limit to know is that a key check in readable code can be edited out by anyone who runs a build of their own. The legal terms, and what you do when someone ignores them, are the real enforcement, so pair a key with a clear license text (see EULA). Gate a closed module if you want a check that holds without relying on terms alone, as in open core licensing.
Questions
Is source-available the same as open source?
No. Open source has a published definition from the Open Source Initiative. A license that limits commercial use or use in a competing service fails it, even if everyone can read the code.
Can I call my project open source if I use a source-available license?
It is likely to mislead, because open source has a defined meaning. Say source-available, and link the license text.