On this page
Short answer
Elasticsearch and Kibana source code is offered under three licences: ELv2, SSPL and, since 2024, the OSI-approved AGPLv3. For most teams running Elasticsearch internally, Elastic says nothing changes. The licence decides what you may do with the software; it does not decide who can support your cluster. This guide sets out what Elastic says on its own pages, with dates, and what it means for Elasticsearch support. It is not legal advice.
# Elastic Licence (SSPL/AGPL) and Your Support Options
Elasticsearch and Kibana source code is offered under three licences: the Elastic License 2.0 (ELv2), the Server Side Public License (SSPL) and, since 2024, the OSI-approved AGPLv3. For most teams running Elasticsearch internally, Elastic says nothing changes. The licence decides what you may do with the software; it does not decide who can support your cluster. This page sets out what Elastic says on its own pages, with dates, and what that means for Elasticsearch support. It is not legal advice; ask your counsel about your own use.
What did Elastic change in 2021?
On 2 February 2021, Elastic announced that Elasticsearch and Kibana source code, previously Apache 2.0, would be dual licensed under the Elastic License and SSPL, with ELv2 applying to all of Elasticsearch and Kibana. The announcement said there was "no impact to any of our Elastic Cloud or self-managed customers" and described SSPL as an option to minimise the effect on users. It listed three ELv2 limitations: offering the products to others as a managed service, circumventing licence-key functionality, and removing licensing or copyright notices.
What changed in 2024?
On 29 August 2024, Elastic announced that it would add AGPL as another licence option next to ELv2 and SSPL "in the coming weeks", described as adding an option and not removing anything, and told existing users to carry on because nothing changed. Elastic's licensing FAQ now describes AGPLv3 as an OSI-approved open source licence that allows free and unrestricted use, modification and redistribution, with modifications and derivative works made available under the same licence.
How do the three licences compare?
| Licence | Source | What Elastic's pages say | Practical question |
|---|---|---|---|
| ELv2 | Elastic License 2.0 | Applies to free and paid features; permits use, copy, distribution and derivative works; limits managed-service offerings, licence-key circumvention and notice removal | Are you offering Elasticsearch to others as a service? |
| SSPL | Server Side Public License | If you provide the product as a service to others, you must publicly release modifications | Do you run a modified build as a service? |
| AGPLv3 | OSI-approved | Free use, modification and redistribution; modifications made available under the same licence | Will you distribute or network-expose a modified version? |
Elastic's FAQ says that if you use its distributions, nothing changes for you, and that you may freely use Elasticsearch inside your own SaaS or self-managed application provided you follow the ELv2 limitations. It also says the licence "does not contain any copyleft provisions" for SaaS built on Elasticsearch, and that public cloud providers need to comply with SSPL, AGPLv3 or the Elastic License to offer a version released after the change.
Elastic's subscriptions page describes the free Basic tier as "available under the Elastic License", with select features also under SSPL or Apache License 2.0. That page does not mention AGPL (read 17 November 2026), so confirm the exact licence of the build you download.
What does the licence mean for support?
It does not restrict who can support your cluster. A licence governs use and distribution of the code; support is a service contract. Three practical points:
- Elastic's subscription is one source of support, not the only one. Its support policy applies to supported versions of Elastic's products under a subscription. Self-managed clusters can also be supported by independent providers. See Elasticsearch support without an Elastic subscription.
- Upgrading across the licence change is a choice. Moving from an Apache 2.0-era release (OpenSearch forked from Elasticsearch 7.10.2) to a later one means accepting one of the three licences. For internal use Elastic says nothing changes; if your product embeds or redistributes Elasticsearch, have counsel read ELv2 and the FAQ.
- OpenSearch is the Apache 2.0 route. The OpenSearch FAQ says all software in the project is released under Apache License 2.0 and that it is wire-compatible with Elasticsearch 7.10, with some caveats: clients with version checks may not work, and Beats 7.13 and later do not support OpenSearch. AWS supports its managed service, and independent providers support self-managed clusters. For the comparison, see OpenSearch support options.
A decision checklist
| Question | If yes |
|---|---|
| Do you only run Elasticsearch internally? | Elastic says nothing changes; keep a record of which licence your build is under |
| Do you embed it in a product you ship or host for customers? | Read ELv2 limits and SSPL/AGPL obligations with counsel before upgrading |
| Do you need Apache 2.0 for policy reasons? | Evaluate OpenSearch, and test clients and Beats |
| Do you need someone to answer a Sev 1 on a self-managed cluster? | Licence is not the constraint; compare providers on versions, response targets and exit terms |
| Are you upgrading from 7.x? | Plan the licence decision alongside the multi-version upgrade |
How AceMQ fits
AceMQ provides 24/7 Elasticsearch and OpenSearch support across the Americas, EMEA and APAC, with response targets from 15 minutes, by plan, and replies to quote requests within 1 hour. Support typically runs $24,000-72,000 a year (USD), by SLA, scope and deployment. AceMQ gives no legal or licensing advice and is not a reseller of Elastic.
Sources
- Elastic, "Elastic License v2" blog post, 2 Feb 2021: elastic.co/blog/elastic-license-v2
- Elastic, "Elasticsearch is open source, again" blog post, 29 Aug 2024: elastic.co/blog/elasticsearch-is-open-source-again
- Elastic licensing FAQ: elastic.co/pricing/faq/licensing
- Elastic subscriptions: elastic.co/subscriptions
- OpenSearch FAQ (Apache 2.0; 7.10 wire compatibility): opensearch.org/faq/
Frequently Asked Questions
Is Elasticsearch open source again?
Elastic's 29 August 2024 post said Elasticsearch and Kibana can again be called open source through the AGPL option, with SSPL and ELv2 remaining.
Can I use Elasticsearch internally under the current licences?
Elastic's FAQ says that if you use its distributions, nothing changes for you. Confirm your own case with counsel.
Can I run Elasticsearch as a service for others?
ELv2 limits offering it to others as a managed service; SSPL requires releasing modifications if you provide it as a service. Take advice before doing so.
Does the licence affect who can support my cluster?
No. Support is a separate service; self-managed clusters can use an independent provider.
Is OpenSearch an alternative to avoid these licences?
OpenSearch is Apache 2.0 licensed and wire-compatible with Elasticsearch 7.10, with some client and Beats caveats.
Guides, comparisons and research
Go deeper on support and version lifecycles
Comparisons
9- PostgreSQL vs MySQL: Where They Differ and How to Choose
- OpenSearch vs Elasticsearch: How the Fork Has Diverged
- Enterprise Support Compared 2026: Databricks, Snowflake, MuleSoft, Boomi, Datadog and Splunk
- Kong Alternatives and Competitors Compared
- Splunk Alternatives and Replacements Compared
- MuleSoft Alternatives and Competitors Compared
