3 ms·
The short version is that the AGPL is like the GPL, except any code that you use to run public services is considered "distributed" in the same way that it woul
by _delirium 16y ago
The short version is that the AGPL is like the GPL, except any code that you use to run public services is considered "distributed" in the same way that it would be if you had distributed it on a CD-ROM. Think of your thin-client AGPL-using webapps as if they were thick-client GPL-using desktop apps, and the requirements are roughly the same.
That still leaves the same grey areas as in the GPL, which seems to be some of your questions: what exactly counts as an API, what counts as a derivative work versus a separate piece of software that communicates, etc.
The intention though is usually to require you to AGPL any SaaS you build on top of the original AGPL'd code, the same way the GPL would require you to GPL any thick-client app you built on top of GPL'd code. That effect is usually intentional, because AGPLing code is sometimes used as an alternative to not releasing it at all. For example, Dropbox keeps their source code closed, partly to keep someone from being able to build a competing SaaS on it. Some people choose to AGPL it instead, as an in-between sort of route: people can now build a competing SaaS on your code, but they have to open-source any improvements, which you can then incorporate back into your own service, so at least they can't leapfrog ahead of you using your own code.
I'd recommend that if your goal is to build a SaaS that has significant portions of its source code stay closed-source, you probably shouldn't use AGPL'd code.