Elasticsearch

Elasticsearch is a distributed search and analytics engine developed by Elastic. Built on Apache Lucene and implemented primarily in Java, it provides a JSON-over-HTTP interface for indexing, searching, aggregating, and analyzing structured and unstructured data. Its central abstraction is the document: records are represented as JSON documents, stored in indices, and distributed across primary shards and replica shards on a cluster of nodes. This architecture allows organizations to search large datasets with low latency while scaling storage and query capacity horizontally. The product originated with Shay Banon, who began developing the Compass search project in 2004 while working on a recipe application. Banon concluded that Compass required a fundamental redesign to support distributed operation and a simpler service interface. He rewrote the project around a RESTful HTTP API and JSON documents, releasing the first version of Elasticsearch in February 2010. Its relatively simple deployment model, broad language-client support, and ability to search both application data and operational logs helped it spread rapidly among developers and technology teams. Elasticsearch supports full-text search, relevance scoring, filtering, faceted and aggregated search, geospatial queries, autocomplete, real-time document retrieval, and percolation, in which stored queries are matched against incoming documents. It can function as a NoSQL-style data store for certain workloads, although it is not designed to provide general-purpose relational transactions or distributed ACID semantics. Automatic routing, shard replication, recovery, and cluster rebalancing make it suitable for highly available deployments, while its schema-flexible document model enables teams to ingest data whose structure evolves over time. The software became the foundational component of the Elastic Stack. Logstash provides data collection and transformation, Kibana supplies visualization and administration, and Beats provides lightweight data shippers. The combination was initially known as the ELK Stack, after Elasticsearch, Logstash, and Kibana, before Elastic broadened the branding to include Beats and other products. Elasticsearch is used in application search, website search, observability, log analytics, security analytics, enterprise search, monitoring, content discovery, and increasingly vector search and retrieval-augmented-generation workflows. Elastic commercialized services around the project after establishing Elastic N.V. in 2012. The company expanded from support and subscriptions into hosted services, managed Elasticsearch deployments, enterprise search, observability, security, machine learning, and AI-oriented search capabilities. Elastic Cloud provides hosted versions of Elasticsearch and related Stack components, while partnerships with major cloud providers have made the technology available through public-cloud marketplaces and managed offerings. The brand has also been shaped by significant licensing changes. Before version 7.11, Elasticsearch was distributed under the Apache License 2.0. In January 2021, Elastic changed the licensing of Elasticsearch and Kibana source code to a choice of the Server Side Public License and Elastic License 2.0, arguing that cloud providers were commercializing the technology without sufficient reciprocal contribution. Amazon Web Services responded by creating an Apache-licensed fork called OpenSearch, and several other ecosystem companies supported the fork. In 2024, Elastic added AGPLv3 as another licensing option for the free portions of the source code, restoring an OSI-approved open-source option alongside the Elastic License and SSPL. As of 2026, Elasticsearch remains an active core product of Elastic's broader Search AI, observability, and cybersecurity platform. Its positioning has expanded beyond conventional text search: Elastic promotes it as a data store and context engine for enterprise AI, co…

