The January 2021 Break

Elastic announced in January 2021 that Elasticsearch and Kibana would move from the Apache 2.0 licence to a dual-licence arrangement: the Server Side Public Licence (SSPL) and Elastic's own proprietary licence. Shay Banon, Elastic's founder and chief executive, framed the change as a response to Amazon Web Services building a managed Elasticsearch service — Elastic claimed AWS was taking substantial value from the project without contributing back.

The SSPL, written by MongoDB in 2018, carries a condition that any party offering the software as a service must open-source the entire service stack around it — a requirement the Open Source Initiative has declined to approve as meeting the Open Source Definition. That non-approval was not incidental: it was precisely why the licence was effective as a deterrent. A company running Elasticsearch as a managed service under the SSPL would face an obligation so broad — open-sourcing its full hosting infrastructure — that compliance is practically impossible at commercial scale.

An adult speaker on a conference stage mid-presentation, a slide behind them showing the text of an open-source licence clause, the audience partially visible in the foreground
PLATE 02Licence changes are argued in public, on stage and on mailing lists, before they are argued in court.Photo: Matheus Bertelli / Pexels

AWS did not attempt compliance. Within days of Elastic's announcement, AWS announced it would fork Elasticsearch and Kibana at the final Apache 2.0 versions, maintaining that fork as OpenSearch, an AWS-led project. The fork drew significant community backing, partly because the Apache 2.0 codebase was genuinely useful, and partly because several contributors objected to Elastic's relicensing on principle — including those who had contributed under the assumption that Apache 2.0 terms would persist. Contributor Licence Agreements had assigned copyright to Elastic, which made unilateral relicensing legally available to the company even where individual contributors disagreed.

The August 2024 Addition

In August 2024, Elastic announced that Elasticsearch and Kibana would become available under AGPL-3.0 as an additional option alongside the existing SSPL and proprietary licences. The AGPL, a copyleft licence that extends GPL requirements to cover software run as a network service, is OSI-approved — a status the SSPL does not hold.

Elastic described the move as a response to community requests for an OSI-approved licence. The practical effect is that users and organisations that want to engage with Elasticsearch under a recognised open-source licence now have a path to do so without touching the SSPL. The AGPL's network-use disclosure requirements are still substantial — anyone running a modified version of Elasticsearch as a service must release those modifications — but unlike the SSPL, the obligation is scoped to the licensed software itself rather than the entire surrounding service stack.

  1. CHRONOLOGYAS RECORDED
  2. January 2021Elastic relicences Elasticsearch and Kibana from Apache 2.0 to SSPL + proprietary
  3. Early 2021AWS forks both at the last Apache 2.0 versions; OpenSearch announced
  4. August2024 Elastic adds AGPL-3.0 as a third licence option alongside SSPL and proprietary
  5. September 2024OpenSearch joins the Linux Foundation

The addition does not retire the SSPL. Elastic's existing commercial relationships and the proprietary licence tier continue unchanged. The company is, in effect, offering three parallel licence tracks: AGPL for community and open-source use, SSPL as a deterrent to unacknowledged commercial hosting, and a proprietary licence for enterprises that want neither copyleft obligation.

OpenSearch, meanwhile, remains a separate project under the Linux Foundation and continues on its own trajectory. The fork was not reversed by Elastic's 2024 announcement, and the Linux Foundation has not indicated any expectation that it would be. Two major distributions of the Elasticsearch codebase — diverging since early 2021 — now exist independently.

A licence file — its SPDX header and copyright notice clearly visible — displayed in a terminal window on a large monitor, shot at an angle that shows both the text and the room behind it
PLATE 03The header block is where the terms live; everything downstream reads it as the contract.
Photo: Pixabay / Pexels

What the Round Trip Settles

The sequence illustrates a pattern visible across several infrastructure projects in this period: a licence tightened under cloud-competition pressure, followed by partial liberalisation once the competitive response — in this case a well-resourced fork — had already absorbed the community most likely to have been deterred. Adding AGPL does not undo the fork; it signals that Elastic considers the cloud-provider threat sufficiently managed that restoring open-source credibility now costs less than it would have in 2021. Whether the community reads it as a genuine return or a managed concession depends largely on what contributors needed in the years between.