Migrate from Redis to Cache-Pot without changing code

Cache-Pot is a drop-in Redis replacement for most use cases. It speaks RESP2 over the wire, so any Redis client library — ioredis, redis-py, go-redis, Lettuce, Jedis — connects and works without a single line of code changing. For the vast majority of apps that use Redis as a cache or key/value store, pointing the connection string at Cache-Pot is all you need to do.

What’s compatible

Cache-Pot implements all the command groups you rely on day-to-day:

Strings

GET, SET, MGET, MSET, INCR, APPEND, GETRANGE, and more

Hashes

HSET, HGET, HGETALL, HDEL, HMGET, HKEYS, HVALS, HLEN

Lists

LPUSH, RPUSH, LPOP, RPOP, LRANGE, LLEN, LINDEX

Sets

SADD, SREM, SMEMBERS, SISMEMBER, SCARD

Sorted Sets

ZADD, ZREM, ZSCORE, ZRANGE, ZRANGEBYSCORE, ZCARD

Pub/Sub

SUBSCRIBE, UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBLISH

Transactions

MULTI, EXEC, DISCARD, WATCH, UNWATCH

Key Expiry

EXPIRE, PEXPIRE, EXPIREAT, TTL, PTTL, PERSIST

Iteration

SCAN, HSCAN, SSCAN, ZSCAN with MATCH and COUNT

Auth & Select

AUTH, SELECT 0, PING, QUIT, ECHO

Server

INFO, DBSIZE, FLUSHDB, SAVE, BGSAVE, BGREWRITEAOF

Observability

MONITOR, SLOWLOG, CLIENT LIST, CONFIG GET/SET

What’s different

Cache-Pot is honest about where it diverges from Redis. These differences only matter if your current setup uses the specific features listed below.

If you use Redis purely as a cache or key/value store, none of these differences will affect you.

Feature	Redis	Cache-Pot
Multiple databases	`SELECT 0` through `SELECT 15`	`SELECT 0` only — `SELECT 1+` returns an error
Clustering & replication	Full support	Single-node only in v1
Protocol version	RESP2 and RESP3	RESP2 only
RedisSearch / RedisJSON modules	Available as add-ons	Not available — Cache-Pot has its own `VSET`/`VSEARCH` and `SCACHE.*` commands

If your application calls SELECT with a database index greater than 0, it will receive an error. Audit your codebase for SELECT usage before switching.

Migration steps

Install Cache-Pot

Install via Go, Docker, or build from source:

go install github.com/subh05sus/cache-pot/cmd/cache-pot@latest
cache-pot

docker run -p 6379:6379 -p 8080:8080 ghcr.io/subh05sus/cache-pot:latest

git clone https://github.com/subh05sus/cache-pot
cd cache-pot
go run ./cmd/cache-pot

Cache-Pot starts listening on :6379 by default — the same port Redis uses.

Export your data from Redis (if you need it)

Cache-Pot uses its own snapshot format, not Redis’s RDB format. If you have data in Redis that needs to carry over, export it using redis-cli and replay the writes:

# Dump a snapshot from your existing Redis instance
redis-cli --rdb dump.rdb

# Cache-Pot cannot load RDB files directly.
# Replay key writes using a script or redis-cli --pipe against Cache-Pot.

For a fresh start or when migrating only the connection (not the data), skip this step entirely.

Update your connection string

Point your application at Cache-Pot. If Cache-Pot is running locally on the default port, your connection string likely does not need to change at all:

# Most apps read this from an environment variable
export REDIS_URL=redis://localhost:6379

Configure authentication (if you use AUTH)

If your Redis instance requires a password, start Cache-Pot with the same password using --auth or the CACHEPOT_AUTH environment variable:

cache-pot --auth mysecretpassword

# Or via environment variable
CACHEPOT_AUTH=mysecretpassword cache-pot

Verify the connection

Confirm everything is working by connecting and running PING:

redis-cli -p 6379 PING
# Expected: PONG

redis-cli -p 6379 SET hello world
redis-cli -p 6379 GET hello
# Expected: "world"

Client library examples

No code changes are required — only the server address changes (and only if Cache-Pot is on a different host).

Node.js (ioredis)
Python (redis-py)
Go (go-redis)

// Before: Redis
const Redis = require('ioredis');
const client = new Redis('redis://localhost:6379');

// After: Cache-Pot (no code change needed)
const client = new Redis('redis://localhost:6379'); // same!

// Everything works as before
await client.set('hello', 'world');
const value = await client.get('hello');
console.log(value); // "world"

# Before: Redis
import redis
r = redis.Redis(host='localhost', port=6379)

# After: Cache-Pot (no code change needed)
r = redis.Redis(host='localhost', port=6379)  # same!

# Everything works as before
r.set('hello', 'world')
print(r.get('hello'))  # b'world'

// Before: Redis
rdb := redis.NewClient(&redis.Options{Addr: "localhost:6379"})

// After: Cache-Pot (no code change needed)
rdb := redis.NewClient(&redis.Options{Addr: "localhost:6379"}) // same!

// Everything works as before
err := rdb.Set(ctx, "hello", "world", 0).Err()
val, err := rdb.Get(ctx, "hello").Result()
fmt.Println(val) // "world"

Once you have migrated, explore Cache-Pot’s AI extensions. Vector search (VSET / VSEARCH) and semantic caching (SCACHE.SET / SCACHE.GET) are available with no additional setup — except an embedding endpoint for the semantic cache. They run through the same RESP2 connection your existing client already holds.

Get Started

Core Concepts

Configuration

Guides

Dashboard

Migrate from Redis to Cache-Pot without changing code

What’s compatible

Strings

Hashes

Lists

Sets

Sorted Sets

Pub/Sub

Transactions

Key Expiry

Iteration

Auth & Select

Server

Observability

What’s different

Migration steps

Client library examples

​What’s compatible

Strings

Hashes

Lists

Sets

Sorted Sets

Pub/Sub

Transactions

Key Expiry

Iteration

Auth & Select

Server

Observability

​What’s different

​Migration steps

​Client library examples

What’s compatible

What’s different

Migration steps

Client library examples