---
title: "Elastic founder on why they returned to open source 4 years after going proprietary"
description: "Elastic, the company behind Elasticsearch, has reverted to open source nearly four years after adopting proprietary licenses. This decision follows a trademark dispute with AWS, which had marketed its"
type: "news"
locale: "en"
url: "https://longbridge.com/en/news/215531135.md"
published_at: "2024-09-29T15:02:02.000Z"
---

# Elastic founder on why they returned to open source 4 years after going proprietary

> Elastic, the company behind Elasticsearch, has reverted to open source nearly four years after adopting proprietary licenses. This decision follows a trademark dispute with AWS, which had marketed its own version of Elasticsearch. Co-founder Shay Banon expressed that the legal battles were consuming resources and causing market confusion. Elastic has now adopted the AGPL license, which imposes more restrictions than its previous Apache 2.0 license, allowing it to be recognized as open source again. Banon emphasized the importance of open source for users who often search for open source solutions.

Licensing kerfuffles have long been a defining facet of the commercial open source space. Some of the biggest vendors have switched to a more restrictive “copyleft” license, as Grafana and Element have done, or gone full proprietary, as HashiCorp did last year with Terraform.

But one $8 billion company has gone the other way.

Elastic, the creator of enterprise search and data retrieval engine Elasticsearch and the Kibana visualization dashboard, threw a surprise curveball last month when it revealed it was going open source once more — nearly four years after switching to a couple of proprietary “source available” licenses. The move goes against a grain that has seen countless companies ditch open source altogether. Some are even creating a whole new licensing paradigm, as we’re seeing with “fair source,” which has been adopted by several startups.

## “It was just taking too long”

In 2021, Elastic moved to closed source licenses after several years of conflict with Amazon’s cloud subsidiary AWS, which was selling its own managed version of Elasticsearch. While AWS was perfectly within its rights to do so given the permissive nature of the Apache 2.0 license, Elastic took umbrage at the *way* that AWS was marketing its incarnation, using branding such as “Amazon Elasticsearch.” Elastic believed this was causing too much confusion, as customers and end users don’t always pay too much attention to the intricacies of open source projects and the associated commercial services.

“People sometimes think that we changed the license because we were upset with Amazon for taking our open source project and providing it ‘as a service,’” Elastic co-founder and CTO Shay Banon told TechCrunch in an interview this week. “To be honest, I was always okay with it, because it’s in the license that they’re allowed to do that. The thing we always struggled with was just the trademark violation.”

Elastic pursued legal avenues to get Amazon to retreat from the Elasticsearch brand, a scenario reminiscent of the ongoing WordPress brouhaha we’ve seen this past week. And while Elastic later settled its trademark spat with AWS, such legal wrangles consume a lot of resources, when all the company wanted to do was safeguard its brand.

“When we looked at the legal route, we felt like we had a really good case, and it was actually one that we ended up winning, but that wasn’t really relevant anymore because of the change we’d made \[to the Elasticsearch license\],” Banon said. “But it was just taking too long — you can spend four years winning a legal case, and by then you’ve lost the market due to confusion.”

## Back to the future

The change was always something of a sore point internally, as the company was forced to use language such as “free and open” rather than “open source.” But the change worked as Elastic had hoped, forcing AWS to fork Elasticsearch and create a variant dubbed OpenSearch, which the cloud giant transitioned over to the Linux Foundation just this month.

With enough time having passed, and OpenSearch now firmly established, Banon and company decided to reverse course and make Elasticsearch open source once more.

“We knew that Amazon would fork Elasticsearch, but it’s not like there was a huge masterplan here — I did hope, though, that if enough time passed with the fork, we could maybe return to open source,” Banon said. “And to be honest, it’s for a very selfish reason — I love open source.”

Elastic hasn’t quite gone “full” circle, though. Rather than re-adopting its permissive Apache 2.0 license of yore, the company has gone with AGPL, which has greater restrictions — it requires that any derivative software be released under the same AGPL license.

