One big reason we don't use AGPL at Sentry is that we want companies to be able to self-host individually (just not start a competing SaaS), and many have a blanket ban on AGPL.
Another possibility is to make it available under several licenses: AGPL + free but restricted licence.
[0] https://openpath.chadwhitacre.com/2024/widespread-use-of-a-f...
https://openpath.chadwhitacre.com/2024/widespread-use-of-a-f...
Sounds like their own self-created problem.
https://opensource.google/documentation/reference/using/agpl...
For example, people seem to have the impression that if you host something like an AGPL email validation service that just has an API to request a check for an email and then connects via SMTP, which another service calls, that you “infect” your product that even uses that API.
I get that if you change the service and/or expose it publicly you have to make the changes available, but it seems misunderstood.
Even personally, years ago I relicensed all my GPL code to BSD/MIT because I wanted people to use my software. I’m not there to tell them that they are wrong about their license restrictions.