Asopitech VS
VictoriaMetrics vs Alopex Skulk
VictoriaMetrics single-node and cluster versions, MetricsQL and its many ingestion formats, compared with Alopex Skulk.
Updated: Oct 13, 2026
What VictoriaMetrics is
VictoriaMetrics is an open source time-series database and monitoring product. It can be used as long-term storage for Prometheus.
How it works
- Single-node and cluster versions: a version that runs as a single executable, and a cluster version split into storage, ingestion and query services.
- Ingestion: accepts Prometheus scraping and remote write, InfluxDB, Graphite, OpenTSDB, JSON, CSV, OpenTelemetry and other formats.
- Queries: MetricsQL, an extension of PromQL.
Main features
- A global query view across data from multiple Prometheus instances.
- Configurable retention.
- The vmagent agent and the vmalert alerting component.
Limits
VictoriaMetrics runs as a server separate from the application. Scaling out means combining the components of the cluster version, and the agent and alerting are separate components as well. The query language is MetricsQL.
How it differs from Alopex Skulk
Both ingest the Prometheus and InfluxDB formats and query with a PromQL-family language.
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. Embedded, server and cluster are one engine, and the same data can be aggregated with SQL.
We recommend Alopex Skulk for handling metric ingestion and queries on one engine from embedded to cluster. Try it from the Alopex Skulk page.