The reason for the creation of AGPL is not “limiting” commercial use. It’s there, so that a company commercially using your AGPL project is also required to publish its changes under AGPL, even if the only way they “distribute” the software is as a Application Service Procider (SaaS company). Because under regular GPL, this case wasn’t covered, so big companies could use your code, modify it, offer it as a SaaS product and NOT publish their changes unter a free license.
AGPL specifically exists, so the rules around commercial SaaS use are clear – so I’d argue it’s the opposite of “limiting commercial use”.
The reason for the creation of AGPL is not “limiting” commercial use. It’s there, so that a company commercially using your AGPL project is also required to publish its changes under AGPL, even if the only way they “distribute” the software is as a Application Service Procider (SaaS company). Because under regular GPL, this case wasn’t covered, so big companies could use your code, modify it, offer it as a SaaS product and NOT publish their changes unter a free license.
AGPL specifically exists, so the rules around commercial SaaS use are clear – so I’d argue it’s the opposite of “limiting commercial use”.
See: https://yairudi.com/understanding-asp-loophole/