Every platform team running vanilla Prometheus eventually hits the same wall: the local TSDB is a single-node database, retention fights with disk space, and the "just add Thanos" answer adds four more services than anyone wanted. VictoriaMetrics — the Apache-2.0 TSDB from the Latvia-based company of the same name — is the most credible "just replace the storage" answer in the CNCF-adjacent market, and this week it shipped v1.153.0 with two security advisories, OIDC single sign-on, and a batch of operational fixes. The repository turned eight years old the same week — created 2018-09-30, now at 17,788 stars and a release cadence that lands a minor every two weeks.

We didn't read about this one: we downloaded the actual v1.153.0 linux-amd64 binary, verified its SHA-256 checksum against the published checksums file, and ran it through a 300,000-sample high-churn ingest, restart cycles, Unix-socket permission tests, and a deliberate probe of every admin endpoint. The result is a two-sided verdict, like most honest ones: the storage engine is genuinely excellent, the release hygiene is better than most vendors', and the operational defaults contain at least three traps that will bite anyone who deploys it the way the quickstart suggests.

Executive Scorecard

DimensionScoreWhy
Reliability8/100.2s clean shutdown, 0.2s storage reopen with all 503,613 rows intact, per-URL persistent disk queues in vmagent; monthly partitions make retention pruning a non-event. Loses points for a 5-second unflushed-data window and single-node being a single point of failure by design
DX7/10Drop-in Prometheus remote-write target, MetricsQL is a strict superset, vmui is genuinely useful; but ~1,000 flags, a two-stage data-visibility model (5s flush + 30s latency offset) that looks like data loss until you read the docs, and dashboards that silently show nothing for fresh series
Cost9/10 community / 4/10 enterpriseCommunity edition is free and includes the full storage engine; downsampling, multiple retentions, and automatic vmstorage discovery are Enterprise-gated behind a quote-only plans page, or a managed VictoriaMetrics Cloud
Security5/10v1.153.0 fixes a memory-exhaustion advisory in the native import path and an OIDC redirect flaw, and adds OIDC SSO — but /api/v1/admin/tsdb/delete_series accepts unauthenticated deletes out of the box, and the docs' own security section assumes you'll front everything with vmauth yourself

Scope note, the honest kind: all numbers below were measured on this review's host — 4 CPU cores, 30 GB RAM, local SSD, single-node binary, default flags unless stated. They are single-run wall-clock numbers from a working benchmark, not a normalized multi-host benchmark suite; treat them as directional, and re-run on your own hardware before making a procurement decision. What they reliably demonstrate is the shape of the system: where it's fast, where it's clever, and where it will surprise your on-call engineers.

Architecture Mechanics: What Actually Runs

The single-node binary is one process with one job: absorb samples, index them, keep queries off the disk where possible. The design choices that matter operationally are all visible in the startup log:

  remote writers (Prometheus, vmagent, OTel, Influx, Datadog agent)
        |
        |  /api/v1/write  (snappy+protobuf remote write)
        |  /api/v1/import/prometheus  (exposition text, fastest bulk path)
        |  /api/v1/import  (JSON line)
        |  /api/v1/import/csv, /influx/write, /opentelemetry/v1/metrics
        v
  +-----------------------------------------------------+
  |  victoria-metrics-prod  (single process)            |
  |                                                     |
  |  in-memory rows --flush every 5s--> data parts      |
  |      (-inmemoryDataFlushInterval, min 1s)           |
  |                                                     |
  |  storage layout (per -storageDataPath):            |
  |   data/data/small/YYYY_MM   small parts             |
  |   data/data/big/YYYY_MM     big parts (compacted)   |
  |   data/indexdb/YYYY_MM      inverted index          |
  |   cache/rollupResult        query result cache      |
  |   snapshots/, metadata/, tmp/                        |
  |                                                     |
  |  monthly partitions: retention prune = drop month   |
  |  adaptive limits at boot:                           |
  |    -search.maxUniqueTimeseries derived from         |
  |    remaining RAM (925,535 on this 30GB host)        |
  +-----------------------------------------------------+
        |
        |  PromQL/MetricsQL queries, -search.latencyOffset=30s
        |  (samples < 30s old excluded by default)
        v
  /api/v1/query, /api/v1/query_range, /api/v1/series,
  /api/v1/export, Graphite API, vmui (web UI)