VeltrixDB is now open source — Apache 2.0. 427K reads/s measured on YCSB. ★ Star us on GitHub ↗
MEASUREDYCSB 0.17 · 100M keys · 0 errors

A billion keys.
Sub-5ms reads.
One-tenth the bill.

VeltrixDB keeps your working set on NVMe, not RAM — so latency stays flat, the bill stays flat, and it runs on any cloud.

Free & open source (Apache 2.0) · one binary · production-ready on Kubernetes in 94 seconds.

10× lower cost / GB <5ms P99 · 1B keys 1.0× write amplification
veltrix@nvme — 60-second start
P99 read · 1B keys · NVMe 4.9ms
Built on the systems primitives you already trust
io_uringO_DIRECT NVMeWiscKey KV-separationgroup-commit WALFNV-1a shardingPrometheus / GrafanaKubernetes operatorgRPC
The problem
At a billion keys, you're not paying for a database. You're paying for RAM.

Redis and other in-memory stores keep every value in DRAM — hot or cold. Cloud RAM costs 15–20× more per gigabyte than NVMe SSD, so the bigger your dataset grows, the more you pay simply to hold it in memory. That's a bill that scales with your data, not your revenue.

In-memory (Redis)
$3,000–5,000
/ month · ~250 GB DRAM
  • Every value pinned in memory, hot or cold
  • P99 spikes when AOF rewrite runs
  • Cost grows linearly with dataset size
≈ 10× lower
VeltrixDB on NVMe
$300–500
/ month · ~160 GB NVMe
  • Values on NVMe, only pointers in DRAM
  • Flat P99 — GC never blocks reads
  • Fixed cluster pricing, no per-op meter
Illustrative — 1 billion keys × 128-byte values, GCP list pricing. Your mileage will vary; the ratio won't.
The shift

One idea, executed properly.

Move the bytes to where they're cheap. Keep only what you need in memory. Never let cleanup touch the fast path.

01 · Storage

Values on NVMe

Written once to an append-only log and never rewritten. Compaction only reclaims dead space — so write amplification stays at 1.0×, not the 10–30× of LSM trees.

02 · Memory

Index in DRAM

Only a 64-byte pointer per key lives in memory. A read is one DRAM lookup at ~0.28ms, or exactly one NVMe read at 4.9ms on a miss. No page-cache roulette.

03 · Latency

P99 that holds

GC is rate-limited to your read latency and runs off the fast path. Across 100M operations in the YCSB run: zero errors, zero emergency GC events.

See the full read/write path →
427K/s
Reads / sec / node
Measured — YCSB 0.17, 100M keys, 200 threads.
<5ms
P99 read latency
Sustained at 1B keys, mixed read/write load.
1.0×
Write amplification
Values written once — never rewritten by compaction.
0
Errors / GC events
Across 100M operations in the YCSB run.
What it means for the business

Four numbers your board will care about.

Latency

An SLA you can actually promise.

Sub-5ms P99 at any scale, under any write load — no degradation during traffic spikes, no stalls when background cleanup runs.

<5msP99 · sustained at 1B keys
Cost

A bill that stops chasing your data.

Fixed cluster pricing on NVMe instead of RAM — roughly a tenth of the cost per gigabyte, with no per-operation meter to model.

10×lower cost per GB vs RAM
Portability

No cloud holds you hostage.

One Helm chart runs identically on GKE, EKS, AKS, or bare metal. Change providers without rewriting your data layer or your contracts.

4 platformsGKE · EKS · AKS · Bare metal
Time to value

Days to production, not quarters.

One command deploys storage, replication, auto-scaling, and monitoring — 50+ metrics and dashboards included. No specialist hire, no dark weeks.

94shelm install → ready
Measured, not projected

33ms is the industry's normal. We ship 4.9ms.

P99 read latency at 1 billion keys, sustained mixed load, equivalent hardware. Full run — hardware spec, YCSB config, raw output — on the performance page.

Cassandra
~80ms
~80ms P99
LSM-tree DB
~33ms
~33ms P99
VeltrixDB · miss
4.9ms
4.9ms · cache miss
Full benchmark & methodology Compare against Redis
Documentation

Everything you need to ship on VeltrixDB

Architecture deep-dives, client SDKs for 6 languages, a full config reference, and Kubernetes guides — in one place.

Browse full docs

See your own numbers in 30 minutes.

33ms P99 ───────▶ 4.9ms P99
No commitment · 30-min session · Free migration & cost analysis included