The point of the AGPL is to require sharing of modifications to the software when that software is used in a service. If you're using an unmodified binary, then

The point of the AGPL is to require sharing of modifications to the software when that software is used in a service. If you're using an unmodified binary, then you haven't made any changes to the software. You won't be obligated to share changes if the changes don't exist, so you could use the unmodified binary internally or externally. The AGPLv3 has a lot to say about patents, which is enough to scare off many companies from software that uses the AGPLv3, but I believe it won't be triggered if you never make any changes in the first place (and are therefore presumably not a 'contributor'). AGPLv3: https://www.gnu.org/licenses/agpl-3.0.en.html https://www.gnu.org/licenses/agpl-3.0.en.html See also https://en.wikipedia.org/wiki/Affero_General_Public_License https://en.wikipedia.org/wiki/Affero_General_Public_License , https://softwareengineering.stackexchange.com/questions/107883/agpl-what-you-can-do-and-what-you-cant#comment202259_107931 https://softwareengineering.stackexchange.com/questions/1078...