Assume the following:
You are developing a server-side application in the GPL. Now this application serves HTML, not an executable file that runs directly on your computer. This means that the other guy can take the GPL code, adapt it, and not necessarily publish it. I.e. he can create an identical service using your software without violating the GPL. (Although THEN he cannot publish the software itself, i.e. sell)
Not so with AGPL.
This hole in the GPL is often called the "Application Service Provider" hole.
Find “Why AGPL” or “AGPL vs. GPL” or just read this for some real life projects that have GPL issues. MongoDB tries another interesting thing. They want people not to deploy the base database (thatwhy AGPL), but the driver that needs to be associated with the main program is apache 2.0 license, so mongoDB can be used in a commercial application.
A public web application using AGPL is listed on wikipedia .
Karussell Jan 24 '10 at 14:10 2010-01-24 14:10
source share