Stores

AI Gateway relies on a store for two kinds of state that need to persist across requests:

• MCP listing cache: aggregated tools/list, prompts/list, and resources/list responses, held for a configurable TTL and referenced by mcp · proxy's options.cache.store. See Listing Cache.
• OAuth guard session state: JWKS keys, nonces, and session tokens tracked while the OAuth guard enforces auth at the gateway. See Auth Enforcement.

The store type chosen determines whether this state lives in a single process or is shared across every node in a deployment:

Store	Edition	Scope
Memory	Community	Single node. Resets on restart.
Redis	Plus	Shared across instances. Persistent.
Hazelcast	Plus	Shared across instances. Distributed cluster.

Start with the in-memory store for single-node deployments and local testing. Move to Redis or Hazelcast once the listing cache or auth state has to stay consistent across multiple replicas.

See the stores top-level config key for how stores fit into the rest of the Zilla configuration.