This page answers most of the common queries that we receive about our license, licensing use of the software, and packaging or redistributing it. For non-licensing questions, please see our General Contact FAQ.
Please check the following list to see if any of the descriptions match your situation. Each one is described in more detail in the following paragraphs.
If none of the above addresses your query, please check the resources at the bottom of this page for general information.
Here are the detailed answers for each of the questions above.
See the following links; 2.0 is the current version while 1.1 and 1.0 are older versions that the ASF no longer use:
Apache License 2.0: http://www.apache.org/licenses/LICENSE-2.0.txt
Apache Software License 1.1: http://www.apache.org/licenses/LICENSE-1.1.txt
Apache Software License 1.0: http://www.apache.org/licenses/LICENSE-1.0.txt
Describing legal documents in non-legalese is fraught with potential for misinterpretation. Notwithstanding the text that follows, the actual text of the license itself is legally binding and authoritative.
That said, here's what the Apache license says in layman's terms:
It allows you to:
freely download and use Apache software, in whole or in part, for personal, company internal, or commercial purposes;
use Apache software in packages or distributions that you create.
It forbids you to:
redistribute any piece of Apache-originated software without proper attribution;
use any marks owned by The Apache Software Foundation in any way that might state or imply that the Foundation endorses your distribution;
use any marks owned by The Apache Software Foundation in any way that might state or imply that you created the Apache software in question.
It requires you to:
include a copy of the license in any redistribution you may make that includes Apache software;
provide clear attribution to The Apache Software Foundation for any distributions that include Apache software.
It does not require you to:
include the source of the Apache software itself, or of any modifications you may have made to it, in any redistribution you may assemble that includes it;
submit changes that you make to the software back to the Apache Software Foundation (though such feedback is encouraged).
It depends entirely on which versions of our software you are talking about - you should adhere to the version of our license that covered the software in question. It should be exceedingly rare to come across version 1.0, and all active products should have had a version released under the Apache License 2.0. Feel free to contact the relevant project if you are unable to find an AL 2.0 version of their software.
While the core Apache developed code will be under one of the Apache licenses, other third party works may have been included and their license text may have been added to the Apache projects' LICENSE or NOTICE files. Alternatively, they may be available separately.
'Apache', 'Apache Software Foundation', the multicoloured feather, and the various Apache project names and logos are either registered trademarks or trademarks of The Apache Software Foundation in the United States and other countries. Please see our Trademark Policy for details of how to use Apache project trademarks or our helpful site map of trademark resources.
Yes. All software developed by all projects of The Apache Software Foundation is freely available without charge from the Foundation's Web sites. This is specified in the Foundation's Articles of Incorporation and explained in more detail about why our software is always free (no charge).
No. We do not distinguish between personal, internal, or commercial use of our software, nor does the ASF charge for any of them. Packaging and redistribution of any of it is subject to the terms of our license , however.
Please see the ASF Exports Classifications and Source Links page.
Certainly. Version 2.0 of the license was designed to be reusable, and often has been reused by parties other than the ASF.
Yes, you are allowed to re-use and modify them. You just can't hold the ASF legally responsible if these documents are not exactly what you intend them to be. We recommend that you obtain your own legal advice so you know exactly what you are getting yourself into.
And if you adapt these agreements for your purposes, you have to make sure that the phrase 'Apache Software Foundation' or any confusingly similar references or parts that specifically refer to the Apache organisation do not appear in your version of the agreements (except to note that your version is derived and differs from the original provided by the ASF).
Yes, you are allowed to re-use and modify it. You obviously can't hold the ASF legally responsible if this document, with or without changes, is not exactly what you intend it to be. We recommend that you obtain your own legal advice so you know exactly what you are getting yourself into.
And if you adapt the agreement for your purposes, you have to make sure that the phrase 'Apache License', 'Apache', or any confusingly similar references or parts that specifically refer to the Apache organization do not appear in your version of the license (except to note that your version is derived and differs from the original provided by the ASF).
Absolutely -- subject to the terms of the Apache license, of course. You can give your modified code away for free, or sell it, or keep it to yourself, or whatever you like. Just remember that the original code is still covered by the Apache license and you must comply with its terms. Even if you change every single line of the Apache code you're using, the result is still based on the Foundation's licensed code. You may distribute the result under a different license, but you need to acknowledge the use of the Foundation's software. To do otherwise would be stealing.
If you think your changes would be found useful by others, though, we do encourage you to submit them to the appropriate Apache project for possible inclusion.
In a word, no. You may, however, use phrasing such as 'based on Apache', 'powered by Apache', or 'based on Apache technology'. You must not use the Foundation's marks in any way that states or implies, or can be interpreted as stating or implying, that the final product is endorsed or created by the Apache Software Foundation. For example, it would be acceptable to use a name like 'SuperWonderServer powered by Apache', but never a name like 'Apache SuperWonderServer'. This is similar to the distinction between a product named 'Microsoft Burp' and 'Burp for Microsoft Windows'.
You may similarly identify the specific Foundation project whose code you're using, such as with 'based on Apache Xerces' or 'powered by Apache Tomcat technology'.
If you wish to use a name including any of the Foundation's marks, such as the word 'Apache', it's best to ask our permission first. Please see our Trademark Policy for more details.
No. You can keep your changes a secret if you like. Maybe your modifications are embarrassing, maybe you'll get rich selling those improvements. Whatever. But please seriously consider giving your changes back! We all benefit when you do.
Yes, you may translate the license text into your local language. However , any such translated text is only for the convenience of understanding, and is not legally binding. Only the English-language version of the license, which you must continue to include in your packaging , is authoritative and applicable in case legal interpretation is required.
From the Free Software Foundation website:
This is a free software license, compatible with version 3 of the GPL. Please note that this license is not compatible with GPL version 2, because it has some requirements that are not in that older version. These include certain patent termination and indemnification provisions.
This is a four part question:
Apache projects - that is, projects formally hosted at the ASF - always use the Apache license for the aggregate work that they distribute. We have listed a number of previously answered questions about how Apache projects license their code.
No. See the Apache Software Foundation licenses page for more details.
Only if their employment situation necessitates that a CCLA be signed. See section 4 of the ICLA for details.
Committers must sign an ICLA. They make an individual claim that the code that they contribute is theirs to license. Reviewing their ICLA against their employer's ownership interests, applicable state and national law, and specific aspects of their employment contract and business policies will reveal that they can or cannot make that claim regarding any particular commit to whichever particular project they are committing in.
The CCLA is a backup document that the committer/ICLA signer may use to eliminate all of the ambiguity between all these conflicting laws, contracts, policies and job assignments. We've never required it, many committers are confident of their individual representations under the ICLA, many other committers find it reassuring that their company has backed up their own ICLA with this umbrella document.
It is the ICLA signatory's call if it is required, but it isn't exactly an easy call for many committers employed in the IT/Software industry.
Finally, see section 8 of the ICLA, which requires signers to notify the Foundation when their status changes in ways that may require this to be reassessed.
If you have questions about The Apache Software Foundation, its projects, or its software, we recommend the following link for more information or assistance:
If you have a question specifically about the Apache license or distribution of Apache software, and it has not been answered by this page, please contact the Legal Affairs Committee.