Kemory vs Zep / Graphiti

Context graphs for enterprise agents.
A shared memory for people across AIs.

Zep calls itself the enterprise context layer for reliable agents: Context Lake turns business data into governed context graphs, built on Graphiti, its open-source temporal graph framework. Kemory overlaps on agent memory over MCP, but it starts from the conversations people have with AIs, and from sharing them safely.

Last verified 7 November 2026 against primary sources

The verdict

Two good answers.
Different jobs.

Choose Zep / Graphiti if…
  • You are building enterprise agents that need governed, graph-structured context over business data.
  • Temporal reasoning (what was true, and when) and provenance back to source data are central to your application.
  • You want an open-source temporal knowledge-graph framework on your own graph database.
Choose Kemory if…
  • You want your own and your team’s chats in six AIs captured automatically, then recalled or continued in another AI.
  • You need to share memory with people across organisations, with accept-to-receive, revocation and audited reads.
  • You want published plan prices that start free, with governance on every plan.
Ideal for

See each one
doing its job.

Public homepage, captured 7 November 2026.
Zep / Graphiti is ideal for
Enterprise agents reasoning over business data.
Temporal graphSource provenanceFramework integrations
Kemory Kemories view: memories and chats from every AI in one place, filtered by AI.
Kemory is ideal for
People and teams carrying memory across AIs.
Automatic chat captureContinue in another AIAudited sharing

Screenshots taken 7 November 2026. Zep / Graphiti is a trademark of its owner, shown here to identify the product.

At a glance

The same rows on every comparison, so you can read one page against another.

Feature
This siteKora + Kemory
Zep / Graphiti
Capture
Kora, an AI chief of staff, included
Yes
—
Pulls in your AI chats automatically
Yes(6 AIs)
—
Keeps whole chats and distilled memories
Yes
Graph facts
Keeps chat artefacts — files, code, images
Yes
—
Use
Native in Claude and ChatGPT (MCP connector)
Yes
Manual
Protocols
MCP · REST · CLI · SDK
MCP · SDK
Ask across everything, with sources
Yes
—
Continue a chat in another AI
Yes
—
Counsel — many models, one answer
Yes
—
WhatsApp
Yes(Coming Soon)
—
Builds a model of you
Yes
—
Share & govern
Two-way memory sharing between people
Yes(across orgs)
—
Fine-grained memory permissions
Yes
—
Audit trail and provenance
Yes
Episode sources
Shows contradictions, lets you resolve them
Yes
Partial
Privacy & trust
Private by default — private tags, secrets stripped
Yes
—
Delete and prove it's gone
Yes(crypto-shred)
—
Data residency on every plan
Yes(India · Switzerland)
—
Measured token savings
Yes
—
Version history and restore
Yes
—
Openness
You hold the keys (community edition only)
Yes
Graphiti only
Integrated with SeKondBrain's Cognition Layer
Yes(Coming Soon)
—
Open-source
Yes(community)
Graphiti (Apache)
Proof & price
Published benchmark
89.6% LongMemEval-S*
Jan 2025 paper; not re-verified
Pricing shape
Free to start
Paid; no free tier to speak of

*89.6% end-to-end answer accuracy on LongMemEval-S, open-weight Llama-3.3-70B reader, six runs. See the benchmarks or the full method on docs.sekondbrain.ai. A dash means not documented, not proven absent.

Where they differ

The same job,
done two ways.

Starting point
Zep / GraphitiBusiness data and agent messages, sent through the SDK
KemoryPeople’s AI chats, captured automatically from six AIs
Memory model
Zep / GraphitiTemporal context graph: episodes, entities and relationships over time
KemoryRaw memories, namespace summaries and one synthesised context
Self-hosting
Zep / GraphitiGraphiti on your own Neo4j, FalkorDB or Neptune; Zep CE removed
KemoryEnterprise self-host, own cloud, air-gap; Community Edition coming
Where Zep / Graphiti is ahead
Credit where it’s due.

Graphiti tracks what was true and when, and links every fact back to its source episode, a strong fit for questions about change over time. Context Lake brings structured and unstructured business data into one graph, and Zep integrates with a wide range of agent frameworks, from Google ADK and LangGraph to the Vercel AI SDK.

Benchmarks

The numbers,
and how each was run.

These rows use different datasets, splits, readers and retrieval budgets, so they cannot be compared directly. We publish the method, every run including the lower ones, and use an open-weight reader rather than a frontier model.

ProductBenchmarkScoreWhat it measuresSetupReader modelRuns
KemoryLongMemEval‑S89.6%End-to-end answer accuracy500 questions, oracle splitLlama-3.3-70B (open-weight)Six, with variance
Zep / GraphitiDMR, LongMemEval (Zep paper, Jan 2025)Not verifiedSelf-reportedNot verifiedNot verifiedNot verified
Read the Kemory benchmark on docs.sekondbrain.aiZep / Graphiti’s published figuresOther products’ figures are their own, self-reported, and not re-run by us.

