MIT License
MIT
MIT lets you use, change, sell, or host the software with almost no friction. Keep the copyright and license notice when you pass the code or a package to someone else.
Before you run, change, or host someone else's app, it's worth knowing what its license lets you do. Compare the common licenses in one table, then open a license for its obligations, its official text, and the apps that use it.
This is a practical guide, not legal advice. If money, customers, or a commercial product are involved, read the project's license and get legal help.
The table shows what each license allows for the things self-hosters do: run it, use it at work, host it for others, change it, and pass it on. It reports what the license text permits, not what a company policy will approve.
| License | Self-host | Company | OSI | Service | Modify | Redistribute | Copyleft |
|---|---|---|---|---|---|---|---|
| MIT | yes | yes | yes | yes | yes | yes | none |
| Apache-2.0 | yes | yes | yes | yes | yes | yes | none |
| BSD-2-Clause | yes | yes | yes | yes | yes | yes | none |
| BSD-3-Clause | yes | yes | yes | yes | yes | yes | none |
| ISC | yes | yes | yes | yes | yes | yes | none |
| Zlib | yes | yes | yes | yes | yes | yes | none |
| Unlicense | yes | yes | yes | yes | yes | yes | none |
| CC0-1.0 | yes | yes | pd | yes | yes | yes | none |
| WTFPL | yes | yes | no | yes | yes | yes | none |
| MPL-2.0 | yes | yes | yes | yes | careful | careful | weak |
| LGPL-2.1 | yes | yes | yes | yes | careful | careful | weak |
| LGPL-3.0 | yes | yes | yes | yes | careful | careful | weak |
| EPL-2.0 | yes | yes | yes | yes | careful | careful | weak |
| GPL-2.0 | yes | yes | yes | yes | careful | careful | strong |
| GPL-3.0 | yes | yes | yes | yes | careful | careful | strong |
| AGPL-3.0 | yes | yes | yes | careful | careful | careful | network |
| EUPL-1.2 | yes | yes | yes | careful | careful | careful | network |
| OSL-3.0 | yes | yes | yes | careful | careful | careful | network |
| SSPL-1.0 | yes | yes | no | careful | careful | careful | service |
| Elastic-2.0 | yes | yes | no | no | careful | careful | none |
| BUSL-1.1 | depends | depends | no | depends | depends | depends | delayed |
| FSL | yes | careful | no | careful | yes | careful | delayed |
| PolyForm Shield | yes | careful | no | careful | yes | careful | none |
| Sustainable Use | yes | yes | no | no | depends | depends | none |
| PolyForm NC | yes | no | no | no | careful | careful | none |
| Proprietary / EULA | depends | depends | n.a. | depends | no | no | n.a. |
| CC BY 4.0 | yes | yes | n.a. | yes | yes | yes | none |
| CC BY-SA 4.0 | yes | yes | n.a. | careful | careful | careful | share-alike |
| CC BY-NC 4.0 | yes | no | n.a. | no | careful | careful | none |
| Dual licensing | yes | yes | depends | depends | depends | depends | depends |
| Community + enterprise | depends | depends | depends | depends | depends | depends | mixed |
| or-later / mixed trees | yes | yes | depends | depends | depends | depends | mixed |
| Column | The question it answers |
|---|---|
| Self-host | Can you run it on your own hardware, for yourself and your household? |
| Company | Can it run on a work server for internal use? |
| OSI | Is it approved by the Open Source Initiative? pd means a public domain dedication, which works like open source without being on the list. n.a. means OSI doesn't review that kind of license, such as Creative Commons or a commercial EULA. depends marks patterns that mix licenses, such as dual licensing. |
| Service | Can you host it for people outside your household or company, including paid hosting? |
| Modify | Can you change the code, and what do you owe when your changes leave your server? |
| Redistribute | Can you pass it on in images, appliances, forks, or products? |
| Copyleft | Do conditions travel with the code, and how far? |
| Value | Meaning |
|---|---|
| yes | Allowed. Routine notices or attribution may still apply. |
| careful | Allowed with a real obligation, such as sharing source, share-alike, or a limit on competing. The license's card explains it. |
| depends | Project terms, a chosen option, or a separate agreement decide. |
| no | The license doesn't allow it. |
WTFPL, for example, allows everything, yet some company policies ban it. The self-hosted apps directory uses the same license names, so you can filter apps by license there.
Most licenses here fall into four families. What separates them is what you owe when the software leaves your hands.
| Family | Examples | What you owe |
|---|---|---|
| Permissive | MIT, Apache-2.0, BSD | Keep the copyright notices when you pass it on. Your fork can stay closed. |
| Weak copyleft | MPL-2.0, LGPL | Changes to the covered files or library stay open when you ship them. The rest of your product stays yours. |
| Copyleft | GPL, AGPL | Distributed covered works follow GPL terms; AGPL adds a source offer for modified network versions. |
| Restricted | SSPL, Elastic, BSL, FSL, PolyForm | The code is public, but the terms limit some uses, often hosting it as a service or competing with the publisher. These are source-available, not open source. |
Self-hosting a restricted app for yourself or your company is usually allowed, but each license's own text decides. Public domain dedications work like permissive licenses. Creative Commons licenses usually cover docs and media, not the app's code.
GPL applies when you distribute a copy, changed or not. Then you must pass on the license and make the source available to whoever gets the copy. Running it on your own server, or inside your company, isn't distribution.
AGPL adds a network rule in section 13. If you change the program and people use your changed version over a network, you must offer them its source. That rule stops a changed, hosted copy from staying closed, which is why AGPL is common for self-hosted web apps.
Two points people often misread:
EUPL and OSL have network rules too. Their cards below explain them.
Each card says what the license asks of you and links to its official text. When the self-hosted apps directory lists apps under a license, the card links to them too.
Run it, change it, sell it, keep your fork private forever. The only real duty is keeping copyright notices when you redistribute.
MIT
MIT lets you use, change, sell, or host the software with almost no friction. Keep the copyright and license notice when you pass the code or a package to someone else.
Apache-2.0
Apache-2.0 gives you MIT-like freedom with explicit patent protection. Keep the license, copyright notices, and any NOTICE file when you redistribute it.
BSD-2-Clause
BSD-2-Clause lets you use and change the software freely. Keep the copyright notice and disclaimer when you redistribute it.
BSD-3-Clause
BSD-2-Clause plus one rule: you may not use the original author's name to promote your product without permission.
ISC
A short permissive license that works like MIT in practice: use it, change it, keep the notice when you redistribute.
Zlib
Permissive and commercial-friendly, as long as you do not misrepresent where the code came from and you mark altered versions.
Fine to run, with almost nothing to comply with. The real question is what part of the project they actually cover.
Unlicense
A public-domain style dedication. Where it works as intended, you can use, change, and share the software with almost no conditions.
CC0-1.0
A Creative Commons public-domain dedication. Common for data and documentation, sometimes used to waive copyright on code as far as the law allows.
WTFPL
An informal do-what-you-want license. In practice it is as free as anything on this page.
Free to use anywhere. The share-back duty is scoped: changes to the covered files or library stay open when you ship them, the rest of your product stays yours.
MPL-2.0
Weak, file-level copyleft. You can combine MPL code with other code, but distributed changes to MPL-covered files stay under MPL with source available.
LGPL-2.1
Weak copyleft built for libraries. You can link it into other software more flexibly than GPL, but changes to the LGPL library itself get shared when you distribute them.
LGPL-3.0
The newer library license. Same share-alike idea as LGPL-2.1, updated terms around combining and installing the library.
EPL-2.0
Weak copyleft, common in the Eclipse and Java tooling world. Source duties focus on the EPL modules you distribute, not on everything around them.
The whole program stays free software. GPL triggers when you distribute it. AGPL, EUPL, and OSL also trigger when people reach your modified version over a network.
GPL-2.0
GPL-2.0 lets you run and change the software freely. If you distribute it, you must provide the corresponding source under the same GPL terms.
GPL-3.0
GPL-3.0 lets you run and change the software freely, but anything you distribute must keep the same source-sharing freedom. It adds clearer patent protection and rules for installing modified software on locked-down devices.
AGPL-3.0
AGPL-3.0 works like GPL but also protects people using a modified version over a network. If you change the hosted app, offer those users the corresponding source.
EUPL-1.2
A European copyleft license with a remote-access trigger, which is why it sits in this family rather than with the weak copyleft licenses.
OSL-3.0
Strong copyleft with network-use language. Less common than AGPL, similar questions when you offer software to other people.
Code you can read and usually self-host, with terms that put it outside the open-source definition. SSPL conditions service use on releasing service source, while BSL, FSL, and PolyForm depend on project parameters or competition limits.
SSPL-1.0
SSPL is comfortable for running software yourself, but offering it as a service can require releasing much of the surrounding service stack. That makes it source-available, not open source.
Elastic-2.0
Elastic-2.0 is meant for self-managed use and lets you modify the software. You cannot offer the product itself to others as a managed service.
BUSL-1.1
BUSL-1.1 changes from project to project, so the Additional Use Grant decides what you may do until the published change date. After that date, the code moves to the named open-source license.
FSL allows broad use but temporarily blocks products that compete with the original software. After the delay, the code converts to MIT or Apache-2.0.
PolyForm-Shield-1.0.0
Broad use allowed, except using the software to compete with the licensor's products.
SUL
Vendor terms that allow free internal self-hosting while limiting your right to offer the software itself to third parties as a service.
PolyForm-Noncommercial-1.0.0
Non-commercial use, modification, and sharing are allowed. Commercial use needs separate permission from the publisher.
Your rights come only from that vendor agreement. There is no general open-source permission set underneath it.
You will meet these on docs, wikis, diagrams, and media packs around self-hosting, not usually on the app backend itself. The first question is always which part of the project they cover.
CC-BY-4.0
Requires attribution. Built for creative works and data rather than application backends.
CC-BY-SA-4.0
Attribution plus share-alike. Publicly shared adaptations must use a compatible ShareAlike license.
CC-BY-NC-4.0
Free non-commercial use with attribution. Company use and other commercial use need a different permission.
Three shapes you will meet on directory cards that are not single licenses at all.
Dual licensing gives the same code more than one legal path, often AGPL for the community and a paid license for companies. You follow the option you qualify for.
The software splits into a free community edition and paid enterprise modules. The core may be open or source-available while features like SSO sit behind a separate commercial license.
Version suffixes, linking exceptions, and licenses that vary by folder. These change what you may do even when the short label looks familiar.
Open source means anyone may use, study, change, and share the software for any purpose, including commercial use, as set out in the Open Source Definition. MIT, Apache-2.0, GPL, and AGPL all qualify. A duty to share source isn't a limit on use, so copyleft licenses count.
Source-available means the code is public, but the terms limit some uses. SSPL, Elastic License, BSL, FSL, and PolyForm each limit something different.
A public repository or a free download doesn't tell you which one you have. Read the license before company use, redistribution, or paid hosting.
Start from what you want to allow and what you want to prevent.
| If you want | Consider |
|---|---|
| As many users as possible, and you don't mind who profits | MIT, or Apache-2.0 for an explicit patent grant |
| Changes to your files shared back, without rules for whole products | MPL-2.0 |
| A library others can use in closed products | LGPL-3.0, or MIT |
| No closed, hosted copies of your changed app | AGPL-3.0 |
| A business on top of open source code | AGPL-3.0 plus a paid commercial license. You need the rights to all the code, often through contributor agreements. |
| To block resale as a managed service, and you accept losing the open source label | BSL 1.1 or FSL, which turn into open source licenses after a set time. Elastic-2.0 or Sustainable Use if you want no conversion date. |
| Free personal use and paid company use | PolyForm Noncommercial. Expect fewer business users. |
Whatever you choose, add a short note beside the LICENSE file that says in plain words what self-hosters may do.
Yes, as long as the copies stay inside the company. GPL applies when you distribute, and internal use isn't distribution.
No. Code is open source only when its license meets the Open Source Definition. SSPL, BSL, FSL, Elastic, and PolyForm code is often public, and none of those licenses are open source.
Yes. Permissive licenses allow it. That's one reason some projects later move to AGPL or a source-available license.
No. Each project sets its own Additional Use Grant and change date, so read both.
First look for a license grant in the README, the docs, or other files. If there's none anywhere, normal copyright applies, so treat it as all rights reserved. GitHub's licensing guidance explains this.