#1
A distributed, RESTful search and analytics engine written in Java, used for full-text search, log analysis and vector search across large datasets.
- GitHub stars
- 79k
- Last commit
- today
- Latest release
- v9.5.6
- Self-hosted
- Yes
- Hosted version
- Available
elastic.co
Elasticsearch is a distributed, RESTful search engine written in Java. It stores documents as JSON, indexes them so they can be searched quickly, and exposes everything through an HTTP API, which makes it a common backbone for site search, application search and log analytics. It is built on the Apache Lucene library.
Beyond full-text queries it supports filtering, aggregations for analytics and, in recent versions, vector search for semantic and AI-assisted retrieval. Data is spread across nodes in a cluster using shards and replicas, so capacity and resilience grow by adding machines. It is the core of the Elastic Stack, usually paired with Kibana for exploration and with ingestion tools for logs and metrics.
The repository describes the project as free and open source, while its license metadata is listed as 'Other', so review the current license terms before relying on it commercially. It can be self-managed on your own servers or used as a managed service through Elastic Cloud.
Key features
- Distributed full-text search over JSON documents
- RESTful HTTP API
- Aggregations for analytics
- Vector search for semantic retrieval
- Clustering with shards and replicas
#2
An open-source column-oriented database management system built for real-time analytical reports, available to self-host or as the managed ClickHouse Cloud service.
- GitHub stars
- 51k
- Last commit
- today
- Latest release
- v26.10.2.103-stable
- Licence
- Apache-2.0
- Self-hosted
- Yes
- Hosted version
- Available
clickhouse.com
ClickHouse is an open-source database management system built to generate analytical reports in real time. Its column-oriented storage makes scans and aggregations over very large tables efficient, which is why it is widely used for event data, logs, metrics and product analytics. It is written in C++ and queried with SQL.
The project's topics describe it as an OLAP, massively parallel and distributed system, and it is used for big data workloads where query latency matters. You can install it on Linux, macOS or FreeBSD, follow a tutorial that sets up a small cluster, or skip installation by trying ClickHouse Cloud, a managed service built by its creators. Releases arrive monthly, with a community call for each one, and there are Slack and Telegram channels for help.
ClickHouse is Apache-2.0 licensed. It is a good fit for analytics engineers and platform teams who need fast aggregations over billions of rows and are comfortable operating a database, or who prefer to hand that operation to the vendor's cloud.
Key features
- Column-oriented storage for analytics
- SQL queries over large datasets
- Distributed, massively parallel processing
- Real-time analytical reporting
- Install on Linux, macOS or FreeBSD
- Managed ClickHouse Cloud option
Pricing: The open-source distribution is free. ClickHouse Cloud is usage-based, with plans from $53 (Basic), $437 (Scale) and $571 (Enterprise) per month and a 30-day trial with $300 in credits.
#3
An analytics engine for processing large datasets, with APIs in Scala, Java, Python and R and libraries for SQL, machine learning, graphs and streaming.
- GitHub stars
- 44k
- Last commit
- yesterday
- Licence
- Apache-2.0
- Self-hosted
- Yes
spark.apache.org
Apache Spark is an analytics engine that brings batch, SQL, machine learning, graph and streaming workloads together for processing data at scale. It is maintained by the Apache Software Foundation under the Apache-2.0 license. It is written mainly in Scala and offers high-level APIs in Scala, Java and Python, with an R API that is now deprecated, on top of an engine optimized to execute general computation graphs.
A set of higher-level tools is included: Spark SQL for queries and DataFrames, MLlib for machine learning, GraphX for graphs, Structured Streaming for streams, and a pandas-style API for existing pandas workloads. Together they let teams run batch analytics, machine learning and streaming jobs on a single engine and share code between them.
The README points to the project website for full documentation and programming guides, and it contains only basic setup and build instructions. Spark suits data engineers and data scientists who process datasets too large for a single machine, and organizations that want one framework for ETL, analytics and machine learning on clusters.
Key features
- High-level APIs in Scala, Java and Python
- Optimized engine for computation graphs
- Spark SQL and DataFrames
- MLlib for machine learning
- GraphX for graph analytics
- Structured Streaming for stream processing
- Pandas API on Spark
Pricing: Free and open source under the Apache-2.0 license.
#4
Grafana Loki is a horizontally scalable log aggregation system that indexes labels instead of log contents, inspired by Prometheus.
- GitHub stars
- 29k
- Last commit
- yesterday
- Latest release
- v3.7.9
- Licence
- AGPL-3.0
- Self-hosted
- Yes
- Hosted version
- Available
grafana.com
Loki is a log aggregation system from Grafana, described as Prometheus for logs. It is horizontally scalable, highly available and multi-tenant. Instead of indexing the contents of log lines, it indexes a set of labels for each log stream and stores the compressed log text, which the project says makes it simpler to operate and cheaper to run. It is written in Go and released under the AGPL-3.0 license.
Because Loki reuses the labels familiar from Prometheus, you can move between metrics and logs using the same label sets, and it has native support in Grafana. It works especially well for Kubernetes pod logs, since metadata such as pod labels is scraped and indexed automatically. A typical stack has three parts: Alloy as the collection agent, Loki for storage and queries, and Grafana for exploration. Alloy replaces Promtail, which is considered feature complete. Unlike Prometheus, Loki receives logs by push.
Key features
- Label-based indexing instead of full-text indexing
- Horizontally scalable, multi-tenant architecture
- Native Grafana integration for querying logs
- Automatic Kubernetes pod label indexing
- Grafana Alloy agent for log collection
- Single-binary deployment option
Pricing: Free and open source under the AGPL-3.0 license.
#5
A scalable time series database and monitoring solution that is compatible with the Prometheus ecosystem, available as single-node and cluster versions.
- GitHub stars
- 18k
- Last commit
- yesterday
- Latest release
- v1.156.0
- Licence
- Apache-2.0
- Self-hosted
- Yes
- Hosted version
- Available
victoriametrics.com
VictoriaMetrics is a monitoring solution and time series database built for performance, cost efficiency and scale. It stores metrics, works with the Prometheus ecosystem and query language, and its topics also list support for InfluxDB, Graphite and OpenTSDB data formats, along with Grafana for dashboards, which makes it a common drop-in backend for existing monitoring setups.
It is offered as a single-node version and a cluster version, both under the Apache License 2.0, with downloadable binaries, container images published to Docker Hub and Quay, and the source code. The project publishes case studies from well-known companies, a quick start and key concepts guide, community channels on Slack, X and YouTube, and a fast-moving changelog. Enterprise support and enterprise releases with long-term support are available, and they can be evaluated with a free trial license. The maintainers also mention security certifications for their development practices.
Written in Go, VictoriaMetrics suits platform and SRE teams that want to store large volumes of metrics efficiently, replacing or extending Prometheus long-term storage. It can be deployed on your own infrastructure, including Kubernetes, and the company offers a managed cloud service as well.
Key features
- Time series database for metrics
- Prometheus and PromQL compatibility
- Single-node and cluster versions
- Docker images and binary releases
- Enterprise releases with long-term support
- Integrations with Grafana and OpenTelemetry
Pricing: Single-node and cluster versions are free under Apache-2.0; enterprise support and releases are offered with a free trial license.
#6
InfluxDB 3 Core is an open-source time series database for ingesting and querying events and metrics in near real time, built on Apache Arrow, DataFusion and Parquet.
- GitHub stars
- 32k
- Last commit
- 2 days ago
- Latest release
- v3.12.2
- Licence
- Apache-2.0
- Self-hosted
- Yes
- Hosted version
- Available
influxdata.com
InfluxDB is an open-source time series database for collecting, processing, transforming and storing event and metrics data. The current Core edition of InfluxDB 3 is written in Rust and builds on Apache Arrow, DataFusion and Parquet, and it targets workloads where data must be ingested continuously and queried quickly enough to drive dashboards, interactive interfaces and automation.
The README lists typical uses such as sensor monitoring, server and network monitoring, application performance monitoring, financial market analytics and behavioral analytics. Feature highlights include a diskless architecture that can store data in object storage or on local disk with no extra dependencies, an embedded Python virtual machine for plugins and triggers, and persistence in Parquet files. The project quotes very low query latency for last-value lookups, though real numbers depend on your hardware and data.
InfluxDB is Apache-2.0 licensed and can be run on your own servers. InfluxData, the company behind it, also sells hosted and commercial editions. The topics list monitoring, metrics and time series, and it commonly sits behind visualization tools such as Grafana in observability stacks.
Key features
- Time series storage for events and metrics
- Diskless architecture with object storage support
- Embedded Python VM for plugins and triggers
- Parquet file persistence
- Built on Apache Arrow and DataFusion
- Fast queries for dashboards and monitoring
Pricing: InfluxDB 3 Core is free. Cloud Serverless is metered on data written, queries, storage and data out, with a free tier and $250 credit; Enterprise and Cloud Dedicated are quoted by sales.
#7
A PostgreSQL extension that adds time-series storage, hypertables and a columnstore for fast, real-time analytics on event data.
- GitHub stars
- 24k
- Last commit
- today
- Latest release
- 2.32.0
- Self-hosted
- Yes
- Hosted version
- Available
tigerdata.com
TimescaleDB is a PostgreSQL extension that turns Postgres into a database for time-series and event data, aimed at real-time analytics. Because it lives inside PostgreSQL, you keep SQL, existing tools and the broader Postgres ecosystem while gaining storage and query features designed for data that arrives continuously with timestamps.
The quick start walks through running it locally with a one-line install script or Docker, creating a hypertable with the columnstore enabled, inserting data directly into the columnstore and running analytical queries. It suggests Docker, around 8 GB of RAM and a psql or other PostgreSQL client, and warns that the install script is meant for local development and testing, not production. Topics list uses such as IoT, financial analysis and historian data.
The code is written in C, and its license is listed as 'Other' on GitHub because some features sit under Timescale's own license rather than a standard open-source one, so check which apply to you. The company, now branded TigerData, also runs a hosted cloud service. It suits teams who want time-series features without leaving PostgreSQL.
Key features
- PostgreSQL extension for time-series data
- Hypertables with columnstore
- Fast analytical queries on event data
- Full SQL and Postgres tooling compatibility
- Docker and one-line local install
- Managed cloud service from the vendor
Pricing: The open-source TimescaleDB is free to self-host. Tiger Cloud compute starts at $30 per month on Performance and $36 on Scale, plus storage, billed hourly with a 30-day free trial; Enterprise is by contact.
#8
Apache Flink is a framework and distributed processing engine for stateful computations over unbounded and bounded data streams, designed to run in all common cluster environments.
- GitHub stars
- 26k
- Last commit
- yesterday
- Licence
- Apache-2.0
- Self-hosted
- Yes
flink.apache.org
Apache Flink is a framework and distributed processing engine for stateful computations over unbounded and bounded data streams. It has been designed to run in all common cluster environments, perform computations at in-memory speed and at any scale.
Flink provides correctness guarantees including exactly-once state consistency, event-time processing, and sophisticated late data handling. It offers layered APIs such as SQL on stream and batch data, DataStream API, and ProcessFunction for time and state.
Key features
- Exactly-once state consistency
- Event-time processing
- Sophisticated late data handling
- Layered APIs including SQL, DataStream API, and ProcessFunction
- Flexible deployment and high-availability setup
- Scale-out architecture with support for very large state and incremental checkpoints
#9
A distributed SQL query engine for big data analytics that runs fast queries across many data sources, formerly known as PrestoSQL.
- GitHub stars
- 14k
- Last commit
- today
- Latest release
- 484
- Licence
- Apache-2.0
- Self-hosted
- Yes
trino.io
Trino is a distributed SQL query engine built for analytics on large data sets. It was formerly called PrestoSQL, and it lets analysts and engineers run interactive SQL against data wherever it lives rather than first moving it into a single warehouse.
The project's topics point to its role in the data lake ecosystem, with connectors and integrations for systems such as Hive, Hadoop, Iceberg and Delta Lake, and a JDBC driver for applications. Trino is a Maven project written in Java, and its repository covers development guidelines, plugin implementors, a security policy and reproducible builds. It runs as a cluster of servers and has a web UI.
Trino is released under the Apache-2.0 licence and is deployed and operated by the user, with deployment instructions and end-user documentation in the project's user manual. It is a fit for data platform teams that need fast, standards-based SQL over many sources, rather than for individual analysts looking for a point-and-click tool.
Key features
- Distributed SQL query engine
- Fast analytics on big data
- Connectors for data lake formats like Iceberg
- JDBC access for applications
- Plugin architecture for custom connectors
- Reproducible builds since version 449
Pricing: Free and open source under the Apache-2.0 licence.
#10
An open-source, low-latency time-series database with a single SQL engine for ingestion, stream processing and tiered storage on open formats like Parquet.
- GitHub stars
- 18k
- Last commit
- today
- Latest release
- 10.2.0
- Licence
- Apache-2.0
- Self-hosted
- Yes
questdb.com
QuestDB is an open-source time-series database aimed at high-speed ingestion and fast analytical queries, with a focus on use cases such as capital markets, tick data and real-time analytics. One SQL engine covers ingestion, stream processing and long-term storage, so teams query live data and years of history the same way.
The engine is written in Java that avoids garbage collection, with C++ and Rust used on performance-critical paths. Data is held in memory-mapped, time-partitioned columns, and queries run across all CPU cores using SIMD and JIT-compiled filters. No third-party libraries sit on the data path. Data moves through three storage tiers: Apache Parquet files, native columnar partitions, and a write-ahead log that is written in parallel. In the open-source edition you convert partitions to Parquet manually, while the Enterprise edition automates tiering to object storage. Because the data stays in open formats (Parquet, Iceberg and Arrow), other tools can read it, and the README publishes benchmark figures for ingestion and query streaming.
QuestDB is Apache-2.0 licensed and runs on your own servers, with documentation also available in Chinese. It suits teams building financial, industrial or telemetry platforms who need very fast time-series ingestion.
Key features
- Single SQL engine for time-series data
- Very high-speed event ingestion
- SIMD and JIT-accelerated queries
- Tiered storage with Parquet
- Open formats: Parquet, Iceberg and Arrow
- Memory-mapped time-partitioned columns
Pricing: The open-source edition is free under the Apache-2.0 license; an Enterprise edition adds features such as automatic tiering.
6 more Azure Data Explorer alternatives
Commercial Azure Data Explorer alternatives
Hosted, closed-source products that compete with Azure Data Explorer.
Azure Data Explorer alternatives: questions
- What is the best open-source alternative to Azure Data Explorer?
- Elasticsearch is the top-ranked open-source alternative to Azure Data Explorer on Enlisted: A distributed, RESTful search and analytics engine written in Java, used for full-text search, log analysis and vector search across large datasets. Other strong options are ClickHouse, Apache Spark, Grafana Loki and VictoriaMetrics.
- What are the best commercial alternatives to Azure Data Explorer?
- Amazon Athena, KX kdb+, Google BigQuery, Logz.io and Snowflake are among the hosted, closed-source alternatives to Azure Data Explorer listed on Enlisted, which lists 10 in total. Compare their pricing and features on each tool page.
- Are these Azure Data Explorer alternatives free?
- All 16 are open source, so the code is free to use under its licence, and all of them can be self-hosted on your own server or computer. 9 also offer a paid or managed cloud version if you'd rather not host it yourself.
- How is this list of Azure Data Explorer alternatives ranked?
- By a score built from GitHub stars, star growth over the last 30 days and how recently the code changed. 16 of these projects shipped code in the last 30 days. Data is refreshed daily, and nobody can pay to move up.