Elastic changed its license twice, in opposite directions

The workload

Elastic changed the license under which self-hosted Elasticsearch and Kibana ship twice in three years, and each change asks a founder to redo the same check: which license file actually governs the version being deployed. Verified: on 14 January 2021, per Elastic's own announcement, the company moved future releases from Apache 2.0 to a dual offering of the Server Side Public License and its own Elastic License. Verified: on 29 August 2024, per a second Elastic post, the company added AGPLv3 as a third option for the same two projects. The workload is checking the specific version and license file in use, since 'Elasticsearch's license' is not one constant fact across time.

What the documents show

Self-reported: the 2021 post states the reason as cloud providers that 'have taken open source products and provided them as a service without investing back into the community.' Verified: the current licensing FAQ, a living document as retrieved 16 September 2026, confirms Elastic 'no longer produces an Apache 2.0 distribution' by default and describes the Elastic License 2.0 as intended to be permissive for most uses while restricting offering the software itself as a competing managed service. Self-reported: the 2024 post frames the AGPL addition as a return, quoting founder Shay Banon that he never 'stopped believing in Open Source,' and the FAQ dates that update to on or around 29 August 2024, ahead of the 8.16 release. These are two separate, dated events, not one continuous fact: a 2021 restriction followed by a 2024 addition of an OSI-recognized option alongside, not instead of, the existing SSPL and Elastic License terms.

The operating cost

Neither announcement states a licensing fee; ELv2 and SSPL are both offered without charge for uses inside their own terms, and AGPL carries none by definition. Estimated: the operating cost to a founder is re-verification, not payment, each time a self-hosted Elastic product is upgraded, since the applicable license depends on the specific release and distribution chosen. No document reviewed here states how the 2021 change affected Elastic's revenue, and none is assumed.

The stop condition

The 2021 restriction on an Apache-2.0 distribution does not expire on its own; per the FAQ, Elastic simply does not produce one going forward, though older Apache-licensed releases already published remain under that license. The 2024 AGPL option does not replace the other two; a deploying founder chooses among the three current options as stated in the license files attached to the release actually downloaded.

• Which license file ships with the specific Elastic version and distribution currently deployed?
• If AGPLv3 is chosen for the 2024-and-later releases, does the network-use obligation documented elsewhere in this batch apply to this deployment?
• Does the planned use fall inside ELv2's stated limits, or does it look like the managed-service use the 2021 change targeted?

Two relicensing events, three years apart, are not evidence of instability by themselves; they are two dated decisions, each stated in the company's own words and each checkable against the license file a given release actually carries.