GreptimeDB
by GreptimeDB · One database for metrics, logs, traces and wide events
BenchRank score
Screenshots of GreptimeDB
Homepage
Overview
GreptimeDB is an observability database that stores metrics, logs, traces and wide events as timestamped events in one columnar engine on object storage. It ingests via OpenTelemetry, Prometheus remote write and other protocols, and is queried with SQL and PromQL, including joins across signals. A Flow engine derives metrics from raw events via streaming and materialised views.
- Best for
- Teams consolidating metrics, logs and traces into one observability backend on object storage
- Pricing
- Open source is free under Apache 2.0; fully-managed Enterprise starts at $290/month, and bring-your-own-cloud Enterprise is custom-priced.
- Runs on
- macOSSelf-hostedCLI
Strengths and trade-offs
Strengths
- Metrics, logs, traces and wide events in one database
- Queried with SQL and PromQL; OpenTelemetry and Prometheus ingest
- Apache 2.0 open source, standalone or cluster deployment
- Object storage first, so compute and storage scale separately
Trade-offs
- Auto-scaling, RBAC/LDAP and security audit are Enterprise-only
- Open source gets only basic auth, encryption and dashboard tooling
- Triggers and edge-cloud sync are marked N/A on the open-source tier
- Managed pricing published only as 'from $290/month', no full rate card
How GreptimeDB markets itself
A structured read of the promise, proof and page design on GreptimeDB’s captured homepage.
Homepage capture
“The Single Database for Observability”
- Angle: All-in-one / consolidation
- Hero: Abstract graphic
Pricing
Published plans and prices from GreptimeDB’s own pricing page.
How this score is made up
Each dimension is scored out of 100 and combined into the headline score using fixed weights.
MCP support
Whether an agent can drive the product through the Model Context Protocol, and how much setup that takes.
API quality
Public API surface: machine-readable spec, official SDKs, documented auth, errors, rate limits and versioning.
Documentation
Publicly reachable docs — coverage, freshness, code samples and machine readability.
Agent friendliness
How readable the site is to an automated client: llms.txt, structured data, server-rendered content, crawler access.
Pricing transparency
Whether real prices are published, self-serve signup exists, and usage costs are knowable without a sales call.
Changelog
A public, dated record of what shipped and when — the clearest signal that a product is still alive.
Marketing site structure
Whether the site answers a buyer's questions: clear positioning, the pages that matter, and accessibility.
Page speed
How fast the site loads for real visitors: Chrome UX Report 75th-percentile LCP, INP and CLS, with a Lighthouse mobile run standing in where a site has too little traffic for field data.
Operational trust
Status page and incident history, security disclosure, compliance and data-processing documentation.
Measured, but not part of the score
Useful to know, but not a mark for or against the product — so these do not affect the ranking.
Openness
Source availability, self-hosting, data export and open standards. Scored and shown, but not part of the composite — paid SaaS is not worse for being paid SaaS.
Maintenance
Release cadence and repository activity. Scored and shown, but not part of the composite — it is only measurable for open repositories.
This doesn’t look right — report a problem with GreptimeDB’s score
Where this comes from
The GreptimeDB pages BenchRank reads when it scores the product — its documentation, release notes, status and security pages, and its repository where there is one.
Alternatives in Monitoring & Observability
Ranked 1
87.4 — BenchRank score out of 100openstatus
OpenStatus · Open source status pages with uptime monitoring from 28 regions
Best for: Teams that need a public status page and uptime checks while working towards SOC 2.
Ranked 2
86.7 — BenchRank score out of 100OneUptime
OneUptime · Open-source observability and incident management on one platform
Best for: Teams wanting monitoring, on-call, status pages and observability on one open-source platform
Ranked 3
83.1 — BenchRank score out of 100Sentry
Sentry · Error tracking and application performance monitoring for developers
Best for: Development teams wanting error monitoring, tracing and session replay tied to one trace
Is this your product?
Claim GreptimeDB to manage its profile. Claiming lets you suggest edits to the descriptive fields — it never changes scores or rankings.