Is Zep SOC 2 Type II certified?

Yes. Zep is SOC 2 Type II certified. Review controls and live compliance status on the Trust Center (https://trust.getzep.com).

Can Zep sign a HIPAA BAA?

Yes. HIPAA BAAs are available with the Enterprise plan.

We're an EU company. Will you sign a DPA?

Yes. Zep signs Data Processing Agreements with EU customers and customers with EU presence.

Zep AI MemoryLong-term memory layer for AI agents and LLM apps

4.8 (4)

Reviewed by Daniel Nikulshyn·Updated July 2026

Developer Tools API Memory Knowledge Graph LLM Infrastructure SDK Semantic Search

Overview

Zep AI Memory is a developer-focused memory service that gives AI agents persistent, structured recall across conversations and sessions. It captures chat history, extracts key facts, and organizes them into a knowledge graph so agents can retrieve relevant context on demand instead of stuffing entire histories into prompts. The platform handles summarization, entity extraction, and semantic search behind a simple API, letting teams add stateful memory to chatbots, copilots, and autonomous agents without building custom retrieval infrastructure. It is designed to scale with production workloads while keeping prompt sizes and token costs predictable. Zep integrates with common LLM frameworks like LangChain and LlamaIndex and provides SDKs for popular languages, making it straightforward to drop into existing agent stacks.

Key features

Long-term conversational memory
Automatic fact and entity extraction
Knowledge graph storage
Semantic and hybrid search
LangChain and LlamaIndex integrations
Multi-language SDKs

Pricing

Model: Freemium
Category: Agent Development
Rating: 4.8 / 5 (4)

Use cases

Persistent memory for customer support chatbots

Give support bots recall of past tickets, preferences, and entities across sessions so users don't need to repeat context, improving resolution quality and continuity.

Stateful copilots with reduced token costs

Replace full chat-history prompt stuffing with targeted semantic retrieval from Zep, keeping prompts small and predictable while preserving relevant long-term context.

Autonomous agents with structured recall

Power multi-step agents using Zep's knowledge graph to remember facts, entities, and relationships gathered across runs, enabling more coherent long-horizon task execution.

LangChain or LlamaIndex memory backend

Drop Zep into existing LLM framework pipelines as the memory layer, adding fact extraction and hybrid search without building custom retrieval infrastructure.

Pros & Cons

Pros

Persistent memory across sessions
Reduces prompt size and token costs
Knowledge graph for structured recall
Works with major LLM frameworks
Developer-friendly SDKs and API

Cons

Requires engineering integration work
Geared toward developers, not end users
Adds another service to the stack

Battle record

Across 3 battles in the Pantheon.

1st

2nd

3rd

Last 3 battles

Reviews

4.8

Average from 4 ratings.

Kwame Mensah

Apr 10, 2026

Does the job

Pretty happy overall. Automatic fact and entity extraction just works and persistent memory across sessions. Geared toward developers, not end users can be annoying, but no dealbreakers — I'd recommend it to a friend without hesitating.

Esther Adeyemi

Jan 15, 2026

Skeptical, then convinced

I went in skeptical — most tools in this space overpromise. It actually delivers on knowledge graph storage, and reduces prompt size and token costs caught me off guard. still, I'd recommend giving it a real trial.

Ingrid Bauer

Aug 27, 2025

Compared a few options

Evaluated this against two competitors. Where it wins: langChain and LlamaIndex integrations and persistent memory across sessions. On balance the feature set — especially multi-language SDKs — justifies the 5 stars for our use case.

Marcus Bell

Aug 4, 2025

Does the job

Pretty happy overall. LangChain and LlamaIndex integrations just works and knowledge graph for structured recall. Requires engineering integration work can be annoying, but no dealbreakers — I'd recommend it to a friend without hesitating.

Q&A

How credits work

Credits are consumed based on the size of each Episode you send to Zep. Episodes up to 350 bytes use 1 credit; each additional 350 bytes (or part thereof) uses another credit. Where available, webhook invocations consume 1/8 of a credit each. Flex and Flex Plus automatically top up your credits when your balance drops below 20%. Flex adds 10,000 credits ($25); Flex Plus adds 40,000 credits ($75). Flex credits roll over for 30 days; Flex Plus credits roll over for 60 days. Free plan credits do not roll over.

Asked by Yuki Mori · Mar 1, 2026

Are we charged for ingestion or storage?

You are charged for ingestion and processing of Episodes. You are not charged for storage of messages or data.

Asked by Nour Khalil · Feb 17, 2026

What is an Episode?

An Episode is any single data object you send to Zep — a chat message, JSON payload, or block of text. Credit cost scales with Episode size. Episodes up to 350 bytes use 1 credit; each additional 350 bytes (or part thereof) uses another credit. A 640-byte Episode uses 2 credits; a 1,200-byte Episode uses 4 credits.

Asked by Sarai Cohen · Feb 18, 2026

How are rate limits calculated?

Each plan tier has a base rate limit, with Free being the lowest. Free and Flex Plan customers may see rate limits lowered depending on service usage. Enterprise plans have committed, guaranteed rate limits.

Asked by Xander de Vries · Jan 30, 2026

What are the Free plan limits?

10,000 credits per month. No rollover or auto-topup. ·2 projects, 5 custom entity & edge types. ·Variable rate limits, depending on service-wide load. ·Lower priority Episode processing. ·Feature availability and service levels may change over time.

Asked by Fiorella Bianchi · Jan 21, 2026