Contents
What do you need to know about the AGPL license?
The AGPL V3 license is a strong copyleft license that enforces open source on all components derived from any previous work. It closes the server-side loophole, where the source code isn’t made available if the software isn’t released. AGPL defines a user as anyone who accesses the server-side application if it is public-facing.
Can a GPL code be distributed alongside an app?
The (A)GPL work cannot be distributed alongside the final application even as a separate app (eg, putting them into the same archive or repository), although it’s fine to provide instructions on where to find the GPL work and how to use it with your app. AGPL is the same as GPL; therefore if your app is using AGPL code it has to be AGPL licensed.
Can you use AGPL with closed source applications?
Copyleft is the opposite of copyright, enforcing the rights to use, modify, and redistribute any source code that has a copyleft license like the GPL. Can you use AGPL with closed source applications? The AGPL V3 license is a strong copyleft license that enforces open source on all components derived from any previous work.
What does AGPL do on top of GPL?
What AGPL does on top of GPL is the redefinition of user. For GPL programs running on your server, you are the user, for AGPL, the real users of the app are the users of your website or service. Therefore you are distributing the app if someone other than you is using it. And that of course implies all the standard GPL requirements.
Can a GPLv3 modified version of AGPL be used?
Any modified versions of the GPLv3 work will have to use the AGPLv3 license. AGPL due to its radical open source licensing is currently only used in less than 1% of open source projects .
How does the copyleft principle work in the AGPL license?
In the standard GPL license, the reciprocity clause comes into effect whenever a developer releases software. The copyleft principle intends to make all of the source code available to the wider open source community. With AGPL, software teams can ensure all changes to the codebase becomes available to the public, even on server-side applications.
Is the AGPL based on the GPL or the LGPL?
The AGPL is based on the GPL, not the LGPL. It does not contain any linking exceptions, and any work using AGPL code (linked or otherwise, modified or not) must also be AGPL licensed and distributed. Using separate processes can circumvent the (A)GPL, but this is murky ground.
When do I need to do an AGPL audit?
Before releasing any updated or modified software, organizations need to conduct a complete license compliance audit, and doing this during every stage of the project can avoid issues in the future. One license teams should look into is the GNU Affero General Public License (AGPL). What is AGPL?
Is the AGPL the same as the GPL?
Small wonder, then, that some companies that license their code under the AGPL internally describe it as the “Amazon GPL.” AWS, for example, has made orders of magnitude more money from MySQL than MySQL AB (and now Oracle) ever hoped to make (through RDS).
Do you have to license derivatives under AGPL?
As per usual with GNU licenses, you must license derivatives under AGPL. It provides the same restrictions and freedoms as the GPLv3 but with an additional clause which makes it so that source code must be distributed along with web publication.
When is AGPL software considered a derived work?
If your end application depends on the external process, such that it wouldn’t function properly without it, then it would be considered a derived work of the AGPL software.
How can I use GPL software in a commercial?
Modification of [L]GPL’d components suggests contribution back to the creator/maintainer. I’m not clear on how that affects your product’s licensing. Some points about the “internal” use: 1. careful if you hire contractors and give them the software. That might be distribution. 2. Tell your employees not to distribute the software.