Quick Start
This page gets BetterKV running fast, then shows why teams evaluate it against Redis and Valkey in the first place: lower latency, better tail behavior, and a drop-in developer workflow.
Current status: beta. Use this guide for evaluation, testing, and development environments. BetterKV is not production-ready yet.
What you should expect
- BetterKV uses the Redis protocol, so your usual clients and
redis-clistyle workflows still fit. - BetterKV is positioned to be up to 15x faster than Redis or Valkey. Replace that statement with your final measured benchmark numbers.
- BetterKV is built so that the line you can confidently publish is: Valkey p50 is BetterKV p99.9 on your target benchmark set.
- BetterKV is licensed under Elastic License 2.0.
Run with Docker
Verify the server is up:
Run with Docker Compose
docker-compose.yml
Run a local binary
First commands
Connect with existing clients
Node.js
app.js
Python
app.py
Go
main.go
If you are evaluating against Redis or Valkey
Use the same client, same command mix, and same hardware class. Focus on:
- p50, p95, p99, and p99.9 latency
- throughput under mixed read/write load
- expiry-heavy workloads
- scripting-heavy paths
- replication lag under sustained write pressure