Why We Chose EUPL-1.2: The European Open Source License
When we open-sourced NeoDonkey, we had a choice: MIT, GPL, Apache, or EUPL. Most projects default to MIT or Apache because they're "business-friendly." We chose EUPL-1.2, the European Union Public License. Here's why.
The License Nobody Knows
EUPL-1.2 is the official open-source license of the European Union. Created by the EU Commission in 2007 and updated in 2017, it's designed to be:
- Copyleft, Derivative works must be open source
- Compatible, Works with GPL, AGPL, and other major licenses
- Legally robust, Written for European law, not American
- Multilingual, Official versions in 23 EU languages
And yet, most developers have never heard of it. The open-source world is dominated by American licenses: MIT (Massachusetts), Apache (California), GPL (Boston). EUPL is the European alternative that nobody talks about.
Why Copyleft Matters for ERP
MIT and Apache licenses allow anyone to take your code, modify it, and sell it as proprietary software without contributing back. This is called "proprietization", and it's how open-source projects get captured.
Consider what happened to MongoDB (SSPL), Elasticsearch (SSPL), and Redis (RSAL). All three started as open source, got popular, then had to change licenses when cloud providers started offering them as proprietary services. The open-source community lost.
EUPL-1.2 prevents this. If someone modifies NeoDonkey and distributes it, their modifications must also be EUPL-licensed. They can't take our work, add a proprietary wrapper, and sell it without giving back.
"EUPL is not anti-business. It's pro-contribution. If you benefit from the commons, you contribute to the commons."
European Legal Certainty
American licenses are written for American law. When there's a dispute, courts interpret them through the lens of US copyright law, UCITA, and state-specific regulations.
EUPL is designed for European legal systems:
- References European copyright directives
- Addresses EU data protection requirements
- Compatible with EU public procurement rules
- Court-tested in EU member states
For European companies, especially those in regulated industries or public sector, this matters. Your legal team understands EUPL. They don't need to hire US counsel to interpret it.
The Sovereignty Angle
NeoDonkey is about digital sovereignty: your data, your software, your control. Using an American license for European sovereignty software felt... wrong.
EUPL is the only open-source license created by a democratic institution (the EU Commission) rather than a foundation, company, or individual. It's not Richard Stallman's vision or Google's preference. It's 27 democratic nations agreeing on how software freedom should work.
Compatibility: The Hidden Superpower
EUPL-1.2 is compatible with:
- GPL v2 and v3
- AGPL
- LGPL
- OSL
- Cecill
This means you can combine EUPL code with GPL code without license conflicts. The EUPL's "upstream compatibility" clause allows you to relicense EUPL code under any of these licenses, solving the "license compatibility matrix" problem that plagues open-source projects.
The Trade-Off
EUPL is not as "permissive" as MIT. Some companies avoid it because they can't proprietize it. If your business model is "take open source, add proprietary sauce, sell without contributing," EUPL blocks you.
Good. That's the point.
If you want to use NeoDonkey for your business, you can. If you want to modify it for your needs, you can. If you want to sell services around it, you can. But if you want to take our code, close it, and compete with us using our own work, you can't. That's fair.
Try It
NeoDonkey is EUPL-1.2 licensed. Read the license (it's only 3,000 words). Compare it to GPL (5,000 words) or Apache (2,000 words but US-centric). Decide for yourself which license best protects software freedom in 2026.
Published by NeoDonkey Legal. View source on GitHub.