The Open-Source Darling
To understand the impact of the decision, you first have to appreciate what Elastic was. The company is the creator of Elasticsearch, a wildly popular open-source search and analytics engine. Combined with its sister products, Logstash and Kibana, the 'ELK
Stack' became a foundational technology for countless companies, including giants like Netflix and Walmart. The model was simple: the core software was free and developed with community help, while Elastic made money selling premium features and managed services. This strategy fueled a decade of growth and cultivated a loyal developer community that believed in the open-source ethos.
The Cloud Giant's Shadow
The problem started when Amazon Web Services (AWS), the world's largest cloud provider, began offering a competing product based on Elastic's free code. Launched in 2015, Amazon Elasticsearch Service gave customers an easy way to use the technology within the AWS ecosystem, but Elastic saw very little of the revenue. To make matters worse, Elastic accused AWS of causing market confusion and misleading users into thinking the service was an official collaboration. Elastic's CEO, Shay Banon, felt AWS was acting like a 'bully,' profiting from their work without contributing back in a meaningful way. The tension simmered for years, a classic David-and-Goliath struggle between an open-source creator and a hyperscale cloud provider.
The Decision That Changed Everything
In January 2021, Elastic made its move. The company announced it was changing the license for Elasticsearch and Kibana from the permissive Apache 2.0 license to the much more restrictive Server Side Public License (SSPL). This wasn't just a technical tweak; it was a declaration of war. The SSPL, first created by MongoDB for similar reasons, was specifically designed to prevent cloud providers like AWS from offering the software as a paid service without also open-sourcing all the supporting management code—a condition AWS would never agree to. This was the 'hidden' decision: a legal maneuver aimed directly at protecting its business model from a trillion-dollar competitor. It was a bet that financial survival was more important than open-source purity.
The Fork and the Fury
The backlash was immediate and intense. Critics in the open-source community argued that Elastic had abandoned its principles. AWS responded decisively. Instead of complying with the new license, Amazon announced it would create a 'fork'—a new, independent project based on the last truly open-source version of Elasticsearch (7.10.2). They called it OpenSearch. This move was devastating for Elastic. In one stroke, AWS created a direct, fully open-source competitor and instantly inherited a huge portion of the developer community that had built their systems on the promise of the Apache 2.0 license. The community was now split, forced to choose between the original creator and the open alternative backed by the world's biggest cloud platform.
Reshaped, but for Better or Worse?
Five years later, the dust has settled, and a new landscape has emerged. Elastic's decision did reshape the company. It successfully stopped AWS from using its new code, and its revenues have continued to grow, with the company reporting approximately $1.27 billion in fiscal 2024. But it came at a high cost. It created a powerful, well-funded rival in OpenSearch and alienated a significant portion of its developer base. The move forced Elastic to re-center its identity, focusing more on its AI-powered platform and enterprise solutions. In a telling move in 2024, Elastic partially walked back its stance by adding a more conventional open-source license option, an acknowledgment that the SSPL had 'created a rift in the community.' The decision ultimately protected Elastic's bottom line but fractured its soul, leaving a permanent mark on its relationship with the very community that helped build it.
