What maps to what: migrate from Redis to KiviDB

The command reference has every command, and Redis compatibility summarises the differences.

RedisKiviDB
ProtocolRESP2, RESP3RESP2, RESP3
Commands run onOne threadEvery core
Default port63796380 (KiviDB Cloud: 6379, or 6380 with TLS)
Data typesStrings, lists, sets, sorted sets, hashes (field expiry from 7.4), streams, bitmaps, geo, HyperLogLogThe same, with field expiry
Lua (EVAL, EVALSHA, FUNCTION)Built inThe lua and full builds; a switch when you create a KiviDB Cloud database. The default build answers with an error
TLSBuilt inThe tls and full builds; on or required per database on KiviDB Cloud
Search, JSON, time series, vectorsModules, or built into Redis 8Built in
Modules (MODULE LOAD)SupportedNot supported
ACL usersACL file, ACL SETUSERACL file, ACL SETUSER; KiviDB Cloud: users in the console
PersistenceRDB save points, AOFAOF (--aof), BGSAVE; save points are accepted and do nothing
ReplicationREPLICAOFREPLICAOF, and replicating from a Redis primary
SentinelSupportedNot implemented. Use cluster mode, the Kubernetes operator or KiviDB Cloud for failover
Cluster16,384 hash slots16,384 hash slots, the same CLUSTER commands. KiviDB nodes cluster only with KiviDB nodes
Search text matchingStemming, phoneticWhole words, prefixes, suffixes, infixes and fuzzy; no stemming or phonetic matching
Config fileredis.confkividb.conf, read strictly: an unknown directive stops the server

The command reference has every command, and Redis compatibility summarises the differences.

Which build

KiviDB ships four builds of each release:

BuildIncludesUse it when
defaultthe serveryou use no Lua scripts and no TLS
luaLua scriptingyou use EVAL, EVALSHA or FUNCTION (BullMQ, Sidekiq and many locking libraries do)
tlsTLSclients connect over TLS
fullLua and TLSyou are not sure; this is the general-purpose build

The Docker image tags follow the same names, e.g. kividb/kividb:v1.2.0-full. The release files are kividb-linux-x86_64.tar.gz, kividb-lua-…, kividb-tls-… and kividb-full-….