What changed at Zep / Graphiti

Products move quickly. These are the dated changes this comparison has been checked against.

  1. 14 October 2026Zep’s integration notes describe it as “a paid product (no meaningful free tier)”.
  2. 20 October 2026Graphiti 0.31.2 released.
  3. 2 November 2026zep-cloud SDK 4.1.0 released.
  4. 4 November 2026getzep/zep rewritten around Context Lake and Agent Skills; legacy Community Edition code removed.
The bigger picture

Specialists do one job well.
Kemory holds the thread across them all.

Every year brings better models and you will keep trying them. Kemory sits above the models rather than inside any one of them, so what you have worked out goes with you.

01
One memory every AI shares.

Tell one AI something once, and every AI you use just knows it. Start a thought in one and carry on in another, mid-sentence.

02
Permissioned, auditable AI memory.

Every memory is permissioned and every change is provable. We do not train on your data. Delete anything, and prove it is gone.

03
Save tokens and time.

Compaction runs on an open-weight model, so the frontier model only ever sees the compacted version — not the pile.

Already using Zep / Graphiti? You do not have to replace it to try Kemory. Kemory connects to the AIs you use over MCP and Kora for Chrome.

Your call

Choosing Zep / Graphiti instead?
Good — it fits you better right now.

Come back to Kemory when cross-AI, governed memory is what you need.

Questions

Five questions,
Kemory vs Zep / Graphiti.

What is the difference between Kemory and Zep?
Zep is an enterprise context layer. It turns business data into governed context graphs for agents, using Graphiti’s temporal graph. Kemory is a cross-AI memory for people and teams. It captures chats from the major AIs, recalls them over MCP, and governs sharing with consent and audit.
Do Kemory and Zep support MCP?
Yes. Zep says agents connect through MCP or its Python, TypeScript and Go SDKs, and Graphiti ships its own MCP server. Kemory offers a one-click connector in Claude, ChatGPT and four more AIs, and MCP recall in about twenty more clients.
How are Zep and Kemory priced?
Zep’s own integration notes describe it as a paid product with no meaningful free tier; we could not verify plan prices on 7 November 2026. Kemory is free for 2,000 memories and two AIs, with Pro at $19.99 a month, Team at $30 a seat and Business at $55 a seat (10-seat minimum).
Can I still self-host Zep?
The legacy Zep Community Edition code was removed from the getzep/zep repository on 4 November 2026. Graphiti, the open-source framework under Zep, is still Apache 2.0 and runs on your own Neo4j, FalkorDB or Amazon Neptune.
Are Zep’s benchmark results comparable with Kemory’s?
Not directly. Zep’s January 2025 paper reports DMR and LongMemEval results, and we have not re-verified their split or reader model. Kemory reports 89.6% end-to-end answer accuracy on the LongMemEval-S oracle split with an open-weight Llama-3.3-70B reader, across six runs. Different splits, readers and retrieval budgets give different numbers.

More comparisons

Credit where it’s due. The real difference, either way.

Memory platformsvs NessieA searchable record of your AI work. A governed memory that travels between AIs.Memory platformsvs MemoryPluginOne person’s memory across 21+ AI tools. A governed memory you can share and audit.Memory platformsvs AI Context FlowContext you save once and carry into any AI. Memory that fills itself, with audited sharing.Memory platformsvs MaximemTwo products: Vity for people, Synap for agents. One governed memory for both, shared with audit.Memory platformsvs SupermemoryA fast memory API. A governed memory across your AIs.Memory platformsvs Living BrainA readable wiki. A memory that travels.Memory platformsvs Mem0A quick start. A shared memory with permissions.Memory platformsvs HonchoA model of the conversation. A governed memory across contexts.Assistantsvs ChatGPT and Claude memoryMemory built into your assistant. Or memory across your assistants.Personal memoryvs PiecesYour working day, on your machine. Your AI conversations, shared under rules.Personal memoryvs MinimiAmbient recall on your Mac. Or conversations you can carry forward.Memory platformsvs MemPalaceVerbatim recall on your own machine. Governed memory across AIs and people.Frameworksvs CogneeA knowledge graph your agents can search. A governed memory across AIs and people.Frameworksvs Basic MemoryA Markdown knowledge base you and your AI write. A memory that fills itself from your chats.Frameworksvs EverOSAn open memory runtime for agents. A governed memory for people, teams and agents.Viewing nowvs Zep / GraphitiContext graphs for enterprise agents. A shared memory for people across AIs.Frameworksvs AWS AgentCore MemoryManaged memory for agents you run on AWS. A cross-AI memory people and agents share.Frameworksvs Google Memory BankManaged memory for agents on Google Cloud. A cross-AI memory people and agents share.
Cite this comparisonKemory vs Zep / Graphiti. SeKondBrain. Last verified 7 November 2026. https://sekondbrain.ai/products/kemory/compare/zep