For the past four years, Elastic has given customers a choice between its proprietary Elastic license or the SSPL (server side public license), which was created by MongoDB and subsequently failed to get approved as “open source” by the Open Source Initiative (OSI), the stewards of the official open source definition. While SSPL already offers some of the benefits of an open source license, such as the ability to view and modify code, with the addition of AGPL, Elastic gets to call itself open source once again — the license is recognized as such by the OSI.

“The Elastic \[and SSPL\] licenses were already very permissive and allowed you to use Elasticsearch for free; they just didn’t have the stamp of ‘open source,’” Banon said. “We know about this space so much, but most users don’t — they just Google ‘open source vector database,’ they see a list, and they choose between them because they care about open source. And that’s why I care about being on that list.”

Moving forward, Elastic says that it’s hoping to work with the OSI toward creating a new license, or at least having a discussion about which licenses do and don’t get to be classed as open source. The perfect license, according to Banon, is one that sits “somewhere between AGPL and SSPL,” though he concedes that AGPL in itself may actually be sufficient for the most part.

But for now, Banon says that simply being able to call itself “open source” again is good enough.

“It’s still magical to say ‘open source’ — ‘open source search,’ ‘open source infrastructure monitoring,’ ‘open source security,’” Banon said. “It encapsulates a lot in two words — it encapsulates the code being open, and all the community aspects. It encapsulates a set of freedoms that we developers love having.”

### Related Stocks

- [ESTC.US - Elastic NV](https://longbridge.com/en/quote/ESTC.US.md)

## Related News & Research

| Title | Description | URL |
|-------|-------------|-----|
| 早盘趋势｜Elastic NV 连续下探支撑，主力防御 or 换挡？本周会否迎变盘急拉？ | Elastic NV（ESTC.US）1 月 15 日走势持续弱势，价格快速接近 71.93–78.78 关键支撑区间。整个云服务和 SaaS 板块这几天都陷入深度观望，主力资金普遍收缩防御，以减少流动性冲击。盘面成交格外冷清，买卖双方都在 | [Link](https://longbridge.com/en/news/272744894.md) |
| 早盘趋势｜Elastic NV 多头集结，主升浪要来了？ | Elastic NV（ESTC.US）自年后延续反弹攻势，盘中高开高走，主力大单鲜明推升趋势，社区充满 “多头集结就要爆拉” 的气氛。科技成长风潮回归 +AI 需求预期，成了炒作主线。近日成交量同步创新高，82-88 美元区间反复换手，积蓄 | [Link](https://longbridge.com/en/news/272744708.md) |
| 沃尔玛四季度财报超预期但盈利指引不及预期，CEO 称 “美国低收入家庭只能勉强维持生计” | 沃尔玛 Q4 营收超预期，新财年盈利指引（每股 2.75-2.85 美元）远低于市场预期的 2.96 美元，显示通胀压力下消费者支出不确定性犹存，拖累股价下跌 1.38%。财报印证 K 型” 分化：高收入家庭驱动增长，低收入群体 “钱包吃紧 | [Link](https://longbridge.com/en/news/276398633.md) |
| 谷歌突然发布 Gemini 3.1 Pro：核心推理性能直接翻倍 | 谷歌发布了最新的大模型 Gemini 3.1 Pro，其推理性能较去年发布的 Gemini 3 Pro 翻倍。在 ARC-AGI-2 评测中，Gemini 3.1 Pro 得分 77.1%，显示出强大的推理能力。新模型支持多源数据综合和复杂 | [Link](https://longbridge.com/en/news/276396515.md) |
| GRAIL｜8-K：2025 财年 Q4 营收 43.6 百万美元超过预期 |  | [Link](https://longbridge.com/en/news/276379877.md) |

---

> **Disclaimer**: This article is for reference only and does not constitute any investment advice.
