Update, September 2026: the managed Redis plans described here are retired and can no longer be purchased. New databases run on Valkey. Existing Redis databases keep running at their original price.
You can now create a Valkey database alongside the Redis plans that were already there. Valkey runs on our own infrastructure, which is why it costs a lot less:
| Dataset | Valkey | Redis |
|---|---|---|
| 250 MB | $3 | $8.80 |
| 500 MB | $5 | — |
| 1 GB | $9 | $27.50 |
Pick the engine at the top of the create flow; everything else works the way it always has.
Nothing in your code changes
Valkey is the Linux Foundation's fork of Redis 7.2, and it is compatible with
Redis at the protocol and command level. Your client library, your rediss://
connection string and your commands are identical — ioredis, redis-py,
go-redis and the rest connect to it without knowing the difference.
Every plan includes a persistent volume, so choosing a persistence mode changes how durable your data is and not what you pay.
When to stay on Redis
Redis plans keep everything they had, and there are three reasons to choose one:
- High availability. Valkey plans ship without automatic failover.
- Flex. Hot keys in memory and colder keys on SSD is a Redis family, and still the best value for a large dataset with a concentrated hot set.
- Bigger datasets. Redis plans go well past where ours currently stop.
Existing databases are untouched. Nothing migrates, nothing is repriced, and you can run one of each in the same project.
The full breakdown is in pricing.