# Permissive License

> A license with few rules. Keep the notice, and use the code as you like.

**Field:** Software Development  
**Category:** Product & Releases  
**Also known as:** Permissive Licence, Permissive Open Source License, Non-Copyleft License

## Think of it like

It is like a free recipe. Cook it, change it or sell the cake. Just keep the cook's name on it.

## Definition

A permissive license is an open source license with very few rules. You may use, change and share the code, even inside a paid, closed product. The main rule is to keep the copyright and license notice with the code. You do not have to share your own changes. MIT, BSD and Apache 2.0 are the best known.

## Example

Lucy's company sells a closed app that uses an MIT library. They keep the MIT notice in the app's credits, and that is all they owe.

## Example code

```json
"license": "MIT"
```

This is the license line in a package.json file. MIT is one with few rules.

## Why it matters

Firms can use this kind of code with little risk, so it spreads far. That is why many big libraries pick one.

## Common mistake

Dropping the notice when you copy the code. Keeping it is the one rule. This is a plain summary, not legal advice.

## Three principles

- **Few rules.** Use it, change it, sell it.
- **Keep the notice.** Copyright and license text stay.
- **No need to share.** Your changes can stay closed.

## Related terms

- [Software License](https://learn.benibix.com/term/development/software-license)
- [Copyleft](https://learn.benibix.com/term/development/copyleft)
- [MIT License](https://learn.benibix.com/term/development/mit-license)
- [Apache License 2.0](https://learn.benibix.com/term/development/apache-license)
- [BSD License](https://learn.benibix.com/term/development/bsd-license)
- [Open Source Software](https://learn.benibix.com/term/development/open-source)

## Told apart from

- [Permissive License vs Copyleft](https://learn.benibix.com/compare/permissive-license-vs-copyleft): People think a permissive license and copyleft are both just open source, so the rules match, and they do not. A permissive license asks you to keep the notice, and your own code can stay closed. Copyleft asks more. If you hand out a changed copy, you must share its code under the same license.

## Taught in

- [Open Model Licenses](https://learn.benibix.com/learn/ai-models-providers/open-model-licenses): AI Models and Providers, 8/13

![A line of licences from the fewest rules on the left to the most on the right. Permissive: MIT, BSD and Apache 2.0, where you only keep the notice. Weak copyleft: LGPL and MPL 2.0, where you share changes to the library or the file. Strong copyleft: GPL, where you share the code of the whole program you hand out. Network copyleft: AGPL, where running it as a web service counts too.](https://learn.benibix.com/diagrams/dev5-license-spectrum.svg)

---

Source: https://learn.benibix.com/term/development/permissive-license
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
