redis-cli

works.

RESP3 wire protocol. Your existing clients, CLIs, and libraries connect without modification. Same commands. Same responses. Extra audit context.

redis-cli 8.2✓ verified
redis-py 7.4✓ verified
ioredis 5.6✓ verified
Jedis 5.2✓ verified
go-redis 9.7✓ verified
Lettuce 6.5✓ verified
Same session. Different foundation.
Redis 8.2
$ redis-cli -p 6379
127.0.0.1:6379>
AUTH mypassword
OK
SET user:42 "ada"
OK
GET user:42
"ada"
DEL user:42
(integer) 1
INFO server
# Server
redis_version:8.2.0
Zaps 0.1.0RESP3
$ redis-cli -p 6380
zaps://localhost:6380>
AUTH agent:scout zap_sk_live_abc
OK — principal: did:oas:zaps:agent:scout
scopes: [read, write] · keyspace: agent:*
SET user:42 "ada"
OK — audited · witness: 0x7f3a…c2d1
GET user:42
"ada"
DEL user:42
(integer) 1 — audited · chain: #849
INFO server
# Server
zaps_version:0.1.0 (RESP3-compat)

█ Highlighted lines are Zaps extras — audit witness, DID identity, scope binding

Command support
0
Redis commands supported
Strings
0/8
Hashes
0/6
Lists
0/6
Sets
0/5
Keys
0/7
Server
0/5
Migration

Change the port. Keep the code.

Your application connects to port 6380 instead of 6379. That is the entire migration. Everything else — clients, libraries, connection pools — stays the same.

:6379→:6380

Your tools already work.

redis-cli, redis-py, ioredis, Jedis, go-redis, Lettuce. All verified. All compatible.

Next: SDKs →Back to Real-Time