Redis Stack

Redis Stack extends Redis with JSON document storage (RedisJSON), full-text and vector search (RediSearch), time-series data (RedisTimeSeries), and probabilistic data structures. Builds on Redis's in-memory key-value store with sub-millisecond latency. Accessible via the Redis protocol (RESP) using standard Redis clients, plus a REST API via Redis Stack Server. Available as Redis OSS + Stack modules, or Redis Cloud.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Other redis redis-stack redisjson redisearch vector-search cache pub-sub open-source in-memory
⚙ Agent Friendliness
79
/ 100
Can an agent use this?
🔒 Security
82
/ 100
Is it safe for agents?
⚡ Reliability
84
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
75
Documentation
88
Error Messages
72
Auth Simplicity
82
Rate Limits
78

🔒 Security

TLS Enforcement
92
Auth Strength
80
Scope Granularity
72
Dep. Hygiene
88
Secret Handling
80

Redis ACL for command-level and key-space access control. TLS optional but recommended. Redis Stack adds JSON, Search, Graph modules. ACL users can restrict agents to specific key patterns and command subsets.

⚡ Reliability

Uptime/SLA
85
Version Stability
85
Breaking Changes
82
Error Recovery
85
AF Security Reliability

Best When

An agent needs ultra-low latency caching, session state, real-time pub/sub, or vector search with JSON document capability, and data volumes fit within available memory.

Avoid When

Your dataset exceeds available RAM, you need persistent ACID transactions across complex relational data, or you require long-term durable storage as the primary database.

Use Cases

  • Agent session state and context caching with automatic TTL expiration
  • Vector similarity search for agent RAG and semantic memory via RediSearch
  • Real-time pub/sub messaging between agent components
  • JSON document storage for agent-generated structured data with querying
  • Rate limiting, distributed locking, and leaderboards in multi-agent systems

Not For

  • Primary persistent database (Redis is in-memory first; persistence requires configuration)
  • Large dataset storage exceeding available RAM (all data must fit in memory by default)
  • Complex SQL joins or relational queries
  • Long-term analytics over large historical datasets

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
No

Authentication

Methods: password acl tls_cert
OAuth: No Scopes: Yes

Redis 6+ ACL system provides user-level access control with command-level and key-pattern permissions — excellent for least-privilege agent access. Authentication via AUTH command or connection string password. Redis Cloud uses username/password. TLS available and recommended for production. Default Redis has no auth — must be configured explicitly. ACL rules can restrict agents to specific key namespaces and command subsets.

Pricing

Model: open-source-plus-hosted
Free tier: Yes
Requires CC: No

Redis OSS is BSD licensed and free. Redis Stack modules (RedisJSON, RediSearch, etc.) are available under RSAL license (non-permissive for competing products). Redis Cloud free tier (30MB) is very limited but sufficient for agent prototyping. Upstash offers serverless Redis with per-request pricing and a generous free tier — often better for agents.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Documented

Known Gotchas

  • Default Redis has no persistence — data is lost on restart unless RDB snapshots or AOF is configured
  • Redis Stack modules (RedisJSON, RediSearch) use RSAL license — not suitable for products that compete with Redis
  • WRONGTYPE errors occur silently if an agent uses the wrong data structure command for a key — always check key types
  • Redis 30MB Cloud free tier is quickly exhausted by vector embeddings — each 1536-dim float32 vector is ~6KB
  • RediSearch vector index must be created before data is loaded — cannot add index retroactively without reindexing
  • TTL is per-key and not inherited — agents setting TTLs on parent hashes must also set TTLs on nested structures manually
  • Pub/Sub messages are not persisted — if an agent subscriber is offline, messages are lost; use Streams for durability
  • The mcp-redis MCP server is newer and less battle-tested than Redis itself — evaluate for production use carefully

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Redis Stack.

$99

Scores are editorial opinions as of 2026-03-06.

5173
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered