# License > Part of the NocoDB documentation (Self-hosting). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL. URL: https://nocodb.com/docs/self-hosting/license Last updated: 2026-10-03 The NocoDB Sustainable Use License (SUL), its Fair-Code principles, and when you need a commercial license. From **January 09, 2026**, NocoDB changes from **AGPL-3.0** to a **Sustainable Use License (SUL)**, based on **Fair-Code principles**. 👉 View the full license terms [here](https://github.com/nocodb/nocodb?tab=License-1-ov-file#readme) This change has these goals: * Keep NocoDB open and accessible * Protect the work of maintainers and contributors * Make sure that the project can continue for a long time * Give clear and predictable rules for commercial use ## Fair-Code Philosophy **Fair-Code** is a licensing philosophy. It balances: * Open access to source code * Freedom to use, modify, and self-host * Fair payment when someone makes money from the software itself Fair-code does **not** try to restrict use. Its goal is to prevent large-scale commercial exploitation, where someone makes money from the software and does not support the people who build it. ## Sustainable Use License (SUL) The **Sustainable Use License** is one license that uses fair-code principles. ### SUL allows * Free use for individuals and organizations * Full access to source code * Self-hosting without restrictions * Modification for internal or product use ### SUL restricts * Offering NocoDB itself as a paid or managed service * Redistributing NocoDB as part of a commercial platform without a license ## Why This Change ### Sustainability AGPL-3.0 permits commercial reuse at scale, but it does not make sure that maintainers continue to get support. SUL lets us continue to invest in development, documentation and support. ### Community Protection The license protects contributors. Commercial value that comes directly from NocoDB must support the ecosystem. ### Clear Commercial Boundaries SUL clearly defines when you need a commercial license. This makes SaaS and redistribution cases less ambiguous. ## Usage Rights ### Free Use (No Commercial License Required) You can use NocoDB free of charge if you are: * An individual developer * A startup or enterprise using NocoDB internally * Self-hosting NocoDB for internal tools or workflows * Building an application or product that uses NocoDB internally * Using NocoDB for education, research, or non-commercial purposes Internal use is permitted for organizations of all sizes. ### Commercial License Required You need a commercial license if you: * Offer NocoDB as a hosted or managed service * Provide direct NocoDB access to external customers * Resell or redistribute NocoDB as part of a paid offering * Embed NocoDB in a platform where customers interact with NocoDB itself If your business model makes money from **access to NocoDB**, you need a commercial license. If you need help to find out which license you need, contact the NocoDB team. Details [here](/docs/self-hosting/license#how-do-i-obtain-a-commercial-license) ## What Remains Unchanged * Source code remains available * Self-hosting remains supported * Community contributions remain welcome * APIs, integrations, and extensions remain open This is **not** a move to closed source. ## Frequently Asked Questions ### Is NocoDB still open source? NocoDB is **source-available under fair-code principles**. SUL is not OSI-approved, but it keeps transparency, extensibility and community access. ### Can I self-host NocoDB for my company? Yes. Internal self-hosting does not require a commercial license. ### Can I modify NocoDB’s source code? Yes. You can modify NocoDB for internal use or as part of your product. ### What licenses are considered fair-code compatible? These licenses meet fair-code requirements. The ecosystem often refers to them: * **[Sustainable Use License (SUL)](https://github.com/n8n-io/n8n/blob/master/LICENSE.md?utm_source=chatgpt.com)** * **[Business Source License (BSL)](https://mariadb.com/bsl11)** * **[Commons Clause](https://commonsclause.com)** (with an OSI-approved license) * **[Confluent Community License](https://www.confluent.io/confluent-community-license)** * **[Elastic License 2.0 (ELv2)](https://www.elastic.co/licensing/elastic-license)** * **[Server Side Public License (SSPL)](https://www.mongodb.com/licensing/server-side-public-license)** ### Which projects follow fair-code-compatible licenses? Several well-known infrastructure and developer-tool projects use licenses that follow fair-code principles. These include: * **[Airbyte](https://airbyte.com)** (Elastic License 2.0) * **[CockroachDB](https://www.cockroachlabs.com)** (Business Source License) * **[Elastic](https://www.elastic.co)** (Elastic License 2.0) * **[HashiCorp](https://www.hashicorp.com)** (Business Source License) * **[MongoDB](https://www.mongodb.com)** (Server Side Public License) * **[n8n](https://n8n.io)** (Sustainable Use License) * **[Sentry](https://sentry.io)** (Business Source License) These projects use a similar approach: open access for builders, and a license when someone makes money from the software itself. ### Why move away from AGPL-3.0? AGPL-3.0 does not cover large-scale commercial redistribution well. SUL gives clearer and more predictable rules, and keeps openness and community access. ### How do I obtain a commercial license? Contact the NocoDB team through official channels about commercial license options: * Ask in the in-product support chat. * Request details by Email ([cs@nocodb.com](mailto:cs@nocodb.com)). * Book a meeting through [Cal](https://cal.com/nocodb/sales). ## Summary The Sustainable Use License makes sure that NocoDB stays: * Open and accessible for builders * Fair to contributors and maintainers * Sustainable for long-term development For most users, **nothing changes**. For commercial redistribution, the license keeps things fair and lets innovation continue. ## Related * [Fair-Code](https://faircode.io/) --- ## Related pages - [Self-Hosting](https://nocodb.com/docs/self-hosting.md): Self-host NocoDB on your own infrastructure and keep full control of your data. - [Environment Variables](https://nocodb.com/docs/self-hosting/environment-variables.md): Set environment variables to configure a self-hosted NocoDB instance: database, storage, authentication, cache, rate limits and more. - [Purchasing a License](https://nocodb.com/docs/self-hosting/purchase-license.md): Purchase a Business or Scale plan license for your self-hosted NocoDB instance through NocoDB Cloud. - [Activating a License](https://nocodb.com/docs/self-hosting/license-activation.md): Activate a self-hosted NocoDB license with the standard, airgapped or fully offline method. - [White Label](https://nocodb.com/docs/self-hosting/white-label.md): Replace the NocoDB branding on your self-hosted instance with your own product name, logos, favicon, brand color, email branding and support contact. - [Troubleshooting](https://nocodb.com/docs/self-hosting/troubleshooting.md): Find and fix common problems with self-hosted NocoDB: startup, network, SSL, database, attachments and login. - [Migration Guide](https://nocodb.com/docs/self-hosting/migration-guide.md): Migrate a self-hosted NocoDB instance from a non-Postgres database to PostgreSQL so you can activate a paid license without losing data. - [FAQs](https://nocodb.com/docs/self-hosting/FAQs.md): Answers to common questions about self-hosted NocoDB: what the Community Edition includes, upgrades, shifted timestamps and instance details.