commonsclause.com

What It Is

Commons Clause is a licensing condition added on top of an existing open-source license, rather than a developer tool or SaaS product in the traditional sense. Its core mechanism is to preserve most of the permissions granted by the original license while explicitly withholding the right to “Sell the Software.” The site positions it as a source-available approach for projects that do not want to go fully closed source but need to address third parties directly commercializing, packaging, hosting, or selling the software itself.

Core Capabilities and Licensing Boundaries

In terms of function and use case, Commons Clause mainly serves software license governance. It allows users to view the source code, modify it, redistribute it, embed it into larger products, and build and sell applications, plugins, and tools on top of it, including charging for SaaS offerings. The key restriction is that users may not sell products or services that “substantially” rely on the software’s own functionality without adding sufficient value. The FAQ uses Redis Graph as an example: an application built on top of it can be sold, but renaming it and offering it directly as a similar SaaS product is not allowed.

Open-Source Status, Ecosystem, and Documentation

The website clearly states that Commons Clause is not an open-source license under the OSI definition and should not be described as open source; it is a source-visible license. It can be layered on top of common licenses such as Apache, BSD, and MIT, and it is also compared with AGPL, GPL, CC-NC, and proprietary closed-source licenses. The documentation is relatively well written, and the FAQ covers key issues such as whether it is open source, the impact of license changes, SaaS usage, commercial sales, and the limitations of AGPL. However, it remains a legal text at its core, and professional legal advice is still recommended for complex commercial scenarios.

Pricing and Services

The collected content does not provide any information on pricing, payment methods, APIs, SDKs, commercial support, or hosted services. It is more like a publicly released license text and explanatory page than a developer product billed by seat or usage.

Pros, Cons, and Best-Fit Users

Its advantages are that the terms are short and the goal is clear. Compared with going fully closed source, it preserves more rights for developers while giving maintainers a transitional way to prevent commercial free-riding. The drawbacks are that it is controversial in the community, and the fact that it is “not open source” can affect enterprise compliance, community contributions, and user trust. It is suitable for projects facing pressure from cloud providers or third parties directly selling their core functionality. It is not suitable for teams committed to a strict open-source definition or requiring reuse without commercial restrictions.

Access from China and Alternatives

The source content does not provide information about access from China, payment, or local services, so its China accessibility status is unknown. Alternative licensing paths to consider include Apache 2.0, MIT, BSD, GPL, AGPL, CC-NC, or a fully proprietary license. The right choice depends on the project’s trade-offs between openness, commercialization, and community governance.