Apache 2.0 License
What Is the Apache 2.0 License?
The Apache 2.0 License, formally Apache License, Version 2.0, is a permissive open-source software license that allows people to use, copy, modify, and distribute code, including in commercial products. It includes an express patent license and requires recipients to preserve certain copyright, license, and notice information when redistributing the work.
Published by the Apache Software Foundation in 2004, it is an OSI-approved open-source license. A company can build and sell a proprietary application using Apache-licensed code without generally publishing its own source code. The official Apache License 2.0 text remains the controlling legal document.
What the Apache License 2.0 Lets You Do
Apache 2.0 gives broad rights to individuals and organizations that follow its conditions.
- Use the software privately, internally, publicly, or commercially.
- Copy the original source code or compiled version.
- Modify the code to fix bugs, add features, or adapt it to another product.
- Distribute original or modified code in source or object form, including applications, libraries, containers, firmware, and mobile apps.
- Combine the code with proprietary software and apply different terms to the larger product while retaining required Apache notices.
- Sell products or services that include Apache-licensed components.
Unlike a strong copyleft license, Apache 2.0 does not generally require distributors to release source code for modifications or larger combined works. This flexibility makes it common in reusable libraries and components used during app design and development.
How Apache 2.0 Works When You Use or Redistribute Code
Internal use and redistribution differ. A team using a component only inside its organization usually has fewer practical duties than one shipping software, publishing a package, or providing firmware.
- Identify Apache-licensed components, including transitive dependencies installed by another package.
- Read the component's license files, copyright headers, and any NOTICE file before using it.
- Keep a copy of the Apache 2.0 license text with source or binary distributions that include the component.
- Retain applicable copyright, patent, trademark, and attribution notices.
- Preserve relevant NOTICE file content when the upstream project provides a NOTICE file.
- Mark changed files with prominent statements that you modified them.
- Record the component name, version, source, license, and notices in a software bill of materials, or SBOM.
For example, a company shipping a paid mobile app with an Apache-licensed networking library can keep its code closed. It should still provide relevant license and notice materials through an in-app legal screen, notices page, or package documentation.
Key Terms and Conditions in Apache License 2.0
The copyright grant permits users to reproduce, prepare derivative works, publicly display, publicly perform, sublicense, and distribute the work. The patent grant covers claims contributors can license that are necessarily infringed by their contributions or a contribution combined with the work.
Redistribution conditions require distributors to provide a copy of the license, retain specified notices, identify modified files, and preserve relevant NOTICE content. A NOTICE file passes along attribution and legal notices supplied by the project, not a marketing credit list.
Contributions intentionally submitted to a project are generally provided under the same license unless a contributor clearly states otherwise. The license does not grant permission to use a contributor's name, trademarks, service marks, or branding. It also includes a warranty disclaimer and limitation of liability, so users receive the software largely as-is.
The Patent Grant and Patent Termination Clause
The explicit patent grant is a key distinction between Apache 2.0 and shorter permissive licenses. Each contributor grants recipients a patent license for claims necessarily infringed by that contributor's contribution or its combination with the licensed work. This can reduce uncertainty where a project includes contributor-held patented inventions.
The grant is limited. It does not clear patents held by unrelated third parties or grant rights beyond the license's scope. Apache 2.0 also has a patent termination provision: if a recipient brings certain patent litigation alleging that the licensed work or a contribution infringes a patent, that recipient's patent license can terminate. Organizations facing patent disputes should seek qualified legal advice.
Apache 2.0 License vs. MIT License vs. GPL
No open-source license is universally best for commercial use. The choice depends on adoption, patent language, simplicity, and source-sharing requirements.
| Topic | Apache 2.0 | MIT | GPL |
|---|---|---|---|
| Commercial use | Allowed | Allowed | Allowed |
| Source disclosure for distributed derivative works | Generally not required | Generally not required | Generally required under GPL terms |
| Notice duties | License, copyright notices, and applicable NOTICE content | License and copyright notice | License, copyright notices, and source-related obligations |
| Express patent grant | Yes, with termination provision | Not stated expressly in the standard text | Includes patent-related provisions, varying by GPL version |
| Copyleft requirement | No | No | Yes |
MIT is shorter, while Apache 2.0 provides more detailed patent language. GPL-family licenses are designed to ensure recipients of distributed derivative works receive source code under the same family of terms. Compatibility can depend on license versions, how code is combined, and distribution method.
Common Uses of Apache 2.0 Licensed Software
Apache 2.0 is often selected where maintainers want widespread reuse across open and proprietary ecosystems.
- Programming libraries and software development kits.
- Web frameworks, databases, build tools, and cloud-native infrastructure projects.
- Commercial web and mobile applications that bundle Apache-licensed dependencies.
- Embedded devices and consumer products shipping compiled firmware.
- Tools used by teams building an AI app builder or another software platform with tracked dependencies.
Benefits of the Apache 2.0 License
The license balances broad reuse with clear obligations and can suit projects seeking adoption by businesses and independent developers.
- It permits commercial use and proprietary extensions.
- Its express patent grant offers clearer protection than many minimal permissive licenses.
- It has a lower compliance burden than strong copyleft licenses because it does not generally require source publication.
- It supports open collaboration while letting downstream users choose their product and distribution model.
- Its established wording is familiar to legal, procurement, and compliance teams.
Practical Limits and Common Compliance Pitfalls
Apache 2.0 is flexible, but it does not remove attribution or other legal responsibilities. Problems often arise from weak dependency records and incomplete release processes.
- Omitting the license text, copyright notices, or applicable NOTICE content from a shipped package.
- Removing copyright headers or failing to identify changed files.
- Overlooking transitive dependencies.
- Assuming the license permits use of project names, logos, or trademarks.
- Treating the patent grant as a guarantee against all patent claims or legal risks.
- Assuming every open-source license can be combined with Apache 2.0 without checking compatibility.
A Practical Apache 2.0 Compliance Checklist
Teams should make license review a repeatable release task rather than a last-minute documentation exercise.
- Maintain an inventory of open-source components, versions, licenses, and sources.
- Keep original LICENSE and NOTICE materials in the source repository where practical.
- Include the full Apache 2.0 license text in releases or an accessible legal-notices location.
- Carry forward relevant copyright and attribution notices.
- Review NOTICE files and reproduce required content in the distribution.
- Add clear modification notices to changed Apache-licensed files.
- Generate and retain an SBOM for each release, and update it when dependencies change.
- Ask qualified counsel about high-risk products, patent-sensitive fields, acquisitions, or unclear license combinations.
Choosing Apache 2.0 for Your Own Project
Maintainers may choose Apache 2.0 when they want broad adoption, commercial friendliness, and an express patent grant without requiring downstream derivative works to become open source. It suits widely reused building blocks, particularly when contributors come from different organizations.
A maintainer may prefer MIT when a short license is the priority and detailed patent provisions are not needed. A GPL-family license may fit better when the goal is to require distributors of derivative works to share corresponding source code under reciprocal terms. License selection affects contributors, adopters, and future product options, so decide early and document the choice clearly.
on Emergent today

