KiviDB: vendor claims and pricing, captured before any test
Source: README.md of github.com/kividbio/kividb (default branch master), fetched 2026-10-20 11:17 UTC+8 via the GitHub API
Repo created 2026-10-16; release used: v1.1.0 linux x86_64 prebuilt binary (tarball sha256 66b22d41ab5b9404994228b618a9f98c534c2017b53ef17c1d38f1733d99c62d; binary sha256 cf374f483c5bf7e1c6432db88daadc3eb9e969b831472f5bcf2b0a8fdf189aee)

--- README lines 7-14 (verbatim) ---
**KiviDB** is a fast, multi-threaded alternative to Redis® and Valkey, written in Rust. It
speaks the Redis protocol (RESP2 and RESP3), so existing Redis clients, `redis-cli` and
libraries work unchanged, and it has full-text and vector search built in. It runs every
core on a sharded in-memory key-value design, and persists to snapshots and an optional
append-only file.

On the same 32 cores, KiviDB serves **21 million pipelined GETs per second: about 9× Redis 8
and 2.3× Dragonfly**, with under half Dragonfly's p99 latency ([benchmarks](#performance)).

--- README lines 25-29 (verbatim) ---
- **Search and vectors**: Redis Stack–style `FT.*` commands for full-text, tag, numeric and vector (FLAT / HNSW) search
- **Lua scripting**: optional Cargo feature. `EVAL`, `SCRIPT`, `FUNCTION`, `FCALL` and related commands are available in builds with `--features lua` (see [Scripting commands (Lua)](COMMANDS.md#scripting-commands-lua))
- **TLS**: optional Cargo feature (`--features tls`)
- **Default listen address**: `0.0.0.0:6380`, with [protected mode](#protected-mode) on
- **License**: [GNU Affero General Public License v3](LICENSE) (AGPL-3.0-only), open source; using KiviDB does not put your application under the AGPL; see [License](#license)

--- README lines 53-70 (benchmark setup + key-value table, verbatim) ---
All figures below are from one session in October 2026 on AWS Graviton3 bare metal: the
server on a `c7gn.metal` (64 vCPU), confined to 32 cores, and the load generator on a
second `c7gn.metal` in the same placement group. Each engine ran alone on the server,
one after another.

### Key-value

memtier_benchmark through kivi-benchmark's `run-matrix.sh`: 10 million keys, 100-byte
values, 30 s a scenario, mean of two rounds; 300 connections pipelined, 1,200 without
pipelining.

<picture>
  <source media="(prefers-color-scheme: dark)" srcset="assets/benchmarks/throughput-pipelined-dark.png">
  <img src="assets/benchmarks/throughput-pipelined-light.png" alt="Pipelined throughput: KiviDB, Dragonfly, Redis, Redis Cluster" width="720">
</picture>

| ops/s | KiviDB 1.1.0 | Dragonfly 2.0.2 | Redis 8.10 | Redis Cluster (32 shards) |
|---|------:|------:|------:|------:|

--- README lines 84-98 (vector table, verbatim) ---

[redis/vector-db-benchmark](https://github.com/redis/vector-db-benchmark) on
glove-25-angular (1.18M vectors, 25 dimensions): HNSW with M=16 and EF_CONSTRUCTION=256,
100 clients uploading in batches of 64, then queries at ef 64, 128, 256 and 512.

<picture>
  <source media="(prefers-color-scheme: dark)" srcset="assets/benchmarks/vector-qps-recall-dark.png">
  <img src="assets/benchmarks/vector-qps-recall-light.png" alt="Vector search: queries per second against recall" width="720">
</picture>

| | KiviDB 1.1.0 | Dragonfly 2.0.2 | Redis 8.10 (query engine) |
|---|------:|------:|------:|
| Queries/s at ef 64 (recall@10) | **59.3k** (0.943) | 41.3k (0.912) | 31.8k (0.912) |
| Queries/s at ef 128 | **50.7k** (0.961) | 40.3k (0.937) | 28.9k (0.937) |
| Queries/s at ef 256 | 31.5k (0.989) | **36.2k** (0.979) | 21.1k (0.979) |

--- README line 141 (snapshots, verbatim) ---
- Native snapshots (**`dump.kdb`**) store the **keys**, the **index schemas**, and, when you **`SAVE` / `BGSAVE`** with indexes populated, the **HNSW graph** of each vector field, so search quality after a restart matches the graph you had before shutdown.

--- README lines 355-372 (startup update check, verbatim) ---
### Startup update check

When it starts, a release build of KiviDB makes **one HTTPS request** to
`https://github.com/kividbio/kividb/releases/latest`, the same page you would open to find
the newest release. GitHub answers with a redirect to that release's tag; if it is newer
than the running build, KiviDB prints a short notice with the link before the startup
banner. Nothing is sent but the request itself, with a `User-Agent` of `kividb/<version>`:
no host name, configuration, keys, data or identifier. GitHub sees the request's source IP
address, as any web server would.

Startup waits at most 1.5 seconds for the reply; a failure is logged at debug level only and
never affects clients. Only a version-shaped tag is accepted from the reply, and nothing
else from it is printed.

Any one of these turns it off:

- `--update-check no` on the command line;
- `update-check no` in the configuration file;

--- Pricing ---
Free. AGPL-3.0-only (README lines 397-411); a commercial licence is offered by KIVIDB PRIVATE LIMITED via support@kividb.io, no public price. No account, key or signup needed for anything we tested.