LEGAL DISCLAIMER: This article provides general, informational content for educational purposes only. It is not a substitute for professional legal advice from a qualified attorney. Always consult with a lawyer specializing in intellectual property and software licensing for guidance on your specific situation.
Imagine software licenses are like deeds to a piece of land. A permissive license, like the mit_license, is like buying a plot with no rules; you can build a private mansion, a public park, whatever you want. The more common gnu_general_public_license_(gpl) is like a deed with a covenant: if you build a house on this land, you must give copies of the blueprints to anyone who asks and let them tour the house. This ensures the community benefits from your work. But what if you build that house and only let people access it through a private, remote-controlled bridge? They can use the house, but since they never technically “set foot on the land,” you argue the covenant doesn't apply. This was a loophole for web applications. The Affero General Public License (AGPL) closes this loophole. It's a “super-powered” version of the GPL. The AGPL deed says: if you build a house and let people use it—even over that remote bridge—you still have to give them the blueprints. For software, this “remote bridge” is a computer network. The AGPL ensures that if users interact with your software over a network, they have the right to get the source code.
The story of the AGPL is a direct response to the evolution of the internet itself. It begins with the philosophy of free_software, a movement championed by Richard Stallman and the free_software_foundation_(fsf). The core legal tool of this movement was the gnu_general_public_license_(gpl), first released in 1989. The GPL's central idea is copyleft: if you use GPL-licensed code to create a new program and then distribute that program, you must also license your new program under the GPL, sharing your “derivative work.” For years, this worked well for desktop software. If you sold a program on a floppy disk, you had to include the source code. However, the dot-com boom of the late 1990s created a new way to deliver software: the Application Service Provider (ASP), the ancestor of today's software_as_a_service_(saas). Companies realized they could take powerful GPL code, modify it, and run it on their own servers to power a website. Users would interact with the software through their web browser, but the company never “distributed” the software to them. The code stayed on the company's servers. This became known as the “ASP loophole.” It allowed companies to build proprietary services on the back of free software without contributing their improvements back to the community, which went against the spirit of the GPL. In 2000, to address this, Henry Poole of Affero, Inc. worked with the FSF to create the original Affero General Public License (AGPL). The goal was simple: to extend the sharing obligations of the GPL to network services. In 2007, the FSF officially released the GNU Affero General Public License version 3 (AGPLv3), making it part of the official GNU license family and solidifying its role as the license for a networked world.
The AGPL is not a law passed by Congress. It is a license, which is a legal contract that operates under the framework of U.S. copyright_law (found in Title 17 of the U.S. Code). Here’s how they connect:
This “share-alike” condition is the heart of the license. By choosing to use AGPL-licensed software, you are legally agreeing to abide by its terms. A violation of the license is a breach of contract and an act of copyright infringement.
While born in the U.S., the AGPL is designed for a global stage. Its enforceability relies on international copyright agreements, primarily the berne_convention, which ensures that creative works (including software) are protected across all signatory countries. However, the practical approach to enforcement can vary.
| Aspect | United States | European Union | China |
|---|---|---|---|
| Legal Basis | U.S. Copyright Act (Title 17). Breach of license is copyright infringement. | EU Copyright Directive & national laws. Strong recognition of “moral rights” for authors. | Chinese Copyright Law. Historically weaker enforcement, but rapidly improving, especially for commercial entities. |
| Enforcement Body | Primarily through civil lawsuits filed by the copyright holder or designated organizations (e.g., software_freedom_conservancy). | Often handled by specialized courts. Organizations like the Free Software Foundation Europe (FSFE) are active. | Lawsuits are possible, but out-of-court settlements and public pressure are more common initial steps. |
| Discovery Process | Extensive. Parties can be compelled to produce internal emails, code repositories, and developer notes. | More limited and judge-led. Focus is on the specific evidence presented rather than broad discovery. | Limited discovery. The burden of proof is heavily on the plaintiff to provide clear evidence of infringement. |
| Damages | Can include statutory damages (up to $150,000 for willful infringement) and attorney's fees. | Typically focused on actual damages (lost profits) and an injunction to force compliance. | Damages are often lower, making litigation less financially attractive. The primary goal is usually to force compliance. |
| What it Means for You | A lawsuit in the U.S. can be extremely costly and invasive. Compliance is critical. | Enforcement is robust. German courts, in particular, are known for being friendly to open-source license enforcement. | The risk is growing. A global company cannot ignore AGPL compliance in its Chinese operations. |
To truly understand the AGPL, you need to understand its engine room—the specific clauses that define your rights and obligations. While the full text is complex, its power comes from a few key sections.
This is the standard copyleft provision, similar to the one in the regular GPL. It states that if you take the AGPL-covered code, modify it, and then “convey” (distribute) it, your modified version must also be licensed under the AGPL. You must include clear notices stating that you changed the files and the date of the change. This ensures that the chain of freedom is never broken; improvements made by one user become available to all subsequent users. Example: You download an AGPL-licensed photo gallery script. You add a new feature that automatically tags faces. If you give or sell this improved script to a friend, you must also provide them the full source code under the AGPL.
This clause deals with “object code” or “compiled code”—the version of the program that a computer runs but humans can't easily read. If you distribute the compiled version of an AGPL program, you must also provide access to the “Corresponding Source” code. The license gives you several ways to do this, such as bundling it with the compiled code or providing a written offer, valid for three years, to give the source code to anyone who asks. Example: You take that photo gallery script, compile it into a mobile app, and list it on an app store. You must either include the source code in the app download or place a clear notice in the app's “About” section with instructions on how to obtain the complete source code.
This is the revolutionary clause that defines the AGPL and sets it apart from all other licenses. It is the legal mechanism that closes the “ASP loophole.” The clause states that if you modify the program and run it on a server to let users interact with it remotely over a computer network, you must make your modified source code available to those users. The user's interaction with the program triggers the obligation. What constitutes “interaction”? This is a key legal question, but it's generally understood to mean a back-and-forth exchange of data and commands that uses the core functionality of the AGPL program. Simply visiting a static webpage served by a web server that happens to use an AGPL component in the background might not count. But using a web-based document editor, a project management tool, or a social media platform powered by modified AGPL code almost certainly does. Example: You take AGPL-licensed database software (like early versions of MongoDB). You build a custom commercial software_as_a_service_(saas) analytics platform on top of it. Your customers upload data and run queries through your web interface. Because your users are interacting with the AGPL database over a network, Clause 13 is triggered. You are now legally obligated to provide the complete source code for your *entire* analytics platform to every single user, upon request.
This clause deals with license_compatibility. It allows for adding certain types of limited, additional non-restrictive terms. However, it explicitly states that you cannot add further restrictions that would contradict the license's core freedoms. This is important because it prevents someone from, for example, adding a clause saying “You can't use this software for commercial purposes.”
Unlike a simple car accident case, an AGPL issue involves a unique set of players with different motivations.
Discovering that a critical component of your commercial, proprietary service is licensed under the AGPL can be a terrifying moment for a Chief Technology Officer or founder. Don't panic. Follow a methodical process.
First, determine how the AGPL code is being used. This is not just a legal question; it's a technical one.
If the component is used in a user-facing network service, you must face Clause 13 head-on.
You have several paths forward, each with significant trade-offs.
This is not optional. Do not try to interpret the AGPL on your own based on blog posts. You need an attorney who specializes in open-source software licensing. They can help you assess your specific situation, understand the legal risks, and choose the best strategic option for your business. The cost of a legal consultation is minuscule compared to the cost of a lawsuit or being forced to release your company's core intellectual_property.
If you choose to comply with the AGPL, you'll need to prepare certain “paperwork” for your software distribution.
Pure AGPL court cases are rare because the license is so strong that most companies, when faced with a violation claim, choose to settle or comply rather than risk a court battle. However, several key events and related cases have defined its impact.
MongoDB was one of the most popular databases licensed under the AGPL. Cloud giants like Amazon Web Services (AWS) began offering a “MongoDB-as-a-service” product. They were complying with the AGPL, but MongoDB, the company, felt this was unfair. AWS was profiting from their work without contributing to the database's development. The AGPL, as written, didn't prevent this. In 2018, MongoDB switched its license from the AGPL to a new license they wrote called the server_side_public_license_(sspl). The SSPL is like the AGPL on steroids: it explicitly requires that if you offer the software as a service, you must open source *not only the application itself but all the management software, APIs, and scripts you use to run that service*.
This 2021 lawsuit involved the regular GPL, not the AGPL, but its outcome has massive implications for all copyleft licenses. The SFC sued television manufacturer Vizio, alleging that Vizio's Smart TV firmware used GPL-licensed code without providing the source code. The key legal question was whether a consumer—a purchaser of the TV—had the right to sue for the source code, or if only the original copyright holder could.
The central conflict surrounding the AGPL today is the “Cloud Wars.” Open-source companies (like MongoDB, Elastic, Redis) invest millions in creating powerful software. They use the AGPL hoping to build a collaborative community. Large cloud providers (like AWS, Google Cloud, Microsoft Azure) then take this open-source code and sell it as a managed service, reaping most of the profits without being major contributors to the original code. This has led to a backlash and a fracturing of the open-source landscape. We are seeing:
The principles behind the AGPL are now being tested by new technologies:
The AGPL was a license built for the web era. The next decade will determine if its principles can adapt to the era of AI and decentralization.