Asopitech VS
GreptimeDB vs Alopex Skulk
How GreptimeDB unifies metrics, logs and traces and stores them on object storage, compared with Alopex Skulk.
Updated: Oct 13, 2026
What GreptimeDB is
GreptimeDB is an open source observability database that handles metrics, logs and traces in one engine. It is written in Rust.
How it works
- Storage: data can live on object storage.
- Ingestion: accepts Prometheus remote write, OpenTelemetry and more.
- Queries: SQL and PromQL.
Main features
- Unified storage of metrics, logs and traces.
- Standalone start and cluster operation.
- Reads through the Jaeger API.
Limits
Whether standalone or clustered, GreptimeDB runs as a server separate from the application. Read replicas are a feature of the GreptimeDB Enterprise cluster edition.
How it differs from Alopex Skulk
Both are written in Rust and query Prometheus data with SQL and PromQL.
Alopex Skulk is a time-series engine written in Rust that grows from embedded to server to cluster on the same engine. Start small by embedding it in your application, then move the same application to a server with Prometheus-compatible endpoints and to a cluster that scales out with sharding and replication. In every form it ingests time series, queries them with PromQL and SQL, stores them in time-partitioned, columnar Parquet files, and drops expired partitions automatically. It starts embedded and shipped with the application and grows to a replicated cluster on the same engine.
We recommend Alopex Skulk for growing a time-series engine that reads with SQL and PromQL from your application binary to a cluster. Try it from the Alopex Skulk page.