VeltrixDB Documentation
VeltrixDB is an NVMe-native distributed key-value database. Values live on NVMe in an append-only log with ~1.0× write amplification (WiscKey KV-separation); the index and hot values stay in DRAM. This is the complete reference for building, deploying, and operating it.
| Benchmark | Result |
|---|---|
| Reads/s (measured — YCSB 0.17, single node, 4×NVMe) | 427,697 |
| Durable writes/s (fsync every write) | 18,064 |
| Read latency (avg, 200 threads) | 461 µs |
| Write amplification | ~1.0× |
| Storage density, 1B × 128 B values | ~160 GB |
Full benchmark methodology and hardware spec →
What's new in 1.1.0
Start here
Explore the docs
Why VeltrixDB
Redis keeps everything in RAM — a billion 128-byte keys needs roughly 250 GB of memory, on the order of $3,000–5,000/month in cloud RAM. VeltrixDB keeps values on NVMe and only a 64-byte pointer per key in DRAM, so the same dataset fits in about 160 GB of NVMe for roughly $300–500/month. LSM-based stores like RocksDB typically see 10–30× write amplification from compaction; VeltrixDB's WiscKey-style KV-separation keeps that close to 1.0×.
See the honest trade-offs in Limitations & Roadmap and a feature-by-feature breakdown in VeltrixDB vs. Redis.