Permissive · keep the notices
MIT, in plain English.
TL;DR
You can use it, change it, self-host it and sell it. Keep the original copyright and license notice with copies of the code. You don’t have to publish your changes. The authors don’t promise it will work.
Source: Open Source Initiative · MIT 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. Include the copyright and license notice.
What do I need to do?
- Keep the original copyright and license notice in copies or substantial portions of the code.
- The software comes without a warranty from its authors.
“Permissive” means you have broad reuse permission with a small set of conditions. MIT does not require your own changes to be open source.
A real-world example
You deploy an MIT project for your team and customise it. You can keep those changes private. If you give someone your version, include the original copyright and license notice.
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 ↗