Skip to content
Home / Migrations / Redis (redis npm)Valkey (iovalkey)

Redis (redis npm) Valkey (iovalkey)

easy

Redis changed its license to non-OSS in 2024. Valkey is the Linux Foundation fork with identical API. Drop-in replacement.

Estimated: 1-2h · 4 steps
Progress0%
Step 1: Replace npm package

iovalkey is the Valkey client, API-compatible with ioredis.

npm uninstall ioredis && npm install iovalkey
Step 2: Update imports

Change import source only. All Redis commands are identical.

// Before: import Redis from 'ioredis'
// After: import Redis from 'iovalkey'
Step 3: Update connection string

Point to your Valkey instance (or AWS ElastiCache Valkey cluster) instead of Redis endpoint.

Step 4: Verify commands

Test SET, GET, HSET, LPUSH, SUBSCRIBE — all Valkey commands match Redis 7.2.

All cache operations work as before

What this migration involves

Moving from Redis (redis npm) to Valkey (iovalkey) is rated easy and takes about 1-2h on a typical project. The guide breaks it into 4 steps, 2 of which ship with runnable commands and 1 with a verification check.

FAQ

How long does migrating from Redis (redis npm) to Valkey (iovalkey) take?

Around 1-2h for a typical project — 4 steps, difficulty rated easy, 2 of them with copy-paste commands.

Is moving from Redis (redis npm) to Valkey (iovalkey) reversible?

No reverse guide is tracked yet, so treat this as a one-way move and keep a full export of your Redis (redis npm) data before you start.

What does Valkey (iovalkey) cost compared to Redis (redis npm)?

Pricing for both tools is contact-based or not tracked yet.