-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License Clarification #3850
Labels
Comments
I agree totally, a clarification would be great for startups that just want to use the product for some of its features on their own products. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While exploring version 2 of the software, I noticed a shift in the project license from GPLv3 to SSPL-1.0. However, the issue highlighted in this GitHub issue persists.
The LICENSE file states:
However, the SSPL-1.0 license does not mandate that all projects utilizing the software must be open source. It specifically targets scenarios where the project is offered as a SaaS. This approach was notably adopted by MongoDB to address services like AWS, which offered MongoDB as a SaaS, rather than commercial projects utilizing MongoDB internally. This distinction is why MongoDB designed SSPL based on the GPL rather than the AGPL.
Therefore, it appears that under SSPL, one is permitted to use the unmodified docker container and integrate the self-hosted service with their own software or website. However, creating a direct competitor to Browserless.io without open-sourcing the competing service's code is prohibited.
If Browserless aims to prevent commercial exploitation of its software without financial compensation, that's entirely justifiable. However, employing a license that allows for commercial use, while simultaneously issuing statements that suggest otherwise, generates confusion. A clarification on this matter would be greatly appreciated.
The text was updated successfully, but these errors were encountered: