README.md
replacing Prometheus, Loki, and Elasticsearch</h2>
<div align="center"> <h3 align="center"> <a href="https://docs.greptime.com/user-guide/overview/">User Guide</a> | <a href="https://greptimedb.rs/">API Docs</a> | <a href="https://github.com/GreptimeTeam/greptimedb/issues/7685">Roadmap 2026</a> </h3> <a href="https://github.com/GreptimeTeam/greptimedb/releases/latest"> </a> <a href="https://github.com/GreptimeTeam/greptimedb/releases/latest"> </a> <a href="https://hub.docker.com/r/greptime/greptimedb/"> </a> <a href="https://github.com/GreptimeTeam/greptimedb/actions/workflows/develop.yml"> </a> <a href="https://codecov.io/gh/GrepTimeTeam/greptimedb"> </a> <a href="https://github.com/greptimeTeam/greptimedb/blob/main/LICENSE"> </a> <a href="https://greptime.com/slack"> </a> <a href="https://twitter.com/greptime"> </a> <a href="https://www.linkedin.com/company/greptime/"> </a> </div>The unified OpenTelemetry backend — with SQL + PromQL on object storage.
GreptimeDB is an open-source observability database built for Observability 2.0 — treating metrics, logs, and traces as one unified data model (wide events) instead of three separate pillars.
Use it as the single OpenTelemetry backend — replacing Prometheus, Loki, and Elasticsearch with one database built on object storage. Query with SQL and PromQL, scale without pain, cut costs up to 50x.
| Feature | Description |
|---|---|
| Drop-in replacement | PromQL, Prometheus remote write, Jaeger, and OpenTelemetry native. Use as your single backend for all three signals, or migrate one at a time. |
| 50x lower cost | Object storage (S3, GCS, Azure Blob etc.) as primary storage. Compute-storage separation scales without pain. |
| SQL + PromQL | Monitor with PromQL, analyze with SQL. One database replaces Prometheus + your data warehouse. |
| Sub-second at PB-EB scale | Columnar engine with fulltext, inverted, and skipping indexes. Written in Rust. |
✅ Perfect for:
Why Observability 2.0? The three-pillar model (separate databases for metrics, logs, traces) creates data silos and operational complexity. GreptimeDB treats all observability data as timestamped wide events in a single columnar engine — enabling cross-signal SQL JOINs, eliminating redundant infrastructure, and naturally supporting emerging workloads like AI agent observability. Read more: Observability 2.0 and the Database for It.
Learn more in Why GreptimeDB.
| Feature | GreptimeDB | Prometheus / Thanos / Mimir | Grafana Loki | Elasticsearch |
|---|---|---|---|---|
| Data types | Metrics, logs, traces | Metrics only | Logs only | Logs, traces |
| Query language | SQL + PromQL | PromQL | LogQL | Query DSL |
| Storage | Native object storage (S3, etc.) | Local disk + object storage (Thanos/Mimir) | Object storage (chunks) | Local disk |
| Scaling | Compute-storage separation, stateless nodes | Federation / Thanos / Mimir — multi-component, ops heavy | Stateless + object storage | Shard-based, ops heavy |
| Cost efficiency | Up to 50x lower storage | High at scale | Moderate | High (inverted index overhead) |
| OpenTelemetry | Native (metrics + logs + traces) | Partial (metrics only) | Partial (logs only) | Via instrumentation |
Benchmarks:
GreptimeDB can run in two modes:
Read the architecture document. DeepWiki provides an in-depth look at GreptimeDB:
docker pull greptime/greptimedb
docker run -p 127.0.0.1:4000-4003:4000-4003 \
-v "$(pwd)/greptimedb_data:/greptimedb_data" \
--name greptime --rm \
greptime/greptimedb:latest standalone start \
--http-addr 0.0.0.0:4000 \
--rpc-bind-addr 0.0.0.0:4001 \
--mysql-addr 0.0.0.0:4002 \
--postgres-addr 0.0.0.0:4003
Dashboard: http://localhost:4000/dashboard
Read more in the full Install Guide.
Troubleshooting:
4000, 4001, 4002, and 4003 are not blocked by a firewall or used by other services.docker logs greptime for further details.Prerequisites:
gcc/g++/autoconf and glibc library (eg. libc6-dev on Ubuntu and glibc-devel on Fedora)Build and Run:
make
cargo run -- standalone start
Status: RC — marching toward v1.0 GA! GA (v1.0): March 2026
GreptimeDB v1.0 represents a major milestone toward maturity — marking stable APIs, production readiness, and proven performance.
Roadmap: v1.0 highlights and release plan and 2026 roadmap.
For production use, we recommend using the latest stable release.
If you find this project useful, a ⭐ would mean a lot to us!
We invite you to engage and contribute!
GreptimeDB is licensed under the Apache License 2.0.
Running GreptimeDB in your organization? We offer enterprise add-ons, services, training, and consulting. Contact us for details.
Special thanks to all contributors! See AUTHORS.md.