SQL and PromQL
SQL over MySQL, PostgreSQL, or HTTP. PromQL for metrics.
GreptimeDB Enterprise
Build your observability data platform on object storage. Query telemetry with SQL, connect it to your analytics stack, and make it available to engineers and AI agents.
Workloads
Keep every high-cardinality series at full resolution, for as long as you need it.
One table, two query languages
sum by (namespace) (
rate(container_cpu_usage_seconds_total[5m])
)SELECT namespace, approx_distinct(pod) AS pods
FROM container_cpu_usage_seconds_total
WHERE greptime_timestamp > now() - INTERVAL '1' DAY
GROUP BY namespace;Scale and cost
Data lives in object storage. You add nodes for throughput, not for disk.
Data and indexes sit in S3, GCS, Azure Blob, or OSS. Nodes keep only a cache.
Add ingest or query capacity on its own. Enterprise repartitions and rebalances automatically.
Indexes and a local cache keep queries fast over object storage.
Get a cost estimate
Tell us your daily volume, retention, and where you deploy. An engineer sizes the cluster and the monthly cost.
Request an estimateAnalytics and agents
One copy of the data serves dashboards, SQL, lakehouse engines, and agents.
SQL over MySQL, PostgreSQL, or HTTP. PromQL for metrics.
Parquet in your bucket. Spark, Trino, and DuckDB read it through the Iceberg REST catalog, no copy.
Agents query through the GreptimeDB MCP Server with read-only SQL and PromQL.
Your collectors, Grafana, Alertmanager, and lakehouse tables.
Customers
“…just because we found that it was more effective.”
Per-task Spark metrics add millions of new series a day. OpenAI moved Spark metrics, events, and logs into GreptimeDB, read by Grafana, a Rust Spark History Server, and an internal agent.
From two OpenAI talks at Apache Community Over Code EU 2026.
Read the talk recapOne GreptimeDB cluster per public cloud, on that cloud's object storage. Searches that timed out on Loki now come back in about a second.
Read the case studyEvaluation
One workload, clear pass criteria, real traffic.
A metric source or log stream with a known pain.
Volume, retention, and the queries that must keep working.
Throughput, query latency, storage, and monthly cost.
Mirror real traffic and compare with what you run today.
Talk to an engineer
An engineer reads your request and replies within one business day.
You agree on one workload and its pass criteria.You run GreptimeDB Enterprise on your own data.
Prefer to try it first? Open the live demo or download GreptimeDB. Compare open source and Enterprise.