Each sheet says what is allowed, what is required, the main pitfall and where to read the official text. The SPDX identifier is the standard short name of the licence.
Public domain: CC0 and Unlicense
Public domainCC0-1.0 · UnlicenseTo be confirmed at the source
✔ You can
Everything: copy, modify, sell, embed, with no conditions and no need to credit the author.
✖ You cannot
Nothing is forbidden.
⚠ You must
Nothing. The licence text mainly makes the waiver of rights clear and valid.
- Watch out
- A file described as “public domain” without a formal text leaves legal uncertainty, because public domain does not work the same way everywhere. Ask for the exact text. CC0's status with the OSI is to be confirmed on the official list.
- Example
- Public datasets, or small tools whose author wants sharing with no conditions at all.
- Official texts
MIT licence
PermissiveMITGuide of 2026-10-13
✔ You can
Use, copy, modify, merge, publish, distribute and even sell the software, including inside a closed product.
✖ You cannot
Remove the author's notice, or claim you wrote the code.
⚠ You must
Keep the copyright notice and the licence text with the code.
- Watch out
- No explicit patent clause, and the software is provided “as is,” without warranty. Copying MIT code without keeping the notice is a common violation.
- Example
- The React library and a large part of the JavaScript tooling.
- Official texts
BSD licences (2 and 3 clauses)
PermissiveBSD-2-Clause · BSD-3-ClauseGuide of 2026-10-13
✔ You can
Like MIT: use, modify and distribute, including in a commercial or closed product.
✖ You cannot
Remove the notice, or use the authors' names to promote your product (3-clause version).
⚠ You must
Keep the notice. The 3-clause version also forbids using the authors' names to promote a derived product.
- Watch out
- The old 4-clause version (with an advertising clause) is best avoided: check the number of clauses.
- Example
- FreeBSD is released under BSD-2-Clause.
- Official texts
Apache License 2.0
PermissiveApache-2.0Checked at the source · 2026-11-08
✔ You can
Commercial use, modification, distribution. It also grants a licence to contributors' patents.
✖ You cannot
Use the author's trademark, or remove the notice and the NOTICE file.
⚠ You must
Keep the notice and the NOTICE file if there is one, and mark modified files. The patent licence ends for anyone who sues over a patent covering this software.
- Watch out
- Compatible with GPL-3.0, but not with GPL-2.0 alone (according to the FSF). It gives no rights over the trademark.
- Example
- The Apache HTTP Server and, since April 2026, Google's Gemma 4 models.
- Official texts
The short cousins: ISC, zlib, Boost, PostgreSQL
PermissiveISC · Zlib · BSL-1.0 · PostgreSQLTo be confirmed at the source
✔ You can
Same spirit as MIT: free use, including commercial.
✖ You cannot
Remove the copyright notice.
⚠ You must
A copyright notice (ISC, PostgreSQL); do not claim you wrote the original and mark modified versions (zlib). Boost requires no notice in distributed compiled code.
- Watch out
- The differences are small but real: read the short text rather than assume “it's like MIT.”
- Example
- PostgreSQL, the database, has its own licence of this kind.
- Official texts
GNU LGPL 2.1 and 3.0
Weak copyleftLGPL-2.1 · LGPL-3.0Guide of 2026-10-13
✔ You can
Use the library in closed software, as long as you link to it without mixing it into your own code.
✖ You cannot
Merge the library into your code without letting the user replace it.
⚠ You must
Share changes made to the library itself, let the user replace it with another version, keep the notices.
- Watch out
- Static linking (the library is copied into your program) brings more conditions than dynamic linking. LGPL-3.0 adds requirements for consumer devices.
- Example
- The Qt framework is offered under LGPL-3.0, or under a commercial licence.
- Official texts
Mozilla Public License 2.0
Weak copyleftMPL-2.0Checked at the source · 2026-11-08
✔ You can
Use, modify and distribute, including in a product that contains code under other licences, even closed ones.
✖ You cannot
Close the source of MPL files you modify.
⚠ You must
MPL files you modify stay under MPL, with their source. Keep the notices.
- Watch out
- The copyleft stops at the file boundary, not the program's. Compatible with the GPL, unless the author added the “incompatible with secondary licenses” notice.
- Example
- Firefox.
- Official texts
Eclipse Public License 2.0 and CDDL 1.0
Weak copyleftEPL-2.0 · CDDL-1.0Checked at the source · 2026-11-08
✔ You can
Use and distribute, including in commercial products, combined with code under other licences.
✖ You cannot
Close the source of files or modules you modify.
⚠ You must
Keep modified files or modules under the same licence and make their source available. Keep the notices.
- Watch out
- These licences do not mix with the GPL. EPL-2.0 may provide a compatible “secondary licence” if the author wrote one: check project by project.
- Example
- Java projects of the Eclipse foundation (EPL).
- Official texts
Quebec free licences (LiLiQ)
Weak copyleftLiLiQ-P-1.1 · LiLiQ-R-1.1 · LiLiQ-R+-1.1To be confirmed at the source
✔ You can
Use, modify and distribute, at three levels: permissive (P), reciprocity (R) and strong reciprocity (R+).
✖ You cannot
Close the source of covered parts (levels R and R+). To be confirmed in the version's text.
⚠ You must
P: keep the notices. R: share changes to the covered parts. R+: share the whole derived work. To be confirmed in the text of each version.
- Watch out
- The texts exist in French, which helps for a Quebec project. Check the version (1.1) and compatibility with the other licences you use.
- Example
- Software published by Quebec public bodies.
- Official texts
GNU GPL 2.0 and 3.0
Strong copyleftGPL-2.0 · GPL-3.0Checked at the source · 2026-11-08
✔ You can
Use, study, modify, copy and sell, including for commercial purposes.
✖ You cannot
Deliver the software while keeping its source code closed.
⚠ You must
If you distribute software that contains GPL code, everything you distribute must be under the same GPL, with its source code.
- Watch out
- Delivering to a client is distributing. Using it yourself, without distributing, does not oblige you to publish. And “GPL-2.0 only” is not “GPL-2.0 or later”: GPL-2.0 alone is not compatible with GPL-3.0.
- Example
- The Linux kernel (GPL-2.0) and WordPress (GPL-2.0 or later).
- Official texts
EUPL 1.2 (European Union)
Strong copyleftEUPL-1.2To be confirmed at the source
✔ You can
Use, modify and distribute, including for commercial purposes.
✖ You cannot
Distribute your changes while keeping the code closed.
⚠ You must
Share the modified code you distribute under this licence, or under a compatible licence listed in its appendix.
- Watch out
- Its list of compatible licences makes mixing simpler than with the GPL alone, but read the appendix for your exact case. It is OSI-approved.
- Example
- Software from European public administrations.
- Official texts
GNU AGPL 3.0
Network copyleftAGPL-3.0Guide of 2026-10-13
✔ You can
Like GPL-3.0: use, modify, distribute, including for commercial purposes.
✖ You cannot
Offer a modified version online without giving the code.
⚠ You must
Like GPL-3.0, plus this: if people use your modified version over a network, you must offer them the source code of that version.
- Watch out
- Hosting a tool you modified under AGPL for a client triggers the obligation. Unmodified, the obligations are lighter, but read the text before delivering.
- Example
- Nextcloud and Grafana.
- Official texts
Creative Commons (CC BY, SA, NC, ND)
Content, data, fontsCC-BY-4.0 · CC-BY-SA-4.0 · CC-BY-NC-4.0 · …Checked at the source · 2026-11-08
✔ You can
Reuse a text, image, music or dataset, according to four combinable elements: BY (credit), SA (share alike), NC (non-commercial), ND (no derivatives).
✖ You cannot
Use an NC work commercially, or adapt an ND work.
⚠ You must
Always credit the author. Depending on the licence: share adaptations under the same terms (SA), do not use them commercially (NC) or do not modify them (ND).
- Watch out
- NC forbids use in a paid deliverable, and ND forbids adapting, so also cutting, translating or cleaning. A CC BY-NC image on a company website is a problem. CC licences are not designed for software.
- Example
- Wikipedia is under CC BY-SA.
- Official texts
SIL Open Font License 1.1
Content, data, fontsOFL-1.1Checked at the source · 2026-11-08
✔ You can
Use the font anywhere (web, print, software), copy it, modify it and embed it in a document or a website.
✖ You cannot
Sell the font by itself, or reuse a reserved name for a modified version.
⚠ You must
Keep the notice and licence; do not sell the font by itself; do not reuse a reserved name for a modified version.
- Watch out
- Fonts bundled with Windows or Office are under the vendor's contract, not OFL: check before embedding them in a website.
- Example
- Playfair Display, DM Sans and Cinzel, the fonts of this site, are under OFL.
- Official texts
Data licences: ODbL and CDLA
Content, data, fontsODbL-1.0 · CDLA-Permissive-2.0 · CDLA-Sharing-1.0To be confirmed at the source
✔ You can
Use and adapt open databases, even commercially.
✖ You cannot
Redistribute a derived database under another licence.
⚠ You must
ODbL: credit and share derived databases under the same licence. CDLA-Sharing: sharing conditions. CDLA-Permissive: mostly credit.
- Watch out
- A data licence covers the database, not always each item inside. An “open” database may contain items under other terms.
- Example
- OpenStreetMap data is under ODbL.
- Official texts
Sustainable Use License (n8n)
Source-availablePersonnalisée (non SPDX)Checked at the source · 2026-11-08
✔ You can
Use n8n for your company's internal business needs, or for personal or non-commercial use. Building and maintaining workflows for a client, on their own n8n, is a permitted service.
✖ You cannot
Resell n8n, or host it so your clients connect and build their own workflows.
⚠ You must
Do not resell n8n, nor host it so that clients connect to it and build their own workflows. Free, non-commercial distribution only.
- Watch out
- “Source visible” does not mean “open source.” If the value of your product comes mostly from n8n, you are outside “internal use.” When in doubt, n8n invites you to write to them.
- Example
- A company automating its own tasks with n8n: allowed. A platform reselling access to n8n: not allowed.
- Official texts
Elastic License 2.0
Source-availableElastic-2.0Checked at the source · 2026-11-08
✔ You can
Use, copy, modify and distribute, including as the engine of your own service.
✖ You cannot
Offer the tool as a managed service, or circumvent licence keys.
⚠ You must
Do not offer the software to third parties as a managed service, do not circumvent licence keys, do not use the trademark misleadingly.
- Watch out
- Hosting a tool under ELv2 for clients as your own product is exactly what is forbidden. Internal use, or as the engine of a service that is not a competitor, remains allowed. Not OSI-approved.
- Example
- Elasticsearch and Kibana.
- Official texts
Business Source License 1.1
Source-availableBUSL-1.1Checked at the source · 2026-11-08
✔ You can
Read, copy, modify and use for non-production purposes, as well as the production use granted by each project's “additional use grant.”
✖ You cannot
Go beyond the project's use grant, for example offering a competing product.
⚠ You must
Respect the project's limits (often: do not offer a competing product). Each version becomes free at its “change date,” at most four years after publication.
- Watch out
- The acronym BSL also designates the Boost licence; for the business licence, it is BUSL. The change date is specific to each version: read the project's licence header.
- Example
- Terraform (HashiCorp, now IBM).
- Official texts
Server Side Public License (SSPL)
Source-availableSSPL-1.0Checked at the source · 2026-11-08
✔ You can
Use and modify freely for yourself.
✖ You cannot
Offer the software as a service without publishing all the infrastructure serving it.
⚠ You must
If you offer the software as a service to third parties, you must publish, under the SSPL, the source code of all the infrastructure that serves it.
- Watch out
- This obligation is so broad that most hosts cannot accept it: in practice, offering the software as a service is blocked. Not OSI-approved.
- Example
- MongoDB.
- Official texts
Open WebUI licence
Source-availablePersonnalisée (BSD-3 + clause de marque)Checked at the source · 2026-11-08
✔ You can
Use, modify and redistribute, including commercially, as with BSD-3.
✖ You cannot
Remove the name and logo, except with 50 users or fewer, a written permission or an enterprise licence.
⚠ You must
Keep the “Open WebUI” name and logo visible, unless you have 50 users or fewer over 30 days, a written permission or an enterprise licence.
- Watch out
- Before version 0.6.6 (2025) it was a plain BSD-3, and before that an MIT. The licence changed along the way: note the version you use.
- Example
- A chat interface for local AI models.
- Official texts
Open core, dual licensing, fair-code
Source-availableConcepts, pas des licencesTo be confirmed at the source
✔ You can
These words describe business models, not rights.
✖ You cannot
Use the “enterprise” files without the paid key.
⚠ You must
Open core: an open core and paid features under a proprietary licence. Dual licensing: you choose one of the two. Fair-code: a label (used by n8n), not a recognised licence.
- Watch out
- Always read the licence of each folder: in the same repository, files can have different licences.
- Example
- A repository whose core is free, but whose “enterprise” files need a paid key.
- Official texts
Open Source AI Definition (OSI 1.0)
Artificial intelligenceOSAID 1.0Checked at the source · 2026-11-08
✔ You can
An AI system is “open source” if it lets you use, study, modify and share it, for any purpose.
✖ You cannot
Nothing: it is a definition, not a licence.
⚠ You must
Three elements: enough information about the training data, the complete training and running code, and the model parameters, all under OSI-approved terms.
- Watch out
- An “open weights” model is not necessarily “open source” in the OSI sense: several popular models have usage conditions.
- Example
- Version 1.0 published in October 2024.
- Official texts
Models under a permissive licence (Apache-2.0, MIT)
Artificial intelligenceApache-2.0 · MITChecked at the source · 2026-11-08
✔ You can
Commercial use, fine-tuning, hosting and redistribution, including of derived versions.
✖ You cannot
Remove the licence notice.
⚠ You must
Keep the licence notice and mark changes (Apache), or keep the notice (MIT).
- Watch out
- Three licences can overlap: the code's, the model weights' and the data's. Check the model card, version by version.
- Example
- Gemma 4 (April 2026) is offered under Apache 2.0, while Gemma 3 stays under the Gemma terms.
- Official texts
Llama Community Licence (Meta)
Artificial intelligencePersonnalisée (Llama 4 Community License)Checked at the source · 2026-11-08
✔ You can
Use, copy, modify and distribute the model, including commercially, royalty-free.
✖ You cannot
Exceed 700 million monthly active users without a licence from Meta, or ignore the acceptable use policy.
⚠ You must
Include the licence and attribution notice, follow the acceptable use policy, and request a licence from Meta above 700 million monthly active users. Depending on the version, you must also display “Built with Llama” and start the names of derived models with “Llama.”
- Watch out
- It is not an OSI-recognised open source licence. Each Llama version has its own text and conditions: read the one for the version you use.
- Example
- A Llama-derived model you redistribute carries Meta's conditions.
- Official texts
Gemma Terms of Use (before Gemma 4)
Artificial intelligenceGemma Terms of UseChecked at the source · 2026-11-08
✔ You can
Use, reproduce, modify and distribute Gemma 3 and earlier models, including commercially.
✖ You cannot
Ignore Google's prohibited use policy.
⚠ You must
Include the terms and notice, pass the prohibited use policy on to those you redistribute to, and comply with it.
- Watch out
- Google may update the prohibited use policy. Gemma 4 (April 2026) left this regime for Apache 2.0: check which version you have.
- Example
- A fine-tuned Gemma 3 model, then redistributed, carries the Gemma terms.
- Official texts
OpenRAIL licences (responsible use)
Artificial intelligenceOpenRAIL · CreativeML OpenRAIL-M · …To be confirmed at the source
✔ You can
Use, modify and redistribute the model, often including commercially.
✖ You cannot
Use the model for a use the licence forbids.
⚠ You must
Respect a list of prohibited uses and pass it on, as a contract clause, to those you redistribute to.
- Watch out
- The use restrictions follow the model and its derivatives. It is not open source in the OSI sense. Read each model's text.
- Example
- Several image and language models published on Hugging Face.
- Official texts
“other,” “unknown” and non-commercial labels
Artificial intelligenceÉtiquettes de Hugging FaceTo be confirmed at the source
✔ You can
Nothing automatic: the label does not say what is allowed.
✖ You cannot
Use it without a clear licence, or put a “non-commercial” model in a paid deliverable.
⚠ You must
Read the model's licence file, then ask the author if in doubt.
- Watch out
- A “non-commercial” model cannot be used in a paid deliverable. “Unknown” means nobody specified the licence: without a licence, no right of reuse.
- Example
- A research model shared for academic trials only.
- Official texts
Proprietary licences, subscriptions and freeware
ProprietaryEULA · conditions de serviceGuide of 2026-10-13
✔ You can
What the vendor's contract says, and nothing more.
✖ You cannot
What the contract forbids: copying, commercial use or redistribution, as the case may be.
⚠ You must
Respect the contract: number of users, commercial use, duration, redistribution.
- Watch out
- “Free” is not “free as in freedom”: freeware can forbid commercial use, copying or modification. A trial (shareware) and freemium (free, but limited features) have their own limits.
- Example
- Software that downloads for free, but whose contract forbids use in a business.
Docker Desktop: threshold-based licence
ProprietaryConditions de service de DockerChecked at the source · 2026-11-08
✔ You can
Free for small businesses (fewer than 250 employees and less than US$10 million in revenue), personal use, education and non-commercial open source.
✖ You cannot
Use it for free above the thresholds: 250 employees or US$10 million in revenue.
⚠ You must
Above either threshold (250 employees or US$10 million in revenue), a paid per-user subscription.
- Watch out
- Each threshold applies on its own, and a subsidiary counts with its parent company. Docker Engine, the engine alone, is a different product.
- Example
- A team of 10 people in a company of 400 employees must pay the subscription.
- Official texts
How to do it, in practice
Example to adapt
Information template, not legal advice: if in doubt, ask a lawyer.