Skip to content
BENIBIX Learn

MIT License vs Apache License 2.0

The MIT License and the Apache License 2.0 both let you use, change and sell code with few rules. The main gap is patents. Apache adds a written promise that the authors will not sue users over patents in the code. It also asks you to keep a NOTICE file and mark changed files. MIT is shorter; Apache gives more legal cover.

Development🚀 Product & Releases

MIT License

A short open source license. You may do almost anything if you keep the notice.

The MIT License is a short open source license with very few rules. You may use it, change it, sell it and put it in closed apps. The one rule is to keep the copyright and license notice with the code. It also says the code comes with no warranty. It is one of the most used licenses, and React and Node.js use it.

Example
Jack puts the MIT License on his small date library. A big company uses it in a paid app, which is fine as long as his notice stays in.
Why it matters
It is simple and lets anyone use your code. That makes it easy for others to pick up.
Full entry
Development🚀 Product & Releases

Apache License 2.0

An open source license like MIT. It adds a promise about patents.

The Apache License 2.0 is an open source license much like MIT. It lets you use, change and sell the code. It adds a patent grant, a promise that the authors will not sue users over patents in the code. You must keep the notices and say which files you changed. It was published in 2004 by the Apache Software Foundation. Kubernetes and Android use it.

Example
Emma's company picks Apache 2.0 for its new tool. Big firms feel safer adopting it, because the patent grant protects them.
Why it matters
Companies worry about patent lawsuits. The patent grant makes Apache code easier for them to use.
Full entry

In one line

MIT License
A short open source license. You may do almost anything if you keep the notice.
Apache License 2.0
An open source license like MIT. It adds a promise about patents.