AGPL would dissuade Google and AWS from using it, and the commercial license would allow the licensee (themselves) to commercialize it?
AGPL would dissuade Google and AWS from using it, and the commercial license would allow the licensee (themselves) to commercialize it?
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.
https://openpath.chadwhitacre.com/2024/widespread-use-of-a-f...
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...