vs

GreptimeDB vs VictoriaMetrics

GreptimeDB: Rust observability database that keeps metrics, logs and traces in one columnar engine on object storage. VictoriaMetrics: Resource-frugal, Prometheus-compatible metrics database, run as a single binary or a sharded cluster.

key differences

  • Only GreptimeDB has joins, secondary indexes, full-text search, json, materialized views.
  • GreptimeDB has a serverless option; VictoriaMetrics does not.

choose greptimedb for

  • +Unified observability backend for metrics, logs and traces
  • +Prometheus long-term storage on S3
  • +IoT and connected-vehicle telemetry
  • +Edge data collection synced to the cloud

best at · Observability, Time-series, IoT

choose victoriametrics for

  • +Long-term storage for Prometheus metrics
  • +Kubernetes monitoring with vmagent and the operator
  • +Consolidating Graphite, Influx and Prometheus metrics in one store
  • +High-rate IoT telemetry

best at · Observability, Time-series, IoT

overview
Primary model
Time-Series
Time-Series
Also supports
Columnar / OLAP, Search Engine
–
Type
Database engine
Database engine
Status
Active
Active
Developer
Greptime
VictoriaMetrics Inc.
First release
2022
2018
Latest version
1.2.1 (Sep 16, 2026)
1.155.0 (Oct 26, 2026)
License
Open source (permissive)Apache License 2.0
Open source (permissive)Apache License 2.0
Free tier
✓
✓
popularity
WhichDB Score
15.1
26.8
Rank
#221
#109
GitHub stars
6.8K
17.9K
Stack Overflow questions
–
143
scale & guarantees
Comfortable data size
Large (≤ 1 PB)
Large (≤ 1 PB)
Horizontal scaling
Native
Native
Multi-region
None
None
ACID
None
None
Consistency
Strong
Eventual
Schema
Flexible
Schemaless
Architecture
Single node, Distributed, Shared storage
Single node, Distributed, Client server
deployment
Self-hosted
✓
✓
Vendor-managed cloud
✓
✓
Serverless
✓
—
Embedded
—
—
Edge
✓
—
Clouds
AWS
AWS
capabilities
Transactions
—
—
Joins
✓
—
Secondary indexes
✓
—
Full-text search
✓
—
Vector search
—
—
Geospatial
—
—
JSON
✓
—
Change data capture
—
—
Triggers
—
—
Stored procedures
—
—
Materialized views
✓
—
TTL / expiry
✓
✓
Pub/Sub
—
—
Columnar storage
✓
—
In-memory
—
—
Durable persistence
✓
✓
Compression
✓
✓
Encryption at rest
—
—
Role-based access
—
—
Time travel
—
—
Branching
—
—
Online schema changes
—
—
Streaming ingest
✓
✓
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
SQL, PromQL
MetricsQL, PromQL
Client languages
Go, Java, Rust, JavaScript
–
Best for
Observability, Time-series, IoT, Real-time analytics
Observability, Time-series, IoT

GreptimeDB vs VictoriaMetrics: FAQ

What is the difference between GreptimeDB and VictoriaMetrics?

GreptimeDB: Rust observability database that keeps metrics, logs and traces in one columnar engine on object storage. VictoriaMetrics: Resource-frugal, Prometheus-compatible metrics database, run as a single binary or a sharded cluster. Only GreptimeDB has joins, secondary indexes, full-text search, json, materialized views. GreptimeDB has a serverless option; VictoriaMetrics does not.

When should I choose GreptimeDB over VictoriaMetrics?

Choose GreptimeDB for unified observability backend for metrics, logs and traces; prometheus long-term storage on S3; and IoT and connected-vehicle telemetry. Choose VictoriaMetrics for long-term storage for Prometheus metrics; kubernetes monitoring with vmagent and the operator; and consolidating Graphite, Influx and Prometheus metrics in one store.

Is GreptimeDB or VictoriaMetrics more popular?

VictoriaMetrics ranks #109 on the WhichDB Score (26.8/100) and GreptimeDB ranks #221 (15.1/100). Popularity is not fit: check the requirements that matter for your project.

Are GreptimeDB and VictoriaMetrics open source?

Yes. GreptimeDB is open source. License: Apache License 2.0. Yes. VictoriaMetrics is open source. License: Apache License 2.0.