Valkey caches

Valkey is the open-source drop-in replacement for Redis we ship as managed cache. Every redis-cli command works; every Redis client library works without changes.

Provision a cache

From a project's Caches tab click + New Cache. Pick a name and a plan.

Plans are sized by memory (the dominant constraint for cache workloads). CPU comes along proportionally; disk is sized for AOF persistence (about 2× memory by default).

Connecting from your app

Same pattern as databases — link the cache from its detail page to inject a connection string. The env var is named after the cache: MY_CACHE_REDIS_URL. If only one cache is linked, we also alias it to plain REDIS_URL.

// StackExchange.Redis works as-is
var redis = ConnectionMultiplexer.Connect(
    Environment.GetEnvironmentVariable("REDIS_URL"));

Persistence

Caches default to AOF (append-only file) persistence with fsync everysec — strong enough to survive a pod restart without losing more than a second of writes. Disable persistence per-cache if your workload is purely ephemeral (sessions, computed-on-demand fragments) and you want the small write-latency win.

Connecting from outside

Same as databases: Connection tab → Reveal for a connection string. External traffic routes through the edge, so redis-cli from anywhere works.