GetSelfHosted
Licences

What each licence actually lets you do

Every edition in this catalogue states its licence. This is what those licences permit, what they require of you and what they refuse to guarantee — read from the licence's own text, with the source and the date beside each one.

16 licences · 35 entries

Strong copyleft

Ship a binary, publish the source under the same licence.

  • GNU Affero General Public License v3.0

    Permissions of this strongest copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights. When a modified version is used to provide a service over a network, the complete source code of the modified version must be made available.

    9 entriesAGPL-3.0

  • GNU General Public License v3.0

    Permissions of this strong copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights.

    2 entriesGPL-3.0

Permissive

Run it, change it, ship it. Keep the notice.

  • MIT License

    A short and simple permissive license with conditions only requiring preservation of copyright and license notices. Licensed works, modifications, and larger works may be distributed under different terms and without source code.

    14 entriesMIT

  • Apache License 2.0

    A permissive license whose main conditions require preservation of copyright and license notices. Contributors provide an express grant of patent rights. Licensed works, modifications, and larger works may be distributed under different terms and without source code.

    5 entriesApache-2.0

  • BSD 2-Clause "Simplified" License

    A permissive license that comes in two variants, the BSD 2-Clause and BSD 3-Clause. Both have very minute differences to the MIT license.

    1 entryBSD-2-Clause

  • BSD 3-Clause "New" or "Revised" License

    A permissive license similar to the BSD 2-Clause License, but with a 3rd clause that prohibits others from using the name of the copyright holder or its contributors to promote derived products without written consent.

    1 entryBSD-3-Clause

Source available

The code is readable. The licence is the vendor's.

  • Kirby End User License Agreement

    Kirby's source code is public on GitHub, but the licence file states that Kirby is not free and composer.json declares the package proprietary. A licence covers one installation on one domain, and the EULA licenses development and private installations free of charge. Open code is therefore not open source here: the terms come from a vendor agreement, not from an OSI-approved licence.

    1 entryVendor licence

  • Open WebUI License

    The BSD-3-Clause text with an added clause 4: altering or removing Open WebUI branding is forbidden in any deployment, except for deployments of 50 or fewer end users in a rolling 30 days, with prior written permission, or under an enterprise licence. A restriction on top of an open licence is why the catalogue records this edition as source available rather than open source.

    1 entryVendor licence

  • OpenPanel End User License Agreement and CC BY-NC

    Two instruments, per the repository README: the OpenPanel EULA covers OpenAdmin and the UI, while Creative Commons Attribution-NonCommercial covers OpenCLI and the configuration files. The licence covers personal, educational, evaluation, non-commercial and internal business use; hosting third parties commercially is not permitted. No OSI-approved licence is named anywhere.

    1 entryVendor licence

  • Business Source License 1.1

    Not an open-source licence: the SPDX text opens by saying so. It grants the right to copy, modify, create derivative works, redistribute and make non-production use of the licensed work; production use is allowed only as far as the licensor's Additional Use Grant says. On the Change Date, or the fourth anniversary of the first publicly available distribution of that version, whichever comes first, the version switches to the Change License the licensor named. A use that does not comply needs a commercial licence.

    No published entry uses it todayBUSL-1.1

  • Elastic License 2.0

    A source-available licence, not an open-source one. It grants a non-exclusive, royalty-free right to use, copy, distribute, modify and create derivative works, and then limits three things: you may not provide the software to third parties as a hosted or managed service that gives users access to a substantial set of its features, you may not move, change, disable or circumvent the licence-key functionality, and you may not alter or obscure the licensor's licensing, copyright or other notices.

    No published entry uses it todayElastic-2.0

  • Metabase Commercial License

    Metabase publishes the enterprise source, and running the self-hosted Pro or Enterprise edition means running the enterprise image with a licence token. The grant is a commercial licence tied to that token, not an open-source licence: what the paid plans buy is a licence to run the enterprise build.

    No published entry uses it todayVendor licence

Weak copyleft

Changes to the library stay open; your app need not.

  • GNU Lesser General Public License v3.0

    Permissions of this copyleft license are conditioned on making available complete source code of licensed works and modifications under the same license or the GNU GPLv3. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights. However, a larger work using the licensed work through interfaces provided by the licensed work may be distributed under different terms and without source code for the larger work.

    No published entry uses it todayLGPL-3.0

  • Mozilla Public License 2.0

    Permissions of this weak copyleft license are conditioned on making available source code of licensed files and modifications of those files under the same license (or in certain cases, one of the GNU licenses). Copyright and license notices must be preserved. Contributors provide an express grant of patent rights. However, a larger work using the licensed work may be distributed under different terms and without source code for files added in the larger work.

    No published entry uses it todayMPL-2.0

Proprietary

Paid terms set by the vendor, not a public licence.

  • Metabase Hosting Terms of Service

    The Cloud plan's licence is Metabase's hosting terms, listed in the plan comparison as the cloud hosting EULA. It governs a service Metabase runs, so there is no self-hosted edition under these terms.

    No published entry uses it todayVendor licence

  • Open WebUI Enterprise License

    The vendor's deployment table marks white-labelling, rebranding, modified branding and enterprise-exclusive offerings as requiring this licence. Terms, seats and price are set in the agreement; the vendor publishes no figure and no seat count.

    No published entry uses it todayVendor licence

Open-source entries were read from the GitHub Licenses API on 2026-10-21. A vendor licence carries the date and the page of the edition it was read from, because nobody publishes those as SPDX.Back to the catalogue