Does Zep decide what each end user can see?
No. Your application authorizes each customer and chooses which graphs to retrieve from. Zep applies policies to the agents that read shared graphs.
Customer context
Build agents that
know each customer
Give the agents in your product current, unified context on each customer and account.
User and account context in one answer
Combine conversations and records
The agent gets the user's past conversations and the account's records together.
Stay current as accounts change
When an invoice or a plan changes, Zep marks the old fact invalid and keeps its dates.
Keep users and accounts apart
Each user's context is in their own graph. Shared records go in the account's graph.
Your application sends conversations and account records through the Zep SDKs.
SDKs
Keep each customer's context separate
Zep separates customers by graph and applies data access policies at the infrastructure level.
Isolation
Isolate each customer
Each user and each account gets a graph of its own.
Access control
Control account access
Policies decide which agents can search each account graph.
Extracted facts
Prefers email replieskept
Plan: Team, 50 seatskept
Diagnosed with asthmahealthdropped
Keep prohibited content out
Content policies drop facts you prohibit, such as health details, before Zep adds them to the graph.
Context Lake
Turn customer data into unified context
Zep ingests data from across your business, builds a context graph for each user, customer, account, or domain, and retrieves the context each task needs.
1 Ingest
Send data from across your business
Each record keeps a link to its source.
Business data
Documents
Conversations
2 Build
Build a context graph for each user, account, or domain
Facts are dated and updated as your data changes.
3 Retrieve
Retrieve the context each task depends on
Filtered by policy and returned in one call.
Policy filter
Account: Acme
Renewal: October 31
SSO setup is blocked.
Confirm SSO setup
before renewal.Recognition
Context infrastructure for the enterprise
“We can easily see Zep becoming a de facto partner in this layer of the enterprise agent stack.”
Research
We wrote the paper on context graphs
January 2025 · arXiv 2501.13956Runs in Graphiti and Zep
FAQ
Questions about customer context
Can we delete a customer's data?
Yes. Deleting a user removes their graph along with their threads and messages.
Do we keep our agent framework?
Yes. Your code calls Zep through its SDKs, so the framework and tools stay the same.
How is this different from agent memory?
Agent memory keeps one user's conversations and preferences. Customer context adds an account graph for the records that a customer's users share.
Give agents customer context
Start with one customer-facing workflow. We'll help map its data to user and account graphs.