Memory

The memory store keeps AI Gateway state, the MCP listing cache and OAuth guard session state, in local process memory. It has no external dependency to run, but it does not persist across restarts and is not shared between Zilla instances.

Configuration

stores:
  cache:
    type: memory

When to Use It

Use the memory store for single-node deployments, local development, and testing, anywhere a restart clearing the listing cache or auth state is acceptable. The Listing Cache page uses it as the default store for caching tools/list, prompts/list, and resources/list responses.

For a multi-node or production deployment where the listing cache or auth state must stay consistent across replicas, use Redis or Hazelcast instead.

See the memory store reference for the full configuration reference.