# Source-available

> Source: https://aiwiki.ai/wiki/source_available
> Updated: 2026-11-17
> Fact-checked: 2026-11-17
> Categories: AI Ethics, AI Policy & Regulation, Open Source AI
> License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) - attribute to "AI Wiki (aiwiki.ai)"
> Cite as: AI Wiki. "Source-available." aiwiki.ai, 17 Nov 2026. https://aiwiki.ai/wiki/source_available
> From AI Wiki (https://aiwiki.ai), the free encyclopedia of artificial intelligence. Reuse freely with attribution.

**Source-available** software is software whose source code anyone can read and usually download, but under a license that withholds rights the Open Source Definition requires, most often the right to use the program commercially, to offer it as a hosted service, or to compete with the company that wrote it. The term is descriptive rather than a legal category: it covers licenses as different as MariaDB's Business Source License, MongoDB's Server Side Public License, the Elastic License, the Commons Clause and the PolyForm licenses, none of which is approved by the [Open Source Initiative](https://aiwiki.ai/wiki/open_source_initiative) (OSI).[1][2][3][4][5] Database and search companies including MongoDB, Elastic and Redis adopted such licenses between 2018 and 2024 to stop cloud providers from selling their software as a managed service, and some of them later restored an open source option.[6][7][8][9][10]

The same pattern appears in [artificial intelligence](https://aiwiki.ai/wiki/generative_ai), where the trained weights of a model take the place of source code. Many model families that are described as open, including Meta's [Llama](https://aiwiki.ai/wiki/llama) series and Google's [Gemma](https://aiwiki.ai/wiki/gemma) models before Gemma 4, are published under custom licenses that cap the size of the licensee, forbid certain uses, rule out commercial use, or, in several 2026 licenses, require a separate agreement from companies that sell model access as a service.[11][12][13][14][15] The G7's May 2026 "Vision on AI Openness Opportunities and Shared Language" gave this category its own name, "Weights Available AI", distinct from "Open Weights AI" released under an open source license.[16] The broader debate over whether such releases may be called open is covered in [open-source AI](https://aiwiki.ai/wiki/open_source_ai), [open weights](https://aiwiki.ai/wiki/open_weights) and [openwashing](https://aiwiki.ai/wiki/openwashing).

## Terminology

### Open source and free software

The OSI's Open Source Definition sets ten criteria a license must meet. Two of them rule out most source-available licenses: criterion 5, "The license must not discriminate against any person or group of persons", and criterion 6, "The license must not restrict anyone from making use of the program in a specific field of endeavor."[17] A license that forbids commercial use, bars companies above a certain size, or reserves the hosted-service market for its author fails one or both.

The [Free Software Foundation](https://aiwiki.ai/wiki/free_software_foundation) (FSF) reaches the same result from its own definition, which lists four freedoms, starting with "The freedom to run the program as you wish, for any purpose (freedom 0)."[18] The FSF states that "'Free software' does not mean 'noncommercial'" and that a program whose license excludes commercial use, development or distribution "does not qualify as free software."[18] Its list of licenses names the Commons Clause as nonfree because "it forbids selling copies of the program, and even running the program as part of implementing any commercial service."[19] Under both definitions, a license that publishes code but restricts who may use it, or for what, is neither open source nor free.

### Labels used by license authors

Companies that publish code under restrictive terms have used several labels for it. Redis called its 2024 terms "source-available licenses" and renamed its free edition "Redis Community Edition" because it no longer met the OSI definition.[8] n8n describes its own license as "fair-code", a term it coined for software that is "commercially restricted by its authors".[20] The application-monitoring company Sentry launched "Fair Source" in August 2024 for software that is publicly readable, allows use, modification and redistribution "with minimal restrictions to protect the producer's business model", and "undergoes delayed Open Source publication".[21] Zeke Gabrielse, founder of the licensing company Keygen, one of the first Fair Source adopters, argued in October 2024 that "source-available" by itself means little, writing that "It has no meaning outside of the thin freedom to read the source code."[22]

## License families

### Business Source License

The Business Source License (BSL, also abbreviated BUSL) was described by Michael "Monty" Widenius, a founder of MySQL, and Linus Nyman in a 2013 article, and was first applied in 2016 to MaxScale, a database proxy from Widenius's later company MariaDB.[5][23] It lets anyone copy, modify and redistribute the code and use it outside production; production use is allowed only as far as the licensor's optional "Additional Use Grant" permits.[24] Its distinctive feature is a time limit. On a "Change Date" chosen by the licensor, or the fourth anniversary of a version's first public release if that comes first, the code passes to a "Change License", which must be the GPL version 2.0 or later or a license compatible with it.[24][25] MaxScale 2.0.0 to 2.0.4 used version 1.0 of the license; the current version is 1.1.[25]

On August 10, 2023 HashiCorp announced that "all future releases of HashiCorp products", including Terraform, would move from the Mozilla Public License 2.0 to BSL 1.1, while its APIs, SDKs and almost all other libraries stayed under the MPL.[26][27] Because each licensor sets its own Additional Use Grant and Change Date, every BSL project is in practice a slightly different license, a point Sentry made when it introduced a replacement in 2023.[28] Red Hat lawyer Richard Fontana, quoted by LWN in 2024, called the packaging of BSL code that had passed its Change Date "'fine' in theory, but somewhat risky", because it may not be clear whether a later version mixes BSL code with code under the converted license.[5]

### Server Side Public License

MongoDB introduced the Server Side Public License (SSPL) for MongoDB Community Server versions and patch releases issued on or after October 16, 2018.[6] MongoDB says it based the SSPL on the GNU General Public License version 3, adding a new section 13 in place of the network clause of the GNU Affero General Public License: anyone who offers the program's functionality to third parties as a service must release, under the SSPL, the source of the program and of "all programs that you use to make the Program or modified version available as a service", including management, monitoring, backup, storage and hosting software.[6][8] MongoDB said that "once an open source project becomes interesting, it is too easy for large cloud vendors to capture all the value but contribute nothing back to the community."[6]

MongoDB submitted the SSPL to the OSI and withdrew it in March 2019, when its chief technology officer Eliot Horowitz wrote on the OSI's license-review list that the community consensus needed for approval did not appear to exist.[29] In January 2021 the OSI board called the SSPL a "fauxpen" license that "actually has taken away user rights", and wrote: "It's deception, plain and simple, to claim that the software has all the benefits and promises of open source when it does not."[1]

### Elastic License

Elastic announced on January 14, 2021 that, starting with version 7.11, Elasticsearch and Kibana would move from the Apache License 2.0 to a choice of the SSPL or the Elastic License, to restrict "cloud service providers from offering Elasticsearch and Kibana as a service without contributing back".[7] The rewritten Elastic License 2.0 followed on February 2, 2021.[2] It grants broad rights subject to three limitations: no providing the software "to third parties as a hosted or managed service" where the service gives access to a substantial set of its features, no circumventing license-key functionality, and no removing the licensor's notices.[30] Elastic said it was "still not claiming that either SSPL or the Elastic License are OSI-approved licenses."[2]

### Commons Clause and the Redis Source Available License

The Commons Clause is a rider drafted by the lawyer Heather Meeker that is added to an existing open source license and removes the right to "Sell" the software, defined as providing to third parties, for a fee or other consideration (including fees for hosting or consulting and support services related to the software), "a product or service whose value derives, entirely or substantially, from the functionality of the Software".[3] Its own FAQ says "it is best not to call Commons Clause software 'open source.'"[3] Redis Labs put its add-on modules, such as RediSearch and ReJSON, under Apache 2.0 with the Commons Clause in August 2018, citing cloud providers "selling (for hundreds of millions of dollars) cloud services based on open source code they didn't develop"; core Redis stayed under the BSD license at that time.[31]

On March 20, 2024 Redis announced that Redis 7.4 and later would be dual-licensed under the Redis Source Available License version 2 (RSALv2) and the SSPL, ending BSD licensing of the core. The modules had already moved from the Commons Clause to a first Redis Source Available License (RSAL) on February 21, 2019, after Redis said the clause had caused confusion and that its restrictions on "support" worked against its intentions.[67] Under RSALv2 a licensee may not "Commercialize the software or provide it to others as a managed service" or remove notices.[8] Redis's FAQ stated: "we openly acknowledge that this change means Redis is no longer open source under the OSI definition."[8]

### Functional Source License and fair source

Sentry published the Functional Source License (FSL) on November 17, 2023, describing it as "an evolution of BSL".[28] It allows any use other than a "Competing Use", defined as use "in or for a commercial product or service that competes with the Software or any other product or service we offer using the Software", and has fixed terms instead of BSL's variables: each version converts after two years to the Apache License 2.0 or the MIT License, depending on the variant (FSL-1.1-ALv2 or FSL-1.1-MIT).[28][32] The Fair Source launch on August 6, 2024 grouped the FSL with Keygen's Fair Core License and MariaDB's BSL, and named Codecov, CodeCrafters, GitButler, Keygen and PowerSync as formerly closed-source products now shared on these terms.[21]

### Sustainable Use License

n8n, a workflow-automation tool, replaced its earlier arrangement of Apache 2.0 with the Commons Clause with the Sustainable Use License on March 17, 2022.[20] The license permits use, modification, derivative works and redistribution with three limitations: the software may be used or modified "only for your own internal business purposes or for non-commercial or personal use", may be distributed only "free of charge for non-commercial purposes", and its notices may not be removed.[33][20] n8n says the change removed the Commons Clause's restriction on consulting and support services, and that "we do not call ourselves open source"; it invites other projects to reuse the license.[20]

### PolyForm licenses

The PolyForm Project, a group of licensing lawyers and technologists, published version 1.0.0 of a set of standardized source-code licenses on May 24, 2020.[34] The set includes PolyForm Noncommercial, Small Business, Free Trial, Internal Use, Perimeter (uses other than those that compete with the software), Shield (uses other than those that compete with the provider) and Strict (noncommercial use only, with no right to distribute or modify).[35] The Small Business license permits use by a company with fewer than 100 workers and less than 1,000,000 US dollars (2019) of revenue in the prior tax year.[36] The project says plainly that PolyForm is not "Open source or free software".[4]

## Comparison of licenses

The table lists the main source-available software licenses and the model licenses discussed below. "Converts" means the license itself turns each version into an open source license after a fixed period.

| License | Year | Steward | Main restriction | Converts to open source? |
|---|---|---|---|---|
| Business Source License (first used 2016; current version 1.1) | 2016 | MariaDB | Production use only as the Additional Use Grant allows [24] | Yes, at the Change Date, at most 4 years, to GPLv2 or later or a compatible license [24] |
| Server Side Public License | 2018 | MongoDB | Offering it as a service requires releasing the whole service stack under the SSPL [6] | No |
| Commons Clause | 2018 | Heather Meeker (drafter) | No selling products or services whose value derives from the software [3] | No |
| PolyForm licenses (version 1.0.0 onward) | 2020 | PolyForm Project | Varies: noncommercial, small business, non-compete and others [35] | No; a separate PolyForm Countdown license can schedule a later change of terms [35] |
| Elastic License 2.0 | 2021 | Elastic | No hosted or managed service; no license-key circumvention [30] | No |
| Sustainable Use License | 2022 | n8n | Internal business, non-commercial or personal use only [33] | No |
| Functional Source License | 2023 | Sentry | No Competing Use [28] | Yes, after 2 years, to Apache 2.0 or MIT [32] |
| Redis Source Available License 2.0 (for Redis core) | 2024 | Redis | No commercializing or managed service [8] | No |
| [Llama 2](https://aiwiki.ai/wiki/llama_2) Community License | 2023 | [Meta](https://aiwiki.ai/wiki/meta_ai) | 700 million MAU cap; acceptable use policy [11] | No |
| Gemma Terms of Use | 2024 | [Google](https://aiwiki.ai/wiki/google) | Prohibited Use Policy passed to every derivative [12] | No |
| Mistral AI Non-Production License | 2024 | [Mistral AI](https://aiwiki.ai/wiki/mistral_ai) | Testing, research, personal or evaluation use only [13] | No |
| FLUX.1 [dev] Non-Commercial License | 2024 | [Black Forest Labs](https://aiwiki.ai/wiki/black_forest_labs) | Non-commercial, non-production use only [37] | No |
| Stability AI Community License | 2024 | [Stability AI](https://aiwiki.ai/wiki/stability_ai) | Separate license above 1 million US dollars annual revenue [38] | No |
| Reka Edge 2603 License (BSL 1.1) | 2026 | [Reka AI](https://aiwiki.ai/wiki/reka_ai) | Production use only below 1 million US dollars revenue; no hosted API [39] | Yes, after 2 years, to Apache 2.0 [39] |
| [Qwen3.8-Max](https://aiwiki.ai/wiki/qwen3_8_max) License | 2026 | Alibaba [Qwen](https://aiwiki.ai/wiki/qwen) | Separate license for Model-as-a-Service and AI work assistant businesses above 50 million US dollars revenue [14] | No |
| [GLM-5.3](https://aiwiki.ai/wiki/glm_5_3) License | 2026 | [Z.ai](https://aiwiki.ai/wiki/z_ai) | Security review for Model-as-a-Service operators above 10 billion US dollars revenue [40] | No |
| Mistral Ecosystem Open-Weight License | 2026 | Mistral AI | Separate commercial license for any Model-as-a-Service business [15] | No |

## Relicensing and forks

When an established open source project changes its license, versions released before the change keep their old terms, and several relicensed projects were forked from those versions.[8]

| Date | Event |
|---|---|
| April 12, 2021 | Amazon Web Services announces OpenSearch, an Apache 2.0 fork of Elasticsearch and Kibana 7.10.2, after Elastic's license change [41] |
| August 10, 2023 | HashiCorp moves future releases of its products, including Terraform, to BSL 1.1 [26] |
| September 20, 2023 | The [Linux Foundation](https://aiwiki.ai/wiki/linux_foundation) announces OpenTofu (first named OpenTF), an open source successor to the MPL-licensed Terraform, with pledges from more than 140 organizations [27] |
| March 20, 2024 | Redis 7.4 and later move from BSD to RSALv2 or SSPL [8] |
| March 28, 2024 | The Linux Foundation announces Valkey, a BSD-licensed fork of Redis 7.2.4 backed by AWS, Google Cloud, Oracle, Ericsson and Snap [42] |
| August 29, 2024 | Elastic announces that it will add the AGPL as a third license option for Elasticsearch and Kibana; the AGPL was added to the Elasticsearch code in September 2024 [9] |
| May 1, 2025 | Redis adds the AGPLv3 as an option starting with Redis 8 [10] |

Elastic's founder Shay Banon wrote in 2024 that the company had changed its license in 2021 because "We had issues with AWS and the market confusion their offering was causing", and that it was "adding another option, and not removing anything".[9] Redis chief executive Rowan Trollope wrote in 2025 that the move to the SSPL had achieved its goal, since "AWS and Google now maintain their own fork", but that "the change hurt our relationship with the Redis community".[10]

## In artificial intelligence

### Weights in place of source code

For a [machine learning](https://aiwiki.ai/wiki/machine_learning) model, the usual counterpart of downloadable source code is the trained parameters, or [weights](https://aiwiki.ai/wiki/weight), together with code to run them; the two lower tiers of the G7 typology described below are defined by the terms on exactly these two components. The OSI's [Open Source AI Definition](https://aiwiki.ai/wiki/open_source_ai_definition) (version 1.0) treats the weights as only one of three parts of the "preferred form of making modifications", alongside "The complete source code used to train and run the system" and detailed information about the training data, and it requires freedom to "Use the system for any purpose and without having to ask for permission."[43] A model release can therefore fall short of open source in two ways: by withholding training code and data while licensing the weights openly, or by publishing the weights under terms that restrict use. Source-available licensing describes the second.

Except for Reka's use of the BSL, the model licenses below are custom texts written by each developer, and they fall into a few groups. The [open-weight license comparison](https://aiwiki.ai/wiki/open_weight_license_comparison) article sets out the commercial terms of the most used ones model by model, and the [list of open-weight models](https://aiwiki.ai/wiki/list_of_open_weight_models) records the license of each release.

### Scale caps and use restrictions

The Llama 2 Community License, dated July 18, 2023, let anyone use, modify and redistribute the model, but required any licensee whose products had more than 700 million monthly active users on the release date to "request a license from Meta, which Meta may grant to you in its sole discretion". It also incorporated an acceptable use policy and barred using the model or its outputs "to improve any other large language model".[11] The OSI's executive director Stefano Maffulli wrote two days later that Meta was confusing open source with "resources available to some users under some conditions".[44] Later Llama licenses kept the threshold; the [Llama 4](https://aiwiki.ai/wiki/llama_4) Community License uses the same 700 million figure.[45] The FSF lists the [Llama 3.1](https://aiwiki.ai/wiki/llama_3_1) Community License and its acceptable use policy as nonfree, objecting both to the policy's list of prohibited uses and to the clause on very widely used licensees: "A free software license may not arbitrarily deny use of the program to anyone."[19]

Google released [Gemma](https://aiwiki.ai/wiki/gemma) on February 21, 2024 as "open models" whose terms of use "permit responsible commercial usage and distribution for all organizations, regardless of size".[46] The Gemma Terms of Use have no size cap, but anyone who distributes Gemma or a derivative must include its use restrictions "as an enforceable provision in any agreement", and Google "reserves the right to restrict (remotely or otherwise) usage" that it reasonably believes violates the terms.[12] The terms page, last modified April 1, 2026, points users of [Gemma 4](https://aiwiki.ai/wiki/gemma_4) to a separate license; Google's documentation lists the Apache License 2.0 as the Gemma 4 license.[12][47]

[OpenRAIL](https://aiwiki.ai/wiki/openrail) licenses are a related case: they permit reuse, distribution and adaptation but forbid listed uses of the licensed model, and the Responsible AI Licenses initiative that publishes them states that "THESE ARE NOT OPEN SOURCE LICENSES, based on the definition used by Open Source Initiative".[48]

### Non-commercial and non-production licenses

A second group allows experimentation but not business use. Mistral AI introduced the Mistral AI Non-Production License on May 29, 2024 with its code model [Codestral](https://aiwiki.ai/wiki/codestral). The license limits use to "testing, research, Personal, or evaluation purposes in Non-Production Environments" and forbids supplying the model in a commercial activity, including "through a hosted or managed service".[13] Mistral said at the time that it would keep releasing other models under Apache 2.0 and that the new license "strikes the right balance between our commitment to openness principles and our responsibility to grow our business".[49] Black Forest Labs released the weights of [FLUX.1](https://aiwiki.ai/wiki/flux_1) [dev] under a FLUX.1 [dev] Non-Commercial License, which allows use, derivatives and distribution "solely for your Non-Commercial Purposes"; the license claims no ownership of generated images and lets users use outputs for any purpose, including commercial ones, except to train a competing model.[37]

Some licenses draw the line by revenue. Stability AI moved its recent models, including [Stable Diffusion 3](https://aiwiki.ai/wiki/stable_diffusion_3) Medium, to a Community License in July 2024, saying the commercial license first attached to SD3 had "caused some confusion and concern"; the community site Civitai had banned SD3-based content over the original terms.[50][51] The Community License is free for research, non-commercial use and commercial use by people and organizations with annual revenue below 1 million US dollars; above that, the license terminates and the user must request a license from Stability AI, which may grant it at its discretion.[50][38]

### Licenses aimed at model-as-a-service operators

In 2026 several developers of large open-weight models adopted short licenses that start from the permission text of the MIT License and add a condition aimed at companies that sell access to the model. Like the SSPL, the Elastic License and the RSALv2 in software, they single out businesses that offer the work to others as a service rather than end users or small companies.

| Model and license | Released | Condition on hosting businesses |
|---|---|---|
| [Qwen3.8-Max](https://aiwiki.ai/wiki/qwen3_8_max), Qwen3.8-Max License | August 2026 [52] | A licensee that runs a "Model as a Service or AI Work Assistant business" with group revenue above 50 million US dollars in any 12 months needs a separate license before commercial use; products with more than 100 million monthly active users or 20 million US dollars monthly revenue must display the model name [14] |
| [GLM-5.3](https://aiwiki.ai/wiki/glm_5_3), GLM-5.3 License | August 2026 [53] | A model-as-a-service operator with group revenue above 10 billion US dollars over 12 months "must pass Z.AI's security review" before commercial use [40] |
| [Mistral Large 4](https://aiwiki.ai/wiki/mistral_large_4), Mistral Ecosystem Open-Weight License | October 2026 [54] | Any licensee whose group "operates a Model as a Service business" needs a separate commercial license from Mistral, whatever its size [15] |

A simpler revenue gate preceded them: the "Modified MIT License" that Mistral used for Devstral 2 in December 2025 copies the MIT grant but withholds all rights from a company whose "global consolidated monthly revenue" exceeded 20 million US dollars in the preceding month, pointing such companies to a commercial license or to Mistral's hosted services.[66]

The three licenses define model as a service in similar words, as giving a third party access to inference or fine-tuning in a manner that allows that party "to exercise meaningful control over the inputs, parameters, or training data", and all three exclude the mere relaying of requests to models hosted by others.[14][40][15] The Qwen3.8-Max and Mistral licenses also exempt internal use that does not make the model available to third parties, and the GLM-5.3 and Mistral licenses exempt end-user products in which the model is only embedded within specific features.[40][15] Mistral's announcement calls the model "free to use, modify, fine-tune, and commercialize, with a single condition".[54]

### Delayed open source for models

The Business Source License model has also been applied to weights. [Reka AI](https://aiwiki.ai/wiki/reka_ai) published the [Reka Edge](https://aiwiki.ai/wiki/reka_edge) 2603 vision-language model on [Hugging Face](https://aiwiki.ai/wiki/hugging_face) in March 2026 under a license headed "Business Source License 1.1" that covers the weights, inference code, tokenizer and related tools.[39][55] Its Additional Use Grant allows research and evaluation and lets for-profit companies with less than 1,000,000 US dollars in annual gross revenue use it in production; larger companies, and government, public-sector and academic bodies, need a commercial license for any production deployment. Without a commercial license, licensees may not offer the model as a hosted API or model-as-a-service platform or use it or its outputs to develop competing foundation models for commercial purposes.[39] The Change Date is two years after public release, when the work "will automatically become available under" the Apache License 2.0.[39] Reka's two-year period is the same as the FSL's and shorter than the four-year maximum of MariaDB's BSL.[39][24][32]

### "Weights Available AI" in the G7 typology

On May 29, 2026 the G7 digital and technology ministers approved a non-binding "Vision on AI Openness Opportunities and Shared Language", for which the OSI acted as a knowledge partner.[16][56] It treats openness as "a spectrum" and defines four tiers. "Open Weights AI" is AI released free of charge "along with its weights and deployment code, under an Open Source License", and "Weights Available AI" is AI released free of charge with its weights and deployment code "under a license which includes restrictions on how they can be used, such as commercial, geographical, or use-case restrictions."[16] The document names avoiding "open washing" among the purposes of a shared vocabulary.[16] Weights Available AI corresponds roughly to the source-available category in software, although the G7 document does not draw that comparison; the [Open Source AI Definition](https://aiwiki.ai/wiki/open_source_ai_definition) article describes the two higher tiers.

Applying the typology in June 2026, Stephen O'Grady of the analyst firm RedMonk found that of 40 openly released models in his sample, about half were Weights Available AI (non-OSI licenses) and half Open Weights AI (OSI licenses), and none met either open source tier.[57]

### Legal consequences in the European Union

The distinction matters for the [EU AI Act](https://aiwiki.ai/wiki/eu_ai_act), which relieves providers of general-purpose AI models released under a "free and open-source licence" of some obligations, though not for models classified as having systemic risk.[58] The European Commission's guidelines of July 2025 list restrictions that disqualify a license: "limitations to non-commercial or research-only use", prohibitions on distribution, "usage restrictions triggered by user scale thresholds", and "requirements to obtain separate commercial licences for specific use cases".[58] These examples correspond to several of the model terms described above: non-commercial licenses, the Llama user threshold, and separate commercial licenses required of model-as-a-service businesses. The guidelines do accept "specific, safety-oriented terms that reasonably restrict usage" where use would pose a significant risk to public safety, security or fundamental rights, if the restrictions are proportionate and non-discriminatory.[58]

### AI developer tools

Source-available terms also appear in the software around models. The local chat application [Jan](https://aiwiki.ai/wiki/jan_ai) carried a license titled "Sustainable Use License", the same name as n8n's, in its first `LICENSE` file, committed on September 6, 2023; it limited use to internal business, non-commercial or personal purposes. The project switched to the GNU GPL v3 on October 15, 2023 and to the GNU AGPL v3 ten days later, and its code has been under the Apache License 2.0 since May 20, 2025.[59][60][61][62] [Open WebUI](https://aiwiki.ai/wiki/open_webui), a self-hosted web interface for models, adopted the "Open WebUI License" with version 0.6.6 on April 19, 2025: it is based on BSD-3-Clause but requires deployments to keep the Open WebUI branding unless they have 50 or fewer users in any 30-day period, are substantive contributors with written permission, or hold an enterprise license. Its documentation states that "Open WebUI v0.6.6+ is not an OSI-approved 'open source' license" while noting that all source code is public.[63] [n8n](https://aiwiki.ai/wiki/n8n), whose Sustainable Use License is described above, includes an AI Agent node for building agent workflows, so the same terms apply to AI applications built on it.[64][20]

## Arguments for and against

Supporters present source-available licenses as a way to keep code public while funding its development. Widenius argued when MaxScale moved to the BSL that the support-services model of open source companies does not scale, saying "the companies that don't have licenses, they can almost never make a product."[23] MongoDB said that large cloud vendors could "capture all the value but contribute nothing back to the community" and that its license was meant to make sure such companies were "giving back".[6] Sentry described the FSL as a way to "grant freedom without harmful free-riding" and argued that a fixed two-year delay was a better bargain than BSL's four years.[28] n8n said its goals were "To be as permissive as possible" while "Safeguarding our ability to build a business".[20] The Fair Source launch post argued that delayed open source publication lets others continue a project if the original company shuts down.[21] In AI, Mistral said its non-production license was meant to ensure "that those who build a business based on our work do so in a fair and sustainable way for all parties", and Reka's license says its purpose is research, development, evaluation and internal use "while restricting certain commercial uses for a limited period of time".[49][39]

Critics object on several grounds. The OSI calls it deceptive to describe such software as open source and holds that use restrictions remove rights the Open Source Definition protects.[1][44] The FSF objects to the restrictions themselves; of the Llama 3.1 acceptable use policy it wrote that there is "a crucial difference between prohibitions enacted by democratically controlled governments in the law and a private company dictating what we are allowed to do in our lives."[19] Relicensing has also prompted forks backed by large companies and foundations, such as OpenSearch, OpenTofu and Valkey, and Redis and Elastic later restored an OSI-approved option.[41][27][42][9][10] Practical costs have also been raised: Sentry noted that each BSL project sets its own terms, which makes compliance review harder, and Linux distribution maintainers discussed in 2024 how to tell whether maintained BSL code had passed its Change Date.[28][5] For model licenses, the OSI's Jordan Maris wrote in February 2025 that the Llama 3.x licenses fail "freedom 0, the freedom to use the model for any purpose" and accused Meta of "open washing".[65]

The OSI's 2023 statement on Llama 2 objected to the label rather than to the release itself. Its 2023 statement on Llama 2 said "OSI is pleased to see that Meta is lowering barriers for access to powerful AI systems" and that it did not question Meta's desire to limit the use of Llama for competitive purposes, only the use of the term open source.[44] The G7 document likewise asks that openness claims state which components are released and "whether with or without restrictions", rather than using "open" without qualification.[16]

## See also

- [Open-source AI](https://aiwiki.ai/wiki/open_source_ai)
- [Open weights](https://aiwiki.ai/wiki/open_weights)
- [Open Source AI Definition](https://aiwiki.ai/wiki/open_source_ai_definition)
- [Open Source Initiative](https://aiwiki.ai/wiki/open_source_initiative)
- [Openwashing](https://aiwiki.ai/wiki/openwashing)
- [OpenRAIL](https://aiwiki.ai/wiki/openrail)
- [Open-Weight LLM License Comparison](https://aiwiki.ai/wiki/open_weight_license_comparison)
- [Apache License 2.0](https://aiwiki.ai/wiki/apache_license)
- [MIT License](https://aiwiki.ai/wiki/mit_license)
- [List of open-weight models](https://aiwiki.ai/wiki/list_of_open_weight_models)

## References

1. Open Source Initiative Board of Directors. "The SSPL is Not an Open Source License". Open Source Initiative, January 19, 2021. https://opensource.org/blog/the-sspl-is-not-an-open-source-license
2. Shay Banon. "Introducing Elastic License v2, simplified and more permissive; SSPL remains an option". Elastic blog, February 2, 2021. https://www.elastic.co/blog/elastic-license-v2
3. Commons Clause. "Commons Clause License Condition v1.0" and FAQ. commonsclause.com. Accessed November 17, 2026. https://commonsclause.com/
4. PolyForm Project. "What is PolyForm?". polyformproject.org. Accessed November 17, 2026. https://polyformproject.org/about
5. Joe Brockmeier. "The complexity of BUSL transformation". LWN.net, August 5, 2024. https://lwn.net/Articles/984249/
6. MongoDB. "Server Side Public License FAQ". MongoDB, accessed November 17, 2026. https://www.mongodb.com/legal/licensing/server-side-public-license/faq
7. Shay Banon. "Upcoming licensing changes to Elasticsearch and Kibana". Elastic blog, January 14, 2021. https://www.elastic.co/blog/licensing-change
8. Redis. "Redis Adopts Dual Source-Available Licensing". Redis blog, March 20, 2024. https://redis.io/blog/redis-adopts-dual-source-available-licensing/
9. Shay Banon. "Elasticsearch is Open Source. Again!". Elastic blog, August 29, 2024. https://www.elastic.co/blog/elasticsearch-is-open-source-again
10. Rowan Trollope. "Redis is now available under the AGPLv3 open source license". Redis blog, May 1, 2025. https://redis.io/blog/agplv3/
11. Meta. "Llama 2 Community License Agreement" (version release date July 18, 2023). GitHub, meta-llama/llama. https://github.com/meta-llama/llama/blob/main/LICENSE
12. Google. "Gemma Terms of Use" (last modified April 1, 2026). gemma.ai (formerly ai.google.dev/gemma/terms). https://gemma.ai/resources/terms/
13. Mistral AI. "Mistral AI Non-Production License" (MNPL-0.1). Mistral AI. Accessed November 17, 2026. https://mistral.ai/licences/MNPL-0.1.md
14. Qwen. "Qwen3.8-Max License". Hugging Face, Qwen/Qwen3.8-2.4T-A95B. Accessed November 17, 2026. https://huggingface.co/Qwen/Qwen3.8-2.4T-A95B/blob/main/LICENSE
15. Mistral AI. "Mistral Ecosystem Open-Weight License". Hugging Face, mistralai/Mistral-Large-4-1T-A52B. Accessed November 17, 2026. https://huggingface.co/mistralai/Mistral-Large-4-1T-A52B/blob/main/LICENSE
16. G7 Digital and Technology Ministers. "G7 Vision on AI Openness Opportunities and Shared Language". Paris, May 29, 2026. G7 Information Centre, University of Toronto. https://www.g7.utoronto.ca/ict/260529-vision.html
17. Open Source Initiative. "The Open Source Definition" (version 1.9, last modified March 22, 2007). Open Source Initiative. Accessed November 17, 2026. https://opensource.org/osd
18. Free Software Foundation. "What is Free Software?". GNU Project. Accessed November 17, 2026. https://www.gnu.org/philosophy/free-sw.html
19. Free Software Foundation. "Various Licenses and Comments about Them" (entries "Commons Clause" and "Llama 3.1 Community License Agreement and Llama 3.1 Acceptable Use Policy"). GNU Project. Accessed November 17, 2026. https://www.gnu.org/licenses/license-list.html
20. n8n. "Community license" (Sustainable Use License FAQ). n8n Docs. Accessed November 17, 2026. https://docs.n8n.io/n8n-community-license/community-license.md
21. Chad Whitacre. "Sentry is now Fair Source". Sentry blog, August 6, 2024. https://blog.sentry.io/sentry-is-now-fair-source/
22. Zeke Gabrielse. "Source-available is meaningless". Keygen blog, October 2, 2024. https://keygen.sh/blog/source-available-is-meaningless/
23. Frederic Lardinois. "MySQL founder tries a new software licensing model". TechCrunch, August 19, 2016. https://techcrunch.com/2016/08/19/mysql-founder-tries-a-new-software-licensing-model/
24. MariaDB. "Business Source License 1.1". MariaDB. Accessed November 17, 2026. https://mariadb.com/bsl11/
25. MariaDB. "Business Source License (BSL) Frequently Asked Questions". MariaDB. Accessed November 17, 2026. https://mariadb.com/bsl-faq-mariadb/
26. Armon Dadgar. "HashiCorp adopts Business Source License". HashiCorp blog, August 10, 2023. https://www.hashicorp.com/en/blog/hashicorp-adopts-business-source-license
27. Linux Foundation. "Linux Foundation Launches OpenTofu: A New Open Source Alternative to Terraform". Linux Foundation press release, September 20, 2023. https://www.linuxfoundation.org/press/announcing-opentofu
28. Chad Whitacre. "Introducing the Functional Source License: Freedom without Free-riding". Sentry blog, November 17, 2023. https://blog.sentry.io/introducing-the-functional-source-license-freedom-without-free-riding/
29. Eliot Horowitz. "[License-review] Approval: Server Side Public License, Version 2 (SSPL v2)". OSI license-review mailing list, March 2019. https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2019-March/003989.html
30. Elastic. "Elastic License 2.0". Elastic. Accessed November 17, 2026. https://www.elastic.co/licensing/elastic-license
31. Redis. "Redis' License is BSD and will remain BSD". Redis blog, August 22, 2018. https://redis.io/blog/redis-license-bsd-will-remain-bsd/
32. Functional Source License. "FSL: Functional Source License". fsl.software. Accessed November 17, 2026. https://fsl.software/
33. n8n. "Sustainable Use License" (LICENSE.md). GitHub, n8n-io/n8n. Accessed November 17, 2026. https://github.com/n8n-io/n8n/blob/master/LICENSE.md
34. PolyForm Project. "Announcing Version 1.0.0 of the PolyForm Licenses". polyformproject.org, May 24, 2020. https://polyformproject.org/announcements
35. PolyForm Project. "Licenses". polyformproject.org. Accessed November 17, 2026. https://polyformproject.org/licenses
36. PolyForm Project. "PolyForm Small Business License 1.0.0". polyformproject.org. https://polyformproject.org/licenses/small-business/1.0.0
37. Black Forest Labs. "FLUX.1 [dev] Non-Commercial License v1.1.1". GitHub, black-forest-labs/flux. Accessed November 17, 2026. https://github.com/black-forest-labs/flux/blob/main/model_licenses/LICENSE-FLUX1-dev
38. Stability AI. "Stability AI Community License Agreement". Stability AI. Accessed November 17, 2026. https://stability.ai/community-license-agreement
39. Reka AI. "Reka Edge 2603: License" (Business Source License 1.1). Hugging Face, RekaAI/reka-edge-2603. Accessed November 17, 2026. https://huggingface.co/RekaAI/reka-edge-2603/blob/main/LICENSE
40. Z.ai. "GLM-5.3 License". Hugging Face, zai-org/GLM-5.3. Accessed November 17, 2026. https://huggingface.co/zai-org/GLM-5.3/blob/main/LICENSE
41. Amazon Web Services. "Introducing OpenSearch". AWS Open Source Blog, April 12, 2021. https://aws.amazon.com/blogs/opensource/introducing-opensearch/
42. Linux Foundation. "Linux Foundation Launches Open Source Valkey Community". Linux Foundation press release, March 28, 2024. https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community
43. Open Source Initiative. "The Open Source AI Definition 1.0". Open Source Initiative. Accessed November 17, 2026. https://opensource.org/ai/open-source-ai-definition
44. Stefano Maffulli. "Meta's LLaMa 2 license is not Open Source". Open Source Initiative, July 20, 2023. https://opensource.org/blog/metas-llama-2-license-is-not-open-source
45. Meta. "Llama 4 Community License Agreement". GitHub, meta-llama/llama-models. Accessed November 17, 2026. https://github.com/meta-llama/llama-models/blob/main/models/llama4/LICENSE
46. Jeanine Banks and Tris Warkentin. "Gemma: Introducing new state-of-the-art open models". Google blog, February 21, 2024. https://blog.google/technology/developers/gemma-open-models/
47. Google. "Apache License 2.0" (linked as the Gemma 4 license). Gemma documentation. Accessed November 17, 2026. https://gemma.ai/resources/apache-2/
48. Responsible AI Licenses (RAIL). "FAQ". licenses.ai. Accessed November 17, 2026. https://licenses.ai/faq-2
49. Mistral AI. "Mistral AI Non-Production License (MNPL)". Mistral AI news, May 29, 2024. https://mistral.ai/news/mistral-ai-non-production-license-mnpl
50. Stability AI. "Community License" (license update). Stability AI news, July 5, 2024. https://stability.ai/news-updates/license-update
51. Decrypt. "Stable Diffusion 3 License Revamped Amid Blowback, Promising Better Model". Decrypt, July 8, 2024. https://decrypt.co/238871/stable-diffusion-3-license-revamped-amid-blowback
52. Qwen. "Qwen3.8-2.4T-A95B" model repository (license: qwen3.8-max). Hugging Face. Accessed November 17, 2026. https://huggingface.co/Qwen/Qwen3.8-2.4T-A95B
53. Z.ai. "GLM-5.3" model repository (license: glm-5.3). Hugging Face. Accessed November 17, 2026. https://huggingface.co/zai-org/GLM-5.3
54. Mistral AI. "Mistral Large 4 (Le Chonk) is now open weight". Mistral AI news, October 2026. https://mistral.ai/news/mistral-large-4-oss/
55. Reka AI. "reka-edge-2603" model repository. Hugging Face, created March 11, 2026. https://huggingface.co/RekaAI/reka-edge-2603
56. Jordan Maris. "Open Source Initiative Helps G7 Deliver Vision On AI Openness". Open Source Initiative, June 1, 2026. https://opensource.org/blog/open-source-initiative-helps-g7-deliver-vision-on-ai-openness
57. Stephen O'Grady. "The G7 on Open Source vs Open Weights". RedMonk tecosystems, June 2, 2026. https://redmonk.com/sogrady/2026/06/02/g7-open-weights/
58. European Commission. "Guidelines on the scope of the obligations for general-purpose AI models established by Regulation (EU) 2024/1689 (AI Act)", section 4.2.1. July 18, 2025. https://digital-strategy.ec.europa.eu/en/library/guidelines-scope-obligations-providers-general-purpose-ai-models-under-ai-act
59. Jan. Commit 5c1b0c2, "license" (first LICENSE file, "Sustainable Use License"). GitHub, janhq/jan, September 6, 2023. https://github.com/janhq/jan/commit/5c1b0c2e2ecd5e402f056decf7e8a56b61300a77
60. Jan. Commit 8860734, "Change License and update README". GitHub, janhq/jan, October 15, 2023. https://github.com/janhq/jan/commit/88607345c386062b2137bb2c98e08de5627175d8
61. Jan. Commit ec612fc, "Change license to AGPL". GitHub, janhq/jan, October 25, 2023. https://github.com/janhq/jan/commit/ec612fc583c01a08a46e6bb049cbda97fa421f02
62. Jan. Commit e8ca7f3, "chore: Jan's code is now under the Apache license (#5042)". GitHub, janhq/jan, May 20, 2025. https://github.com/janhq/jan/commit/e8ca7f3c1bc5eee962b49ee46982e83e217ed928
63. Open WebUI. "Open WebUI License". Open WebUI documentation. Accessed November 17, 2026. https://docs.openwebui.com/license/
64. n8n. "AI Agent node". n8n Docs. Accessed November 17, 2026. https://docs.n8n.io/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.agent/
65. Jordan Maris. "Meta's LLaMa license is still not Open Source". Open Source Initiative, February 18, 2025. https://opensource.org/blog/metas-llama-license-is-still-not-open-source
66. Mistral AI. "Modified MIT License" (LICENSE). Hugging Face, mistralai/Devstral-2-123B-Instruct-2512. Accessed November 17, 2026. https://huggingface.co/mistralai/Devstral-2-123B-Instruct-2512/blob/main/LICENSE
67. Redis. "Redis Labs' Modules License Changes". Redis blog, February 21, 2019. https://redis.io/blog/redis-labs-modules-license-changes/

