The AGPL does not enforce the publishing of the source code when used server side.
Github blog: What’s up with these new not-open source licenses? https://github.blog/2021-03-18-whats-up-with-these-new-not-open-source-licenses/ is mentioning: In response to this pressure, many open-core or dual-license companies, including Confluent, MongoDB, Cockroach Labs, Redis Labs, Timescale, and Graylog moved away from OSI-approved licenses to licenses that are not ‘open source.’ These new ‘source available’ licenses contain restrictions to prevent cloud infrastructure providers from building a service out of their code. Example is MongoDB changing from AGPL to SSPL or Server Side Public License and enforcing the source code to be available rather than just a prominent offer as in the AGPL, as enforcement is difficult, requires expensive litigations. https://www.mongodb.com/blog/post/mongodb-now-released-under-the-server-side-public-license https://www.mongodb.com/licensing/server-side-public-license The PDF with changes to AGPL is on this hyperlink: https://webassets.mongodb.com/_com_assets/legal/SSPL-compared-to-AGPL.pdf Maybe it is the time to update the AGPL to enforce the source to be available when program is served server side? Jean
