Grow at SSD prices.
Put growing value capacity on NVMe and reduce the need for expensive DRAM upgrades.
Lavik keeps a compact key index in DRAM and stores values on files, raw block devices, or SPDK NVMe namespaces.
Open source. Free to use. · v0.1.0-beta.1↗Faster than Redis.
Faster than Redis.
20× lower
capacity cost.
Replace expensive DRAM with NVMe for your values. Lavik gives Redis / Valkey workloads a new cost structure: familiar Redis clients, a measured million requests per second, and capacity that grows with SSDs.
Apache 2.0RESP2 / RESP3Linux · x86_64 / ARM64
The performance behind the savings
NVMe storage. In-memory-class performance.
1.01M
GET requests / second with SPDK
Lavik stores values on NVMe. Redis and Valkey keep them in memory. In the published 1 KiB experiment, Lavik SPDK exceeded both peers’ peak GET and SET throughput, with comparable p99 latency.
SPDK benchmark · 2026-09-18 · v0.1.0-beta.1Peak throughput · requests / second
Lavik 0.1.0 SPDK1,012,180
p99 3.599 msRedis 8.8.0976,801
p99 4.671 msValkey 9.1.0965,697
p99 4.543 msAMD EPYC 9V74 server, approximately 126 GiB RAM, six NVMe drives, 10 million 1 KiB values, pipeline=1, and 30-second measurement windows. Lavik uses the beta release with SPDK and kernel TCP. Redis and Valkey controls reuse an earlier sweep on the same hosts, with persistence disabled. Each point was measured once; these results do not establish equivalent crash durability or an application SLA. Source report ↗
Why switch from Redis / Valkey?
Keep your Redis clients.
Lavik speaks RESP2 and RESP3 and implements a broad Redis-compatible command surface. Check the commands and operational behavior your application depends on.
Apache 2.0. Free to use.
EloqData-authored Lavik code is available under Apache License 2.0. Third-party components retain their own licenses and notices.
Bring your Redis / Valkey workload
Make your next capacity upgrade NVMe.
Start today