MIT License, explained

Permissive MIT · MIT-0

MIT is a short permissive licence: you can use, change and sell the code, closed source included, as long as you keep the copyright and licence notice.

Not legal advice. Read the licence text for the exact terms.

What it allows

  • Use the code commercially
  • Modify it and keep your changes private
  • Ship it in closed-source products
  • Sublicense it, and combine it with code under any other licence

What it requires

  • Keep the copyright notice and the licence text in copies of the code (MIT-0 drops even this)

When it matters

Shipping an app (desktop, mobile, on-premises)Allowed, closed source included. Include the licence text and copyright notice, usually in a third-party notices file or an "About" screen.
A hosted service (SaaS)Allowed. Nothing to publish; the notice requirement applies when you distribute the code, and JavaScript sent to browsers counts, so keep notices in your bundles.
Internal useAllowed, with no conditions to meet while the code stays inside your organisation.

Its family: permissive

You can use, change and ship the code in any product, including closed-source ones. You must keep the copyright and licence notice (usually in a third-party notices file); Apache-2.0 also asks you to state changes and keep its NOTICE file.

Questions

Can I use MIT code in commercial software?

Yes. MIT allows commercial use, including in closed-source products. Keep the copyright and licence notice.

Is MIT compatible with GPL?

Yes: MIT code can be included in a GPL project. The combined work is then distributed under the GPL.

Is MIT compatible with Apache-2.0?

Yes. Both are permissive; keep both notices.

Other licences

Published ; awaiting review.