Zep Cloud
Manages long-term memory for AI agents using a temporal knowledge graph that stores conversations, extracts facts, and indexes them with time-awareness so agents can recall what was true at any point in time.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
All data encrypted at rest and in transit; project-scoped API keys; no per-session key scoping available.
⚡ Reliability
Best When
You need temporally-aware memory where the sequence and timing of facts matters, such as tracking evolving user beliefs or commitments across many sessions.
Avoid When
Your agent is stateless per request or memory requirements are simple key-value lookups without temporal or graph relationships.
Use Cases
- • Build a personal assistant agent that recalls user preferences, past decisions, and evolving facts over months of interaction
- • Power a sales assistant with persistent CRM-style memory of every prospect conversation and extracted commitment
- • Enable a medical information agent to track patient-reported symptoms over time with temporal context
- • Implement dialog state tracking for multi-session customer service bots that remember issue history
- • Feed a research agent structured facts extracted from prior sessions to avoid re-discovering known information
Not For
- • Single-session stateless request/response agents that do not require cross-session persistence
- • Bulk document indexing pipelines — use a purpose-built vector store instead
- • Agents requiring sub-10ms memory retrieval at very high throughput
Interface
Authentication
API key passed as Authorization Bearer header; project-level keys scope access to all sessions within a project.
Pricing
Open-source Community Edition (CE) available for self-hosting. Cloud adds managed infrastructure, temporal graph, and enterprise support.
Agent Metadata
Known Gotchas
- ⚠ Fact extraction runs asynchronously after message ingestion — do not assume facts are immediately queryable after adding messages
- ⚠ Session IDs must be consistent across the lifetime of a user conversation or history fragments into disconnected sessions
- ⚠ The temporal graph is a Cloud-only feature; OSS CE uses simpler vector search without temporal indexing
- ⚠ Large conversation histories trigger background summarization that may alter what raw messages are returned
- ⚠ Graph traversal for complex relational queries is not exposed in the public API — only semantic search over extracted facts
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Zep Cloud.
Scores are editorial opinions as of 2026-03-06.