Elasticsearch traces its origins to Shay Banon's Compass project, begun in 2004. Banon initially created Compass while developing a recipe application for his wife, who was studying at Le Cordon Bleu. As Compass evolved, he determined that its architecture would not provide the scalability and distributed behavior required for a modern search service. Rather than continue incrementally modifying the project, he undertook a substantial rewrite centered on Apache Lucene, JSON documents, and a common HTTP interface. The first version of Elasticsearch was released in February 2010. Its design made Lucene functionality accessible through a service-oriented API rather than requiring every application to embed and manage Lucene directly. Documents could be indexed as JSON, queried over HTTP, and distributed among shards and replicas. The combination of a flexible document model, near-real-time search, straightforward deployment, and clients for languages including Java, C#, PHP, Python, and Ruby helped the project gain adoption among application developers and infrastructure teams. Elasticsearch was developed in close association with other open-source projects. Logstash handled collection and transformation of logs and events, Kibana provided visualization and exploration, and Beats supplied lightweight agents for shipping operational data. Together, these components became known first as the ELK Stack and later as the Elastic Stack. This ecosystem helped Elasticsearch move beyond website and application search into centralized logging, metrics, monitoring, security analytics, and enterprise data exploration. In 2012, Elastic N.V. was established by Shay Banon, Steven Schuurman, Uri Boness, and Simon Willnauer to provide commercial services around Elasticsearch and related projects. The company raised venture capital to fund engineering, support, sales, and cloud services. A Series C round announced in June 2014 raised $70 million and brought reported total funding to $104 million. During this period, the company developed a commercial model based on support, subscriptions, training, hosted services, and additional enterprise functionality while maintaining a strong developer and community presence. Elastic's 2015 acquisition of Found was an important step toward managed cloud delivery. Found had operated hosted Elasticsearch clusters and provided automation for installation, configuration, maintenance, and backups. Its technology and service model became part of Elastic Cloud. The same year, the company changed its corporate name from Elasticsearch to Elastic, reflecting expansion into products beyond the search engine itself. In 2017, Elastic acquired Swiftype, whose search technology contributed to App Search and Site Search. Elastic also developed cloud partnerships, including arrangements involving Google Cloud and Alibaba Cloud. The company filed for an initial public offering in 2018 and was listed on the New York Stock Exchange on October 5, 2018. Although Elasticsearch remained the best-known product in the portfolio, Elastic increasingly presented the technology as a common data foundation for search, observability, and security. Machine learning, alerting, security information and event management, enterprise search, and cloud management features were progressively integrated around the Elasticsearch and Kibana core. A major turning point occurred in 2019, when Elastic made several core security features available without a paid subscription. The move included TLS encryption, authentication realms, and role-based access control, reducing barriers to secure production deployments and strengthening the product's position in operational environments. Another turning point came in January 2021. Elastic announced that Elasticsearch and Kibana would no longer be distributed under Apache License 2.0 for the affected source code beginning with version 7.11. Instead, users could choose between the Server Side Public License and Elastic License 2.0. Elastic argued that the change was necessary because cloud providers were offering managed versions of Elasticsearch without contributing sufficiently to the upstream project or protecting the company's commercial model. Critics argued that the change conflicted with earlier assurances about Apache licensing and could fragment the ecosystem. Amazon Web Services answered by creating an Apache-licensed fork, later named OpenSearch to avoid trademark conflicts. Companies including Aiven, CrateDB, and Logz.io also expressed support for the fork or for continued Apache-licensed development. The episode divided parts of the Elasticsearch ecosystem and created a long-term distinction between Elastic's Elasticsearch distribution and the AWS-led OpenSearch project. In 2024, Elastic added AGPLv3 as an additional licensing option for the free portions of Elasticsearch and Kibana source code. This restored an OSI-approved open-source option while retaining the Elastic License and SSPL. The change was presented as a way to provide clearer community rights and reduce concerns created by the 2021 licensing transition. Recent development has emphasized vector search, semantic retrieval, generative-AI infrastructure, and the use of Elasticsearch as a context engine. Version 8.16 introduced improvements for vector workloads and large-language-model observability. As of 2026, Elasticsearch remains an active component of Elastic's broader Search AI platform, available for self-managed use and through Elastic Cloud, and continues to support traditional text search alongside analytics, security, observability, and AI retrieval applications.

1. 2026Elastic restructures its workforce

   Elastic announces an organizational change involving an approximately 7% workforce reduction while emphasizing search, security, observability, and AI infrastructure.

   Source
2. 2024AGPLv3 licensing option added

   Elastic adds AGPLv3 as an option alongside the Elastic License and SSPL for the free portions of Elasticsearch source code.

   Source
3. 2024Elasticsearch 8.16 release

   Version 8.16 adds vector-search and AI-observability capabilities, including Better Binary Quantization for large vector workloads.

   Source
4. 2021Licensing transition

   Elasticsearch source code moves from Apache License 2.0 to a choice of SSPL and Elastic License 2.0 for releases beginning around version 7.11.

   Source
5. 2021OpenSearch fork emerges

   AWS announces an Apache-licensed fork of Elasticsearch and Kibana, later branded OpenSearch.

   Source
6. 2019Core security features become available without charge

   Elastic makes selected encryption, authentication, and role-based access-control capabilities available without a paid subscription.

   Source
7. 2018Initial public offering

   Elastic lists on the New York Stock Exchange under ESTC on October 5.

   Source
8. 2017Swiftype acquisition

   Elastic acquires Swiftype, adding technology that later supports App Search and Site Search.

   Source
9. 2015Found acquisition and corporate rebranding

   The company acquires hosted Elasticsearch provider Found and changes its corporate name from Elasticsearch to Elastic.

   Source
10. 2014Series C financing

    The company announces a $70 million Series C financing round, bringing reported total funding to $104 million.

    Source
11. 2012Elastic N.V. is founded

    Shay Banon, Steven Schuurman, Uri Boness, and Simon Willnauer establish the company then known as Elasticsearch to commercialize the project and related services.

    Source
12. 2010First Elasticsearch release

    Banon releases the first version of Elasticsearch in February, introducing a distributed search service based on Lucene, JSON documents, and HTTP APIs.

    Source
13. 2004Shay Banon begins the Compass search project

    Shay Banon begins developing Compass, the precursor to Elasticsearch, while building a recipe application.

    Source

A scalable search, analytics, vector database, and data-context engine for enterprise applications, observability, cybersecurity, and AI retrieval workloads.

• ElasticsearchDistributed search and analytics engine2010

  The core Elasticsearch product is a distributed engine for indexing and querying JSON documents. It supports full-text search, filtering, relevance scoring, aggregations, geospatial queries, real-time retrieval, autocomplete, and vector or semantic search. Data is stored in indices divided into primary shards and replicas distributed across cluster nodes. Elasticsearch is used for application search, enterprise search, log analytics, observability, security analytics, content discovery, and AI retrieval workflows.

• Elastic CloudManaged cloud service2015

  Elastic Cloud provides hosted deployments of Elasticsearch and related Elastic Stack components. It abstracts infrastructure provisioning, cluster configuration, upgrades, backups, scaling, and operational maintenance. The service grew from Elastic's acquisition of Found, a hosted Elasticsearch provider, and is offered through Elastic's own cloud environment and public-cloud partnerships. It is designed for teams that want Elasticsearch capabilities without operating the underlying cluster infrastructure themselves.

• Elastic StackData collection, search, analytics, and visualization platform

  The Elastic Stack combines Elasticsearch with Kibana, Logstash, and Beats. Logstash collects and transforms data, Beats provides lightweight shippers, Elasticsearch indexes and analyzes the resulting documents, and Kibana supports visualization, exploration, dashboards, and administration. The stack was previously called the ELK Stack and remains widely associated with centralized logging, monitoring, observability, security analytics, and operational intelligence.

• Elasticsearch Vector SearchVector database and semantic retrieval

  Elasticsearch's vector-search capabilities allow organizations to store embeddings and combine approximate or exact nearest-neighbor retrieval with conventional lexical search, filtering, ranking, and aggregations. This supports semantic search, hybrid retrieval, recommendation systems, retrieval-augmented generation, and AI applications that need enterprise data access with permissions and metadata-aware filtering.

• Elasticsearch Security and Observability PlatformSecurity analytics and observability data platform

  Elastic uses Elasticsearch as the data and search foundation for observability and security products. These workloads include log and metric analysis, application performance monitoring, infrastructure monitoring, SIEM, threat detection, endpoint and cloud-security investigations, alerting, and machine-learning-assisted anomaly detection. The product positioning emphasizes a common searchable data layer across operational and security teams.

• 2023Elastic Search AI positioning

  Worldwide

  Elastic increasingly positioned Elasticsearch as a search and context engine for generative AI, combining traditional search, vector retrieval, enterprise data, and observability.

  Outcome. The positioning expanded the product's addressable use cases from conventional search and logging to retrieval-augmented generation and broader AI infrastructure.

  Source
• 2016Elastic Stack ecosystem positioning

  Worldwide

  Elastic promoted Elasticsearch, Logstash, Kibana, Beats, and associated commercial features as an integrated stack for search, logging, analytics, and operational data.

  Outcome. The campaign broadened the product's identity beyond application search and reinforced the ELK-to-Elastic-Stack transition.

  Source
• 2015Elastic Cloud and managed Elasticsearch expansion

  Worldwide

  Following the acquisition of Found, Elastic expanded its managed-cloud proposition and began presenting hosted Elasticsearch as a central part of its commercial offering.

  Outcome. The initiative developed into Elastic Cloud and helped move Elasticsearch from a self-managed developer project toward a broader cloud and enterprise platform.

  Source

• 2024Add AGPLv3 as a licensing optionStrategy

  Elastic sought to restore an OSI-approved open-source option while retaining licenses designed to protect its commercial distribution model.

  What changed. Elastic added AGPLv3 alongside SSPL and Elastic License 2.0 for the free portions of Elasticsearch and Kibana source code.

  Aftermath. Elasticsearch again became available under an OSI-approved open-source license option, although the licensing framework remained multi-license rather than returning to Apache License 2.0.

  Source
• 2024Release Elasticsearch 8.16Generation change

  Enterprise AI workloads increased demand for vector retrieval, efficient embedding search, and visibility into large-language-model applications.

  What changed. Elastic released version 8.16 with vector-search improvements, Better Binary Quantization, LLM observability, and related platform enhancements.

  Aftermath. The release reinforced Elasticsearch's positioning as a search, vector database, and AI context platform in addition to a traditional text-search engine.

  Source
