License Comparison
Quick Comparison Table
| Feature | FFP v2.0 | MIT | Apache 2.0 | GPL v3 | BSD 3-Clause |
|---|---|---|---|---|---|
| Permissions | |||||
| Commercial Use | ✅ | ✅ | ✅ | ✅ | ✅ |
| Modification | ✅ | ✅ | ✅ | ✅ | ✅ |
| Distribution | ✅ | ✅ | ✅ | ✅ | ✅ |
| Private Use | ✅ | ✅ | ✅ | ✅ | ✅ |
| Patent Grant | ✅ | ❌ | ✅ | ✅ | ❌ |
| Conditions | |||||
| Include License | ✅ | ✅ | ✅ | ✅ | ✅ |
| Include Copyright | ✅ | ✅ | ✅ | ✅ | ✅ |
| State Changes | ❌ | ❌ | ✅ | ✅ | ❌ |
| Disclose Source | ❌ | ❌ | ❌ | ✅ | ❌ |
| Same License (Copyleft) | ❌ | ❌ | ❌ | ✅ | ❌ |
| Limitations | |||||
| Liability | ❌ None | ❌ None | ❌ None | ❌ None | ❌ None |
| Warranty | ❌ None | ❌ None | ❌ None | ❌ None | ❌ None |
| Trademark Use | ❌ Not granted | ❌ Not granted | ❌ Not granted | ❌ Not granted | ❌ Not granted |
| Patent Retaliation | ✅ | ❌ | ✅ | ✅ | ❌ |
Detailed Comparisons
FFP vs MIT License
Similarities:
- Both are permissive licenses
- Both allow commercial use
- Both require license and copyright notice preservation
- Both disclaim warranties and liability
- Neither requires source code disclosure
Differences:
- Patent Grant: FFP includes an explicit patent grant; MIT does not
- Patent Retaliation: FFP terminates patent rights for patent litigation; MIT has no patent provisions
- License Length: FFP is more detailed with explicit definitions and terms
- Attribution: FFP explicitly requires preservation of all attribution notices
- No Lockdown: FFP explicitly prohibits measures that restrict recipients' rights
When to choose FFP over MIT: When patent protection is important to you or your project.
When to choose MIT over FFP: When you want maximum simplicity and the most widely recognized permissive license.
FFP vs Apache License 2.0
Similarities:
- Both are permissive licenses with explicit patent grants
- Both include patent retaliation clauses
- Both allow commercial use and modification
- Both require license and copyright notice preservation
- Both disclaim warranties and liability
Differences:
- State Changes: Apache 2.0 requires documenting changes; FFP does not
- NOTICE File: Apache 2.0 has specific NOTICE file requirements; FFP does not
- Reinstatement: FFP has a more flexible cure provision for violations
When to choose FFP over Apache 2.0: When you want simpler compliance requirements.
When to choose Apache 2.0 over FFP: When you want a widely-recognized, legally vetted license with stronger trademark protections.
FFP vs GPL v3
Similarities:
- Both include patent grants and retaliation provisions
- Both allow commercial use and modification
- Both disclaim warranties and liability
Major Differences:
- Copyleft: GPL v3 is copyleft (derivative works must be GPL); FFP is permissive
- Source Disclosure: GPL v3 requires source code disclosure; FFP does not
- Same License: GPL v3 requires derivatives to be GPL-licensed; FFP allows relicensing
- Complexity: GPL v3 is much longer and more complex
When to choose FFP over GPL v3: When you want to allow proprietary derivatives or minimize compliance burden.
When to choose GPL v3 over FFP: When you want to ensure all derivatives remain open source.
FFP vs BSD 3-Clause
Similarities:
- Both are permissive licenses
- Both allow commercial use and modification
- Both require copyright and license preservation
Differences:
- Patent Grant: FFP includes an explicit patent grant; BSD 3-Clause does not
- Patent Retaliation: FFP has patent retaliation; BSD 3-Clause does not
- Endorsement: BSD 3-Clause has an explicit non-endorsement clause; FFP has it too (Section 7)
- No Lockdown: FFP explicitly prohibits locking down recipients' rights; BSD 3-Clause does not
When to choose FFP over BSD 3-Clause: When patent protection matters.
When to choose BSD 3-Clause over FFP: When you want maximum brevity and recognition.
Summary: Is FFP Right for Your Project?
Choose the FFP License if you want a permissive license that:
- Allows maximum freedom for users and contributors
- Includes explicit patent protection
- Has a minimal compliance burden
- Protects against patent litigation abuse
- Is clear and readable
FFP v1.0 vs v2.0
| Aspect | v1.0 | v2.0 |
|---|---|---|
Source Form / Object Form definitions | ❌ Absent | ✅ Added (Section 0) |
Legal Entity definition | ❌ Absent | ✅ Added (Section 0) |
Effective Date definition | ❌ Absent | ✅ Added (Section 0) |
| Patent clause covers threats | ❌ Filed suits only | ✅ Filed + threatened (Section 3.2) |
| DRM/TPM explicitly named in No-Lockdown | ❌ Generic "measures" | ✅ Explicitly named (Section 4.3) |
| AI/ML Training permission | ❌ Not addressed | ✅ Section 4.5 |
| Contributor representation/warranty | ❌ Absent | ✅ Section 5 |
| Indemnification clause | ❌ Absent | ✅ Section 11 |
| Export Controls notice | ❌ Absent | ✅ Section 12 |
| Entire Agreement clause | ❌ Absent | ✅ Section 15 |
| Version upgrade path | ❌ Absent | ✅ Section 16 |
| Governing Law / Dispute Resolution | ❌ Absent | ✅ Section 17 |
| Jurisdictional carve-outs (warranty/liability) | ❌ Absent | ✅ Sections 9 & 10 |
| Cure window specified (reinstatement) | ❌ Unspecified | ✅ 30-day cure window (Section 8.2) |