Is AGPL 3.0 compatible with MPL 2.0?
AGPL 3.0-licensed code is conditionally compatible with a MPL 2.0 project. Here is what that means for your obligations, conflicts, and distribution.
The license of the code you want to use.
The license you are applying to your project.
The short answer
This combination depends heavily on specific clauses, exceptions, or how the code is used.
Key obligations
Consult legal counsel. This often requires isolating the code in separate modules.
Potential conflicts
Compatibility depends on specific clauses, use cases, or "or later" exceptions.
Distribution notes
May require distributing different parts under separate licenses.
Deep-dive resources
Stop guessing. Start automating.
Modern applications pull in hundreds of transitive dependencies. A manual check can't keep up.
Disclaimer: This tool offers general guidance based on widely accepted open source community norms and does not constitute legal advice. For commercial use, always consult legal counsel or use a dedicated compliance platform like FOSSA to analyze your specific dependency graph.
What this means in practice
GNU AGPL v3.0 is a network copyleft license and Mozilla Public License 2.0 is a weak copyleft license. Whether you can combine them depends on the details: how the code is linked, whether you modify it, and how you distribute it. Treat the obligations below as a starting point and get legal review before a commercial release.
Compliance checklist for AGPL 3.0 → MPL 2.0
- Keep AGPL 3.0 code in clearly separated files or modules.
- Map which obligations apply to your distribution model (binary, SaaS, or internal).
- Document the boundary between AGPL 3.0 and MPL 2.0 code.
- Obtain legal review before a commercial or public release.
About these licenses
GNU AGPL v3.0
LibraryNetwork copyleft. Closes the "SaaS loophole" — offering the software over a network triggers the obligation to share source.
- Type
- Network copyleft
- Patent grant
- Express
- Source sharing
- Combined work + network use
Mozilla Public License 2.0
ProjectWeak, file-level copyleft. You must share changes to MPL-covered files, but the rest of your project can use another license.
- Type
- Weak copyleft
- Patent grant
- Express
- Source sharing
- Modified files only
AGPL 3.0 and MPL 2.0: frequently asked questions
Common questions about combining GNU AGPL v3.0 and Mozilla Public License 2.0.
Is AGPL 3.0 compatible with MPL 2.0?
This combination depends heavily on specific clauses, exceptions, or how the code is used.
Can I use AGPL 3.0 code in a MPL 2.0 SaaS or cloud application?
AGPL 3.0 is a network-copyleft license that closes the "SaaS loophole" — serving the software over a network triggers copyleft, so you cannot re-license it under MPL 2.0.
What are my obligations when combining AGPL 3.0 and MPL 2.0?
Consult legal counsel. This often requires isolating the code in separate modules. May require distributing different parts under separate licenses.