Valkey is the open-source continuation of Redis 7.2, run by the Linux Foundation under the BSD licence. For most teams it is a drop-in replacement. We check what you use, replicate your data, switch clients over in seconds and keep a way back.
Redis 7.4+ moved to source-available licences; your legal team has questions.1
Replicate into Valkey — the BSD-licensed fork — and switch clients in seconds.
Same protocol, same clients, a permissive licence, rollback kept ready.
We give you the facts; the choice is yours.
We use replication wherever we can, so the data is already in place when clients move.
| Your set-up | Route |
|---|---|
| Single instance or primary/replica | Valkey added as a replica, catches up, then promoted; clients switched |
| Sentinel | Valkey nodes join, failover moves the primary, old nodes removed one by one |
| Cluster | Node-by-node replacement with slots moved in a controlled way |
| Managed cloud service | Engine change or a new Valkey instance, depending on what your provider offers |
Commands, data types, Lua scripts and modules you use, checked against Valkey before anything moves.
Replicated, verified, switched — with the old nodes kept as a rollback for an agreed period.
Your client libraries confirmed to work; connection settings updated where needed.
Memory, latency and replication alerts on the new nodes.
Failover, restart, upgrade, restore from a snapshot.
The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.
Inventory of instances, versions, modules and clients; compatibility check; final price.
Full switch rehearsed on a non-production copy.
Production switched in an agreed window; rollback kept ready; runbook delivered.
Fixed price after the check in step 1. Paid on completion.
Redis 8 can be used under AGPLv3, an open-source licence with copyleft terms. Some teams are fine with that; others prefer Valkey's permissive BSD licence. We explain the practical difference — your counsel makes the call.
Usually no. Valkey keeps the Redis protocol, so existing client libraries connect as before.
With replication in place, clients reconnect within seconds when the new primary takes over.
We check each module you use. Where Valkey has an equivalent we test it; where it has none, we tell you before you decide.
Version, topology and number of instances — we give you a price on the call.