SPDX Identifier: SSPL-1.0
- SSPL is not OSI-approved open source
- Redistribution in source form
- Notice obligation: Retain the copyright/license information
- When modifying: The same obligations as AGPL-3.0
- Redistribution in binary form
- Notice obligation + provision of source code
- The same obligations as AGPL-3.0
- Additional obligations when providing SaaS
- Disclose the SSPL software + all software needed to operate the service
- Including infrastructure management tools, operations scripts, etc.
SSPL is a “Source Available” license that has not been approved by the OSI (Open Source Initiative). When providing commercial SaaS, it carries an obligation to disclose virtually all service infrastructure, so it cannot be used in any of SK Telecom’s products and services.
What Is SSPL?
SSPL (Server Side Public License) is a license that MongoDB created in 2018 to prevent cloud providers such as AWS from offering MongoDB as a commercial service.
Differences from AGPL-3.0
| Item | AGPL-3.0 | SSPL |
|---|---|---|
| OSI approval | Approved | Rejected |
| Network service | Disclose AGPL code + linked code | Disclose the entire service operation infrastructure |
| Disclosure scope | Application layer | Down to infrastructure management tools |
SSPL modifies AGPL-3.0 Section 13 to require, when providing a service, the disclosure of all of the following:
- The SSPL software itself
- All software that interacts with the service
- The management software needed to operate the service
- Infrastructure provisioning, monitoring, backup tools, etc.
Major Use Cases
MongoDB’s License Change
- Before October 2018: AGPL-3.0
- After October 2018: SSPL-1.0
Other Projects Adopting SSPL
- Graylog
- Some NoSQL databases
Why Did the OSI Not Approve It?
In 2019, the OSI decided not to recognize SSPL as open source:
- Overly broad disclosure requirement: The scope of “everything needed to operate the service” is unclear
- Violation of non-discrimination: It effectively prohibits a specific business model (SaaS)
- Restriction on free use: Providing a commercial cloud service is practically impossible
Reasons for the Usage Restriction
If you provide a service using SSPL software, you must disclose all of the following:
- The source code of the SSPL software
- The service application code
- Kubernetes configurations
- Terraform scripts
- Monitoring tools (Prometheus, Grafana, etc.)
- CI/CD pipelines
- Backup and recovery systems
Since this would require disclosing all of SK Telecom’s core infrastructure information, its use is not possible.
Alternatives
If you need to use SSPL software, please consider the following alternatives.
MongoDB
- MongoDB Community Edition: SSPL
- Alternative 1: MongoDB Atlas (MongoDB’s official cloud service)
- Alternative 2: PostgreSQL + JSON features
- Alternative 3: FerretDB (a MongoDB-compatible AGPL project)
Graylog
- Graylog Open Source: SSPL
- Alternative 1: Elasticsearch + Kibana (Elastic License 2.0, separate review required)
- Alternative 2: Grafana Loki (AGPL-3.0)