More than strings
Lists, sets, hashes and sorted sets support queues, rankings and structured cached values.
Read the official guideAll database engines
Managed Valkey
Managed ValkeyKeep frequently needed data within quick reach.
Use Valkey for application caches, sessions and counters. Familiar Redis-compatible clients work with a rich set of data structures, rather than treating every value as a document in a table.
Valkey / a familiar starting pointSET session:42 active EX 1800
GET session:42
INCR requests:customer:42
EXPIRE requests:customer:42 60Working with Valkey
Choose it for the work
it does well.
Expiry as part of the design
Give temporary data a lifetime and plan eviction behavior around the memory your workload needs.
Read the official guidePersistence with clear limits
Understand snapshots and append-only logs before deciding which data can live only in a cache.
Read the official guideWhere it fits.
Sessions, caches, rate limiting and workloads that benefit from fast key lookups.
Before you choose
Active data must fit in memory. Extra disk storage helps persistence and recovery, not RAM capacity. Replication is asynchronous, so failover can lose recent writes.
Your database.
The server work, covered.
The workspace brings connections, access and recovery together. Your application keeps its standard database client.
Connect with confidence
Find your endpoint, port, credentials and certificate together, with examples for standard clients.
Control who gets in
Set allowed IPs and give applications separate users. Review permissions before opening access.
Keep recovery separate
Full backups and recovery logs are stored off-server. Your workspace shows completed coverage.
Give Valkey its own workspace.
Choose a published node type, region and storage. Review your monthly total before checkout.