Self-managed Redis Agent Memory

Deploy, configure, secure, and operate Redis Agent Memory on a self-managed Kubernetes cluster.

Redis Iris

Redis Agent Memory provides persistent memory for AI agents and applications. Applications write conversation events and long-term memories to Redis Agent Memory, then query Redis Agent Memory for relevant context before calling an LLM.

This guide covers deployment, configuration, security, validation, API examples, and operations for self-managed Redis Agent Memory.

The Redis Agent Memory API is the shared Data Plane API for Redis Cloud and self-managed deployments. The Control Plane API reference documents the self-managed admin endpoints for stores and agent keys.

Note:
Self-managed Redis Agent Memory is available as a private preview. You need a license key to deploy it. Contact your Redis representative or contact sales.

What you are deploying

A standard self-managed Redis Agent Memory deployment contains:

Component Purpose Default service
Redis Agent Memory Data Plane Store-scoped runtime memory API. redis-agent-memory:9000
Redis Agent Memory worker Background promotion, summarization, and forgetting work. No public service
Redis Agent Memory Control Plane Optional admin API for creating stores and managing agent keys. redis-agent-memory-controlplane:9100
Store Redis Holds session memory, long-term memory, indexes, and TTL data. Customer-provided
Job Redis Holds background work for Redis Agent Memory workers. Customer-provided
Metadata Redis Holds Control Plane store records and agent-key records. Required for Control Plane managed stores and agent keys

How the components work together

The Data Plane handles runtime memory requests. The optional Control Plane handles store and agent-key administration.

Flow Caller Service Backing Redis
Store and key administration Platform admin Redis Agent Memory Control Plane Metadata Redis
Runtime memory requests Agent, app, or gateway Redis Agent Memory Data Plane Store Redis
Background memory processing Redis Agent Memory worker Redis Agent Memory Data Plane Job Redis and Store Redis
  1. Platform admins use the Control Plane to create stores and agent keys.
  2. The Control Plane stores store records and agent-key grants in Metadata Redis.
  3. Agents and applications call the Data Plane with a store ID.
  4. The Data Plane enforces the configured auth mode and reads or writes memory in Store Redis.
  5. Workers use Job Redis for background work and write generated memory to Store Redis.

API surfaces

All Data Plane APIs are scoped to a store. A store is the logical isolation boundary for memory data.

When agent-key authentication is enabled, grants stored in Metadata Redis determine which stores and actions each key can access.

API surface Endpoint prefix Purpose
Session memory /v1/stores/{storeId}/session-memory Ordered conversation events, session metadata, and session lifecycle operations.
Long-term memory /v1/stores/{storeId}/long-term-memory Searchable facts, preferences, summaries, and custom memory records.
Control Plane /v1/stores, /v1/api-keys Self-managed administration for stores and agent keys.

Session memory keeps conversation continuity within a session. Long-term memory provides searchable context across sessions.

Long-term memory memoryType is an open identifier. When omitted on create, Redis Agent Memory stores the record as semantic; built-in names include semantic, episodic, message, and session_summary_view.

Deployment modes

Start with Plan a deployment to choose between static stores and Control Plane managed stores.

If you need to Go to
Review software, Redis, network, Secret, image, and sizing requirements Prerequisites
Prepare memory-dataplane.config.yaml for either deployment mode Data Plane configuration
Deploy a first-install or single-store setup without the Control Plane Deploy with static stores
Deploy runtime store and agent-key administration Deploy with Control Plane managed stores

Do not combine static metadata.stores with Control Plane managed store metadata in the same Data Plane config. Static stores do not use Metadata Redis. Control Plane managed stores use metadata.source: live and require Metadata Redis.

Warning:
Do not expose an auth-disabled Data Plane to untrusted callers. In auth-disabled mode, Redis Agent Memory does not authenticate or authorize Data Plane requests; any caller that can reach the API can read or write memory for configured stores. Use that mode only when Kubernetes NetworkPolicy, private service exposure, ingress/gateway policy, service mesh, or equivalent controls restrict access to trusted components.
RATE THIS PAGE
Back to top ↑