GreptimeTeam/greptimedb
The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage.
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
5 releases in the last 90 days, the latest 2 days ago, with 168 contributors on GitHub.
Use Cases & Benefits
- Provides an open-source observability database unifying metrics, logs, and traces on object storage with SQL and PromQL querying.
- Delivers up to 50x lower storage costs and seamless scaling by using object storage and compute-storage separation.
- Use for replacing Prometheus, Loki, and Elasticsearch with a single backend for all observability signals.
- Use for analyzing high-cardinality, long-term observability data at petabyte to exabyte scale with sub-second query latency.
- Use for AI/LLM observability to store and analyze large volumes of conversation data and agent traces using OpenTelemetry GenAI conventions.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Apache 2.0
Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.
Community files
- README: present
- Contributing guide: present
- Code of conduct: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
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.
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.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
+236 stars over 82 days across 10 snapshot days; best day +16 on Sep 4.
Forks
576+53
Open issues
337+114
Compared with peers in Analytics
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| openobserve/openobserve | 22.8K | +235 | 40 | today |
| algorithm-visualizer/algorithm-visualizer | 49.4K | +130 | 30 | — |
| itsPLK/ps5-payload-manager | 715 | +33 | 38 | 16 days ago |
| ant-design/ant-design-pro | 38.9K | — | 56 | 80 days ago |
| Canner/WrenAI | 18.1K | — | 65 | 7 days ago |
| GreptimeTeam/greptimedb | 6.8K | — | 65 | 2 days ago |
| Category median | 22.8K | +130 | 40 | — |
Discover Repositories
Search across tracked repositories by name or description