Permissive · notices and patent terms
Apache 2.0, in plain English.
TL;DR
You can use, change and sell it, including in closed-source products. When sharing copies, include the license, keep required notices and mark changed files. It includes a contributor patent grant with conditions, but no trademark permission or warranty.
Source: Apache Software Foundation · Apache 2.0 license text ↗What can I do with it?
- Self-host it for yourself
- Yes.
- Use it for your business
- Yes, including paid products.
- Change the code
- Yes.
- Keep your changes private
- Yes.
- Share or sell copies
- Yes, with the required license, notices and change labels.
What do I need to do?
- Give recipients a copy of the license and retain applicable notices.
- Mark files you changed. Preserve required attribution from a NOTICE file, if one is supplied.
- The patent grant has conditions, including termination for certain patent lawsuits.
The license does not grant use of the project’s trademarks. Software is supplied without a warranty.
A real-world example
You customise an Apache 2.0 app and sell copies. Include its license, preserve applicable notices and record changed files; your modifications can have different license terms.
The code license and the hosting bill are separate.
A license tells you what you can do with the code. It doesn’t make Cloudflare, domains, email delivery or other services free. Check the project’s hosting notes as well.
This is a general explanation. The repository’s exact license, version, exceptions and package-specific terms govern. Other packages, dependencies and images can have different licenses.
Read the complete license terms ↗