Redis

Available in Zilla Plus

The redis store connects to a Redis instance and holds AI Gateway state, the MCP listing cache and OAuth guard session state, so every Zilla instance in a deployment sees the same data instead of keeping its own local copy.

Configuration

stores:
  cache:
    type: redis
    options:
      url: redis://redis.example.com:6379
      default-ttl: PT10S

default-ttl sets how long entries live before expiring. TLS connections to Redis are supported via the vault option.

When to Use It

Choose Redis once AI Gateway runs as more than one instance and the listing cache or OAuth guard session state needs to be consistent across all of them, for example behind a load balancer or in a horizontally scaled Kubernetes deployment. A single shared Redis instance replaces per-node caches and per-node auth state with one source of truth.

For a single-node deployment or local testing, the Memory store avoids the extra dependency. Hazelcast is an alternative distributed store when a dedicated Redis instance isn't already part of the deployment.

See the redis store reference for the full configuration reference, including TLS and vault options.