Skip to content

Valkey

Valkey is Watasu’s managed in-memory data service. It speaks the Redis protocol, so any Redis client library works against it without changes.

Use Valkey for fast, ephemeral state. Use PostgreSQL when the data must be your long-term system of record.

  • caching computed values or query results
  • session storage
  • rate limiting and throttling
  • ephemeral coordination (locks, leader election with TTL)
  • queue acceleration
Terminal window
watasu addons:create valkey --app my-app

Pass a plan to pick a tier:

Terminal window
watasu addons:create valkey:premium-0 --app my-app

hobby-0 is a non-persistent 25 MiB cache at €1/month. The active Premium plans range from premium-0 (50 MiB, €5/month) to premium-14 (100 GiB, €1,100/month). Every Premium plan includes AOF persistence, one managed HA standby, and automatic failover. The plan numbers are not consecutive; use the catalog table to select a supported size.

Storage backend: Valkey uses network-attached storage for persistence. Premium adds a managed standby and automatic failover. It does not promise three data replicas or local NVMe.

See Add-on Plans for the full catalog.

After attachment, your app gets:

VariablePurpose
REDIS_URLRedis-protocol connection URL

The variable name keeps the Redis prefix on purpose so existing libraries and frameworks “just work.”

Terminal window
watasu valkey:cli --app my-app

The legacy redis:cli alias still works for muscle memory.

Premium plans support manual and scheduled backups. Hobby 0 is non-persistent and has no backup contract.

Terminal window
watasu addons:backups:capture my-cache
Terminal window
watasu addons:backups my-cache

Restores create a replacement add-on, then you promote it. Restore from a managed backup or from a local .rdb file:

Terminal window
watasu addons:restore my-cache ./backup.rdb --name my-cache-restored
watasu addons:promote my-cache-restored

For the full restore workflow, see Backups and Restores.

  • Treat Valkey contents as expendable unless you’ve explicitly chosen a persistent plan with backups.
  • Set TTLs on everything you can — unbounded keyspaces are how Valkey instances run out of memory at the worst possible moment.
  • For pub/sub or fan-out patterns at scale, Redpanda is a better fit.