• 2021Change the source-code licensing modelStrategy

  Elastic argued that cloud providers could offer managed Elasticsearch services while contributing insufficiently to the upstream project and commercial ecosystem.

  What changed. Elastic changed affected Elasticsearch and Kibana source code from Apache License 2.0 to a choice of SSPL and Elastic License 2.0 beginning around version 7.11.

  Aftermath. AWS launched the OpenSearch fork, while other ecosystem companies supported Apache-licensed alternatives. The change became one of the most consequential ecosystem disputes in the product's history.

  • Amazon Web Services — AWS forked the projects under Apache License 2.0 and later renamed the fork OpenSearch.
  • Aiven — Aiven expressed support for continuing an Apache-licensed fork of the technology.
  • CrateDB — CrateDB joined other ecosystem participants in supporting fork-based continuity.
  • Logz.io — Logz.io committed to supporting an open alternative following the licensing change.
  Source
• 2019Make core security capabilities available without chargeStrategy

  Secure production deployment was becoming essential for organizations running Elasticsearch in operational environments.

  What changed. Elastic made selected TLS, authentication, and role-based access-control features available without a paid subscription.

  Aftermath. The decision lowered adoption barriers and strengthened Elasticsearch's credibility for production logging, observability, and security workloads.

  Source
• 2017Acquire SwiftypeM&A

  Elastic sought to expand from infrastructure and developer search into packaged enterprise and website-search experiences.

  What changed. Elastic acquired Swiftype and used its technology as the basis for later App Search and Site Search offerings.

  Aftermath. The transaction broadened Elastic's enterprise-search product portfolio.

  Source
• 2015Acquire Found and build managed cloud servicesStrategy

  Self-managed Elasticsearch adoption created demand for hosted deployment, automated operations, maintenance, and backup services.

  What changed. Elastic acquired Found and incorporated its hosted-cluster capabilities into the company's cloud strategy, later developed as Elastic Cloud.

  Aftermath. Managed Elasticsearch became a major route for customers to adopt the technology without operating their own clusters.

  Source

• 2021Elasticsearch licensing controversyControversy

  Elastic's decision to move affected Elasticsearch and Kibana source code away from Apache License 2.0 generated sustained criticism from parts of the open-source community. Critics argued that the change contradicted earlier expectations and risked fragmenting the ecosystem. Elastic said it was responding to cloud providers commercializing the software without adequate collaboration.

  Source
• 2021AWS fork and trademark disputeControversy

  AWS created OpenSearch as an Apache-licensed fork after Elastic's licensing change. The resulting dispute included disagreement over the use of the Elasticsearch name and later developed into a trademark infringement lawsuit that the parties announced as resolved in 2024.

  Source

• 2026Elastic announces approximately 7% workforce reduction

  Elastic announced an organizational change involving an approximately 7% reduction in its workforce. CEO Ash Kulkarni attributed the restructuring to changes in the technology industry, increasing automation, and the company's effort to operate more efficiently while focusing on search, security, observability, and AI infrastructure.

  Leadership changeOther
  Source
• 2024Elastic adds AGPLv3 as a licensing option for Elasticsearch

  Elastic added the OSI-approved GNU Affero General Public License v3 as an option for the free portions of Elasticsearch and Kibana source code, alongside the Elastic License 2.0 and Server Side Public License.

  OtherProduct launch
  Source
• 2024Elasticsearch 8.16 introduces major vector and AI observability capabilities

  The 8.16 release expanded Elasticsearch's AI-oriented capabilities, including Better Binary Quantization for vector workloads and improved observability for large-language-model applications.

  Product generationProduct launch
  Source
• 2019Elastic makes core security features available without charge

  Elastic made several core security capabilities available without a paid subscription, including encrypted communications, native and file-based authentication, and role-based access control for cluster and index APIs.

  Product launch
  Source
• 2018Elastic lists on the New York Stock Exchange

  Elastic completed its initial public offering and began trading on the New York Stock Exchange under the symbol ESTC.

  Other
  Source
• 2017Elastic completes acquisition of Swiftype

  Elastic acquired Swiftype, a search startup whose technology later supported Elastic App Search and Elastic Site Search and expanded Elastic's enterprise-search portfolio.

  M&A
  Source
• 2015Elastic acquires Found and broadens its business beyond the Elasticsearch name

  Elastic acquired Found, a hosted Elasticsearch provider, and used the transaction to expand managed cloud services. The company also adopted Elastic as its corporate name to reflect a broader product portfolio.

  M&A
  Source

1. Elasticsearch
2. Elastic N.V.
3. Elastic Leadership Team
4. Elastic Licensing FAQ
5. Elasticsearch History: Overview of 15 Years of Searching
6. Elastic 8.16 Release Highlights
7. Elastic and Amazon Reach Agreement on Trademark Infringement Lawsuit
8. Elastic Reports Fourth Quarter and Fiscal 2026 Financial Results
9. Swiftype acquisition
10. Elastic restructures its workforce