Elastic License: The Anti-Parasite Decree
Sometimes a company watches the cloud economy approach its codebase like a predatory bird and decides to bolt the windows shut.
That is the Elastic License 2.0.
It is not GPL. It is not BSD. It is not MIT. It is not even pretending to be open source in the OSI sense.
It is source-available software with a very specific refusal built into the terms: you may use the software, copy it, distribute it, make derivatives, and run it, but you may not turn it into a hosted or managed service that gives third parties substantial access to the same functionality.
The Supreme Leader calls this what it is: an anti-parasite decree.
I. What Elastic License 2.0 Actually Says
Elastic’s own license text grants broad rights to:
- use
- copy
- distribute
- make available
- prepare derivative works
But it also imposes hard limits:
- you may not provide the software to third parties as a hosted or managed service if they get substantial functionality
- you may not move, change, disable, or circumvent the license-key functionality
- you may not remove or obscure notices
| Permission | ELv2 |
|---|---|
| Use privately | Yes |
| Modify | Yes |
| Redistribute | Yes, within the limits |
| Host as a competing managed service | No |
| Remove license checks | No |
| Strip notices | No |
That is the political center of the license. Elastic wants the code to circulate, but not to be absorbed into a rival cloud product under the old “we just operate it as a service” costume.
II. Why Elastic Wrote It
Elastic says the goal of ELv2 is to be as permissive as possible while protecting the products and brand against abuse. That is corporate language for a very old fear:
someone will take the software, operate it at scale, and sell the service back as if the original author were just unpaid infrastructure.
Elastic’s answer was not copyleft in the GPL sense. It was a service restriction.
That makes ELv2 a different species of license entirely:
| License family | Core strategy |
|---|---|
| GPL / AGPL | Reciprocity through legal obligation |
| BSD / MIT / Apache | Maximize reuse |
| Elastic License 2.0 | Permit broad use, but block hosted cloning |
That is why people call it “anti-AWS” or “cloud anti-parasite” rhetoric. The label is dramatic, but the mechanism is plain.
III. Why It Is Not Open Source
Elastic’s own FAQ says that in 2021 it moved Elasticsearch and Kibana source code to non-OSI-approved licenses, and in 2024 it added AGPLv3 as an option alongside SSPL and Elastic License v2 for parts of the source.
That matters. Source-available is not the same as open source.
| Category | Meaning |
|---|---|
| Open source | OSI-approved licensing with public-use freedoms |
| Source-available | You can see the source, but restrictions may block normal open-source reuse |
Elastic License 2.0 is in the second category. It is designed to allow use and redistribution under specific restrictions, not to satisfy the Open Source Definition.
The Supreme Leader appreciates precision. Confusing source-available with open source is how people get surprised in procurement meetings.
IV. Elastic vs AGPL
Elastic later added AGPLv3 as an option for the free portions of Elasticsearch and Kibana source. That creates a useful contrast:
| License | Trigger | Goal |
|---|---|---|
| AGPLv3 | Network interaction with modified software | Keep hosted derivatives free |
| ELv2 | Hosted or managed service delivery of the software | Stop commercial service cloning |
AGPL is copyleft. Elastic License 2.0 is a usage restriction with source availability.
They are not the same weapon. They do not ask the same question.
- AGPL asks: “Did you serve modified software to users?”
- ELv2 asks: “Are you using this as a competing managed service?”
That second question is the one cloud vendors do not enjoy answering.
V. Why Companies Reach For This Kind of License
Elastic License 2.0 exists because pure permissive licensing can be too permissive for some business models.
If the product is expensive to build and easy to host, then a rival can replicate the service layer and monetize the deployment without paying for the product in the same way the original author expected.
ELv2 responds by making that use case contractually expensive.
| Problem | ELv2 response |
|---|---|
| Service cloning | Blocked |
| Notice removal | Blocked |
| License circumvention | Blocked |
| Normal use, testing, internal deployment | Generally allowed |
This is not philosophy. It is a perimeter.
VI. The Real Story (Suppressed)
Officially, Elastic License 2.0 is a source-available license for Elastic’s distributions.
Unofficially, it is a moat with a sign at the gate.
The sign says:
- you may inspect the machinery
- you may build on the machinery
- you may not run a rival factory that charges the public for the same output
That is the logic of anti-parasite licensing. Not freedom everywhere. Not enclosure everywhere. Just enough legal force to stop the obvious exploitation path.
The Supreme Leader does not confuse this with the GPL. GPL is a freedom machine. Elastic License 2.0 is a commercial defense perimeter.
The Decree
Elastic License 2.0 matters because it shows the limit of permissive licensing in a hostile market.
Sometimes a vendor does not want reciprocity. Sometimes a vendor does not want full open-source adoption. Sometimes a vendor wants the source visible, the users unblocked, and the service clone prevented.
That is ELv2. Not open source. Not free software. Source-available with a very specific threat model.
Next: the last stretch of the series can cover the remaining edge licenses if you want them:
- zlib
- Boost
- 0BSD
- Unlicense / CC0
- EPL
— Kim Jong Rails, Supreme Leader of the Republic of Derails