> SSPL includes most of the AGPLv3 ... but modifies its provisions for software that is conveyed over a network—requiring that anyone who offers the functionality of SSPL-licensed software to third-parties as a service must release the entirety of their source code, including all software, APIs, and other software that would be required for a user to run an instance of the service themselves, under the SSPL. In contrast, the AGPL v3's equivalent provision covers only the licensed work itself.
This just goes beyond anything reasonable IMO, they set terms that no-one could comply with so you need to negotiate to have it under a different license.
And why is that unreasonable?
- all your changes to the product
- all infrastructure code you use to deploy the product for your customers
- all billing code you use to bill for the product
But I would not expect you to release code for e. g. services based on other products (open source or otherwise), or your whole billing stack, or your internal services you use for customer support for example. Just the code that you use with my particular product.
Now, SSPL is a bad license for numerous reasons (many of the concerns in the OP article are valid!) and this is why I've decided against it on my project [1], but I think the basic premise of it is completely valid.
[1]: https://lunni.dev/, licensed AGPL-3.0
SSPL also deals with selling the software under license as a service, but it does not define _exactly_ what is included as pertaining to being SaaS. It only gives you some examples. This means the actual test can only be determined in a civil suit.