Charon IA

Reference

Licences and open source

“Free” does not mean “without conditions.” A licence says what you may do with software, an AI model, an image or a font. Here is how to read one.

At Charon IA, we read the licence of every tool before installing it in a system, because that is what makes our work legal, lasting and safe for you. Our philosophy

Coming soon: a complete knowledge base on licences. This page is its starting point.

This guide is informational and is not legal advice. Last checked: November 8, 2026.

At a glance

What can I do with this software?

One line per licence. Click the name to read the sheet.

  • ✔ Allowed
  • ⚠ Allowed with a condition
  • ✖ Forbidden
  • ? To be confirmed at the source
  • — Not applicable
LicenceFor my businessDeliver it to a clientResell it as a serviceModify it
Public domain: CC0 and UnlicenseCC0-1.0 · Unlicense
MIT licenceMIT
BSD licences (2 and 3 clauses)BSD-2-Clause · BSD-3-Clause
Apache License 2.0Apache-2.0
GNU LGPL 2.1 and 3.0LGPL-2.1 · LGPL-3.0
Mozilla Public License 2.0MPL-2.0
Eclipse Public License 2.0 and CDDL 1.0EPL-2.0 · CDDL-1.0
GNU GPL 2.0 and 3.0GPL-2.0 · GPL-3.0
EUPL 1.2 (European Union)EUPL-1.2
GNU AGPL 3.0AGPL-3.0
Sustainable Use License (n8n)Personnalisée (non SPDX)
Elastic License 2.0Elastic-2.0
Business Source License 1.1BUSL-1.1
Server Side Public License (SSPL)SSPL-1.0
Open WebUI licencePersonnalisée (BSD-3 + clause de marque)
Models under a permissive licence (Apache-2.0, MIT)Apache-2.0 · MIT
Llama Community Licence (Meta)Personnalisée (Llama 4 Community License)
Gemma Terms of Use (before Gemma 4)Gemma Terms of Use
OpenRAIL licences (responsible use)OpenRAIL · CreativeML OpenRAIL-M · …
Proprietary licences, subscriptions and freewareEULA · conditions de service
Docker Desktop: threshold-based licenceConditions de service de Docker———

Hover a cell for a summary, click for the details. Always read the sheet before delivering.

How it works

A licence is the author's written permission

An architect's plan belongs to its author: without their agreement, you cannot copy it or build from it. The same goes for software, a text, an image or an AI model: the law protects them from the moment they are created (that is copyright). The licence is the author's written agreement, with its conditions.

  1. 1

    The author creates

    Copyright exists right away. Without a licence, everything is forbidden.

  2. 2

    They publish a licence

    A text says what you can do (use, copy, modify, sell) and under what conditions.

  3. 3

    You use it

    By using, copying or delivering the work, you accept those conditions.

  4. 4

    You follow them

    Otherwise the permission can lapse and you no longer have the right to use it.

What a licence settles

  • use: personal, internal, commercial
  • copying and modifying
  • redistribution: delivering to a client or publishing
  • warranty: most often, none

What it does not settle

  • the trademark and logo
  • the security or quality of the code
  • the protection of personal information (Law 25)
  • the licences of other elements in the same product

Why so many licences

Authors do not all have the same goal. Some want everyone to use their work with no conditions. Others want what is built on it to stay open. Others protect their business model or sell a closed product. Each licence family answers one of those goals.

The map of the territory

From the freest to the most closed

A licence is the permission the author gives you, with conditions. The further right you go, the more conditions apply to you.

Public domaindo what you want with it
Permissivecredit the author, that's all
Weak copyleftshare your changes to that file
Strong copyleftwhat you deliver must stay open
Network copylefteven an online service counts
Source-availablereadable code, limited use
Proprietaryper the vendor's contract
← more freedom for youmore constraints on you →

Copyleft: a rule that requires whatever you build from the code to be shared under the same conditions. Free or open source? Two movements, two definitions: the Open Source Initiative (OSI) publishes a ten-criteria definition, and the Free Software Foundation (FSF) speaks of four freedoms. They overlap a lot without being identical.

The licence sheets

The licences, one by one

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.

How to do it, in practice

  1. Nothing to do: you can copy, modify and sell without crediting anyone.
  2. As a courtesy you may still name the source, but it is not required.

Example to adapt

Data: dataset X, public domain (CC0).

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Keep the author's “Copyright” line and the MIT licence text: those are the only two obligations.
  2. Create a credits file in your product (for example LICENSES.txt or an “About” page) and copy both items there for each MIT-licensed software you use.
  3. If you deliver the software to a client, that file goes with it. For an online service only, a “Credits” page on the site is enough in practice.

Example to adapt

This product uses SoftwareName (https://project-address)
Copyright (c) 2024 Author name
MIT License: the full licence text is included in the file LICENSES/SoftwareName.txt

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Same step as for MIT: keep the “Copyright” line, the list of conditions and the disclaimer of the licence.
  2. If you deliver the software in compiled form, reproduce those texts in the documentation or the credits file delivered with it.
  3. 3-clause version: do not use the authors' names in your advertising to suggest they endorse your product, without their permission.

Example to adapt

This product includes SoftwareName.
Copyright (c) 2024, Author name. All rights reserved.
3-clause BSD licence: full text in LICENSES/SoftwareName.txt

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Include a copy of the Apache 2.0 licence (LICENSE file) with everything you deliver.
  2. If the original software contains a NOTICE file, copy it as is into your delivery, without altering it. You may add your own lines below it.
  3. If you modify files, write a short note at the top of each saying it was changed: by whom, when, what.

Example to adapt

# Modified 2026-11-08 by Your Company: added network error handling.
# Copyright 2024 Original Author (Apache 2.0 licence)

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Keep the “Copyright” line and the licence text, as with MIT.
  2. Put them in your credits file or “About” page.

Example to adapt

This product uses SoftwareName (https://project-address)
Copyright (c) 2024 Author name
ISC / zlib / Boost licence (as applicable): the full licence text is included in the file LICENSES/SoftwareName.txt

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Include the LGPL licence and say where to find the library's source code.
  2. Make the library replaceable: the simplest way is to ship it as a separate file (.dll, .so, or package) that your program loads at startup.
  3. Write an instructions page: where the file is, how to replace it with another version, and how to test it.
  4. If you modify the library itself, publish those changes under the LGPL. Your own code can stay closed.

Example to adapt

This product uses the library LibName (LGPL 2.1).
Source code: https://project-address
To replace it: replace the file libname.dll in the /lib folder with your version, then restart.

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Keep the original notice at the top of each MPL file (“This Source Code Form is subject to the terms of the Mozilla Public License…”).
  2. If you modify an MPL file and deliver it, offer the source of that file, under the MPL, with a link or an address to get it.
  3. Your own separate files can stay closed and under your licence.

Example to adapt

This product contains code under the MPL 2.0 licence.
Source code of the MPL files (including our changes): https://your-site/source-code
Licence: https://mozilla.org/MPL/2.0/

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Keep the copyright notices and the licence with the original files.
  2. If you modify those files or modules and deliver them, offer their source under the same licence (EPL or CDDL).
  3. Your own code, in separate files, can have another licence.
  4. Careful: EPL and CDDL do not mix with the GPL. Read the “Mixing” section.

Example to adapt

This product contains modules under the EPL 2.0 licence.
Source code of the modules (with our changes): https://your-site/source-code

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. If you hand the software to someone (installer, Docker image, device), also give them the exact source code of that version, or include a written offer valid for at least three years.
  2. Simplest: put the source code on your site, next to the download, and add the link in your delivery.
  3. Keep the GPL licence and copyright notices. What you deliver with it as linked program must also be under the GPL.
  4. Using the software on your side, without handing a copy to your clients, does not trigger these obligations.

Example to adapt

This product contains free software under the GPL 3 licence.
Source code of this version: https://your-site/source-code/product-1.2.zip
We will also send it on request to [email protected] for at least three years.

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. This European licence is close to the GPL for code sharing. We have not yet checked the detail at the source.
  2. Before delivering, read the official text (link in the sheet).

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. If you modify the software and people use it online, add a clearly visible “Source code” link in the interface that leads to the code of YOUR version.
  2. Keep that link up to date: with every change you put online, the published code must follow.
  3. If you change nothing, you do not have this obligation. If you hand a copy to a client, the GPL rules apply.

Example to adapt

Application footer:
Source code of this version: https://your-site/source-code (AGPL 3 licence)

Information template, not legal advice: if in doubt, ask a lawyer.

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).

How to do it, in practice

  1. Give the Title, Author, Source and Licence (TASL method), with links when possible.
  2. If you changed the work, say so (“modified: cropped”).
  3. For SA licences, publish your version under the same licence. For NC, no commercial use. For ND, no modification.

Example to adapt

“Photo of a building site” by Jean Tremblay, https://source-address, licence CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. You can use the font in a site, a document or a product, even commercial, without crediting the author.
  2. If you redistribute it (font file), include the OFL.txt licence file and keep the copyright line.
  3. Do not sell the font on its own. If you modify it, rename it if the name is reserved.

Example to adapt

In your fonts/ folder: the font's OFL.txt + its copyright notice.

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Allowed: building, installing and maintaining n8n workflows for a client, on the client's n8n or on yours for your own business.
  2. Forbidden: reselling n8n, or hosting it so your clients connect and build their own workflows, without a commercial licence.
  3. Keep the licence and copyright notices in the files.
  4. For a need beyond that: ask n8n for a licence (https://n8n.io).

Example to adapt

Client contract: “We install and configure the workflows on your own n8n instance, which you remain the holder of.”

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. You can use, copy, modify and deliver the software.
  2. Do not offer the software to third parties as a managed service where they access a significant part of its features.
  3. Do not circumvent licence keys, and do not remove licence or trademark notices.

Example to adapt

Allowed: install the software for a client on their server.
Forbidden: sell a “Hosted Software X” subscription to all your clients.

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Open the project's LICENSE file: the header says what is allowed in production (“Additional Use Grant”).
  2. Note the “Change Date”: on that date the code automatically becomes free-licensed (at most 4 years after publication).
  3. Before the change date, do not use the software in production if your use is not listed.

Example to adapt

In the licence header, look for:
Additional Use Grant: … (what is allowed)
Change Date: 2030-01-01 (start of the free licence)

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Internal use, or simple delivery of a copy: nothing special to do besides keeping the licence.
  2. Offering the software as a service to third parties: you would have to publish the code of all the infrastructure that runs it (management, interface, backups, etc.). That is why most people avoid this case.
  3. If that is your project, use the vendor's commercial version instead.

Example to adapt

Tip: if a client wants to use the software, install it on THEIR server instead of hosting it for them.

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Keep the name “Open WebUI” and its logo visible in the interface, except in the cases below.
  2. Exceptions: 50 users or fewer over 30 days, written permission from the authors, or an enterprise licence.
  3. Also keep the copyright notice and the BSD-3 licence in your files.

Example to adapt

Interface: “Powered by Open WebUI” with the logo, visible at the bottom of the login page.

Information template, not legal advice: if in doubt, ask a lawyer.

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).

How to do it, in practice

  1. Same as for the Apache 2.0 licence: include the licence and, if there is one, the model's NOTICE file.
  2. If you modify the model's files, note it in a short note (“modified by… on…”).
  3. Your data and your use stay yours: no obligation to publish your results.

Example to adapt

Model: Gemma 4 (Google), Apache 2.0 licence. See LICENSES/gemma-4.txt

Information template, not legal advice: if in doubt, ask a lawyer.

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.”

How to do it, in practice

  1. Include the Llama licence and a visible attribution notice, for example “Built with Llama” (the exact wording depends on the version).
  2. Follow Meta's acceptable use policy and pass it on to those you hand the model to.
  3. Depending on the version, the name of a derived model must start with “Llama”.
  4. Above 700 million monthly active users, ask Meta for a licence.

Example to adapt

In your product: “Built with Llama” + link to the official licence of the version used.

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Before 2 April 2026, Gemma had its own terms. Include them with what you deliver.
  2. Pass Google's list of prohibited uses on to those you hand the model to.
  3. For Gemma 4, the licence is Apache 2.0: see that sheet.

Example to adapt

Included with the delivery: copy of the Gemma Terms of Use + Prohibited Use Policy.

Information template, not legal advice: if in doubt, ask a lawyer.

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.

How to do it, in practice

  1. Count your employees and your annual revenue (the whole company, not only the team using it).
  2. Fewer than 250 employees AND under US$10 million in revenue: free to use.
  3. Otherwise: paid per-user subscription. Docker's free tools (the engine) are not concerned; it is Docker Desktop.

Example to adapt

Internal sheet: “Docker Desktop – 12 employees – free, recheck every year”.

Information template, not legal advice: if in doubt, ask a lawyer.

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

Mixing licences

Common combinations

Mixing two licences means applying them to the same result. Here are the cases that come up most often.

CombinationPossible?Keep in mind
MIT or BSD with copyleftYesThe result follows the copyleft licence. Guide of 2026-10-13
Apache-2.0 with GPL-3.0YesThe result is under GPL-3.0 (compatible according to the FSF). Checked at the source · 2026-11-08
Apache-2.0 with GPL-2.0 onlyNoThe patent clauses do not line up, according to the FSF. Checked at the source · 2026-11-08
GPL-2.0 only with GPL-3.0NoTwo distinct versions: “only” versus “or later.” Checked at the source · 2026-11-08
GPL-2.0 or later with GPL-3.0YesYou pick version 3 for the whole. Guide of 2026-10-13
MPL-2.0 with GPLYes, generallyUnless the “incompatible with secondary licenses” notice is present. Checked at the source · 2026-11-08
EPL or CDDL with GPLNoConsidered incompatible with the GPL. Checked at the source · 2026-11-08
AGPL-3.0 with GPL-3.0Yes, with conditionsBoth licences provide a way to pass from one to the other: read the AGPL clause. Guide of 2026-10-13
Closed code distributed with GPL codeNoThe whole would have to be published under the GPL. Checked at the source · 2026-11-08
LGPL library in closed softwareYes, with conditionsLinking, possible replacement, sharing the library's changes. Guide of 2026-10-13
CC BY-NC content in a paid deliverableNoNC forbids commercial use. Checked at the source · 2026-11-08

The pitfalls

What trips people up most often

“Free” is not “free as in freedom”

A free download can forbid commercial use, copying or modification.

“Source visible” is not “open source”

Being able to read the code does not mean being able to use it as you wish.

The acronym BSL

BSL designates the Boost licence; the business licence is written BUSL.

The label hides the file

The repository says “MIT,” but a folder or a file may have another licence.

Delivering is distributing

Handing software to a client triggers the GPL's obligations, even if you do not publish it.

Hosting a modified AGPL

Offering a modified version online obliges you to give its code to the users.

The managed service (ELv2, SUL, BUSL)

Hosting the tool for others, as a product, is often what is forbidden.

“NC” in a dataset or a model

Non-commercial means: not in a paid deliverable.

Three licences in one model

The code, the weights and the data can each have their own licence.

GPL-2.0 only versus or later

Two versions that do not mix. Read the “only” or “or later” wording.

The licence changes along the way

Open WebUI, Gemma or Terraform changed licence: always note the version used.

Trademark versus licence

An open licence does not give you the right to use the name or the logo.

Docker Desktop in business

Above 250 employees or US$10 million in revenue, the subscription is mandatory.

Dependencies of dependencies

Your project inherits the licences of everything it bundles, at every level.

Our practice

How we do it at Charon IA

Every tool, library, model and service we use has a documented licence notice. We prefer open, permissive licences, we keep the notices they require, and we read the licence of the exact version before delivering anything to a client.

When a case is borderline, we say so, and we have it checked by an intellectual property lawyer.

Five checkpoints before choosing or using

  1. What I am doing: internal use, distribution, or a service for others.
  2. The nature of the element: code, model weights, data, a font, content.
  3. The usage clauses: commercial, competing, employee or user threshold.
  4. The exact version, and any licence change since it was published.
  5. Who answers for a mistake. When in doubt, ask a legal professional.

Good to know

About this guide

This guide is informational and is not legal advice. Before delivering to a client or publishing a product, have borderline cases checked by an intellectual property lawyer.

Last checked at the source: November 8, 2026 for AI licences, “source-available” licences, Docker Desktop and licence compatibilities. The other sheets come from our internal guide of October 13, 2026. The badge on each sheet shows what was checked and what remains to be confirmed.

An error, a broken link? Write to [email protected].

The philosophy of Charon IA

Charon IA is a Quebec-based integrator of sovereign, local and hybrid AI for SMEs. Six rules, non-negotiable:

  1. Sovereignty Your data belongs to you. It stays with you, encrypted.
  2. Zero black boxes Every component is named, its licence checked, its role explained.
  3. Security from the foundation Zero trust, encryption, logging, Law 25.
  4. Autonomy We leave; your team stays capable.
  5. Clear-eyed pluralism Local, hybrid or cloud, open or commercial: we choose the tool that serves your case.
  6. Durability Documentation and up-to-date plans: what we build must stand in ten years.

Read more on the home page

Why we read every licence

Concrete examples

  • Docker Desktop Free for a small business (fewer than 250 employees AND less than US$10 M in revenue). Above that, a paid per-user subscription.
    Docker's official page ↗ (opens in a new tab)
  • n8n You can build workflows for a client on their own n8n. Hosting n8n so your clients connect and build their own workflows requires a commercial licence.
    n8n's official page ↗ (opens in a new tab)
  • GPL If you deliver the software, the recipient is entitled to the source code of everything you deliver with it.
    GPL text (GNU) ↗ (opens in a new tab)

True stories

Hancom and Ghostscript

Hancom, a South Korean company, built Ghostscript into its office software. Ghostscript is offered under the free GPL licence or a paid commercial licence. Hancom neither paid for the commercial licence nor opened the code of its applications. Artifex, Ghostscript's author, claimed a royalty for those years of unlicensed use. The court recognised that the GPL also applies as a contract. The case was settled out of court, confidentially.

Quartz: an open source licence is a contract ↗ (opens in a new tab)

Vizio and the source code

In 2018, the Software Freedom Conservancy, a non-profit, bought a Vizio TV containing GPL v2 software and asked for the source code. Judging the answers insufficient, it sued in 2021. A California court ruled that the code must be provided in a form that others can obtain and modify. We did not find a final judgment (checked in November 2026).

DLA Piper: key takeaways of the ruling ↗ (opens in a new tab)

Reconstruction (typical case)

An SME has a consultant install an automation tool whose licence limits use to internal purposes. Two years later, the company is put up for sale. The buyer's due diligence finds that the tool is not allowed for its commercial use. Usual consequences: delayed sale, price negotiated down, urgent replacement of the tool.

Reconstruction note: a typical scenario built to illustrate, not a specific event. No real name or figure.

Our rule: no licence read, no installation.

Our philosophy