---
title: "Permissive or copyleft: two philosophies, two different outcomes"
type: Article
published: 2026-10-18T06:00:00.000Z
url: https://agenticopenfinance.com/blog/license-permissive-vs-copyleft
source: AgenticOpenFinance
---

# Permissive or copyleft: two philosophies, two different outcomes

> Permissive licences such as MIT allow almost any use; copyleft licences such as the GPL require modified versions to stay under the same terms when distributed.

Open source licences are usually grouped into two families.

**Permissive licences**, such as MIT, BSD, ISC and Apache-2.0, allow almost any use, including in commercial and closed products. Their main condition is to keep the copyright and licence notices. As choosealicense puts it, the work, its modifications and larger works that include it may be distributed under different terms and without source code.

**Copyleft licences**, such as the GPL and AGPL, and in a weaker form the LGPL and MPL, add a further condition: if you distribute a modified version, you must make its source code available under **the same licence**. The aim is to keep the code free along the chain of distribution.

Copyleft comes in degrees:
- **Strong**: GPL and AGPL, which reach the combined work.
- **Weak at library level**: LGPL, which leaves a program that only uses the library free to use other terms.
- **Weak at file level**: MPL-2.0, which covers only the licensed files.

For a product team the key question is: do we distribute this software, and if so, are we prepared to publish our own code? The answer decides which family causes less friction. Later episodes take each licence in turn.

This is general information, not legal advice.

**Sources:** [choosealicense.com: Licenses](https://choosealicense.com/licenses/), [choosealicense.com: Choose an open source license](https://choosealicense.com/)
