AGPL

AGPL The GNU Affero General Public License is a copyleft software license designed to ensure that modifications to network server software are shared with users interacting remotely. Drafted and published by the Free Software Foundation as an adaptation of the GNU General Public License version 3, it extends distribution-triggered obligations to software-as-a-service deployments and web applications. The license has been influential among projects seeking reciprocity in environments dominated by cloud computing providers and internet-hosted services.

Overview

The license was created to close a perceived loophole in existing copyleft licenses by treating remote interaction as a form of distribution. It was proposed in response to trends exemplified by Amazon Web Services, Google, Microsoft Azure and other cloud service providers that offer hosted versions of software without providing corresponding source code changes. The AGPL requires that recipients who interact with modified versions via a computer network be able to obtain source code, aligning its goals with movements led by the Free Software Foundation and proponents like Richard Stallman, Lawrence Lessig, and organizations such as the Electronic Frontier Foundation. Its formulation references international legal frameworks including instruments influenced by Berne Convention principles and interacts with statutory regimes like the United States Copyright Act.

Legal Provisions and Requirements

Key provisions mirror those of the GNU General Public License version 3 while adding network interaction clauses. The license mandates that when a modified program is conveyed or made available to users over a network—situations similar to deployments by entities such as Facebook, Twitter, or GitHub—the distributor must provide source code under the same license terms. It contains sections addressing patent grants and patent retaliation akin to practices in disputes involving corporations like Oracle Corporation, IBM, and Red Hat. The AGPL includes compatibility and termination clauses that have implications for collaborations involving entities such as Apache Software Foundation projects or contributions from developers affiliated with Google LLC and Canonical Ltd.. The license also specifies how to provide corresponding source, with mechanisms comparable to distribution practices used in projects hosted on platforms like SourceForge and GitLab.

Differences from Other Free Software Licenses

The principal distinction is the AGPL’s "network use" clause, which differentiates it from permissive licenses used by projects like Apache HTTP Server or MIT License-licensed software and from copyleft licenses like the GNU General Public License and GNU Lesser General Public License. Unlike the BSD licenses or MIT License, the AGPL requires reciprocal sharing for software offered as a hosted service, influencing choices by companies such as Red Hat and consultancies advising clients like Accenture or Deloitte. Compared to the GPLv3, the AGPL imposes obligations when users interact remotely with modified versions, a concern during adoption debates involving organizations such as Automattic (owner of WordPress.com) and MongoDB Inc. prior to MongoDB’s relicensing. Differences also affect license compatibility scenarios in combined works involving components from projects like Kubernetes, Docker, and OpenStack.

Adoption and Use Cases

The license has been adopted by server-side and web-focused projects seeking to protect community contributions in hosted contexts. Notable adopters include projects associated with GNU Project initiatives and independent projects that aim to prevent proprietary remixes by large providers such as Amazon or Google Cloud Platform. Developers in sectors involving healthcare platforms, financial technology startups, and academic projects affiliated with institutions like Massachusetts Institute of Technology or Stanford University have considered AGPL for protecting public-facing services. Hosting platforms and enterprises evaluating tradeoffs have compared AGPL to alternatives when deploying open source databases, content management systems, and analytics tools—areas where companies such as MongoDB Inc. and Elastic NV have made licensing changes prompting community debate. Some cloud-native projects and software maintained by foundations like the Linux Foundation weigh AGPL adoption against contributor ecosystems and commercial partnerships.

Controversies and Legal Challenges

The AGPL has generated controversy over its reach and compatibility with commercial deployment models. Critics including Red Hat, Debian Project maintainers, and corporate legal teams at firms like Microsoft have questioned whether the network clause creates uncertainty for cloud providers and integrators. High-profile relicensing decisions—such as those by MongoDB Inc. and Redis modules—sparked disputes involving companies like Amazon, Elastic NV, and prompted discussions in venues including Open Source Initiative forums and panels at conferences like FOSDEM and OSC events. Litigation has been sparse but contentious license enforcement actions and settlement negotiations have involved foundations and firms including Software Freedom Conservancy and commercial entities negotiating compliance. Debates also address interactions with patent assertions seen in litigation involving Oracle Corporation and interoperability concerns raised in standards bodies like W3C and IETF.

Category:Software licenses