[vrtx0]

Projects that change from Apache or GPL-like licenses to SSPL are still open source. This doesn’t mean you have to release your source code if you use these projects — only if you start selling a hosted platform that offers the software as a service. Every company I’ve seen do this was been backed into a corner by Amazon, who almost never contributes to these projects. This is nothing more than Amazon trying to kill these projects by causing fragmentation.

*Yes, I’ve read the OSI link AWS-fans always refer to.

[SXX]

Have you read SSPL? It's literally apply restriction to SaaS that impossible to comply with.

Also it's not some "everyone, but Amazon license". Terms they use are very fuzzy and can easily apply to more than just SaaS companies.

If Elastic wanted to stay open source they would use BSL: proprietary for N years and then code became GPL / APLv2.

Anti-SaaS clause of SSPL is here:

   > The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
   
   > The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

https://www.mongodb.com/licensing/server-side-public-license