Zep vs Memlo: which memory to use

Last updated October 31, 2026

Zep is a hosted context platform for teams building AI agents: it organizes users, conversations, business data and documents into temporal "Context Graphs," built on its open-source Graphiti framework, and agents reach it through Python, TypeScript and Go SDKs or an MCP server. Memlo is a hosted memory server for the agents you already use: Claude Code, Codex, claude.ai, ChatGPT and other MCP apps share memories that agents save on purpose, each with its own version history. Pick Zep to give an agent product memory of its users and your company's data. Pick Memlo to give your own agents and your team one shared memory.

At a glance

Facts about Zep come from its own site, pricing page and documentation, read on October 31, 2026. Links are in Sources at the end.

How Zep works

You send Zep data: chat messages for each user and thread, business data and documents. Zep calls each piece an episode and builds a temporal Context Graph from it, so it can track how facts change over time. When your agent needs context, Zep retrieves what's relevant for that user and returns it as a "Context Block" to put in the prompt. The graph engine is Graphiti, which is open source; see Graphiti vs Memlo.

Zep's pricing is credit-based: "1 credit per Episode up to 350 bytes," and "0 credits for retrieval, storage, threads, users." The Free plan includes 10,000 credits a month, Flex $125 a month with 50,000 credits, Flex Plus $375 a month with 200,000 credits, and Enterprise is custom. Zep says it is SOC 2 Type II certified.

Zep's Context MCP Server "lets an end user connect an MCP client (Claude, ChatGPT, Claude Code, Codex, Cursor…) to their own agent memory." It uses MCP seats per account: one on Free, five on Flex and fifteen on Flex Plus.

How Memlo works

Memlo is an MCP server at https://memlo.ai/mcp. You add it to each agent and sign in once. Agents get tools to save, search, read, change and retire memories.

• Curated memories. Each memory is a short note with a name and a title, saved when the agent learns something worth keeping.
• History, with authors. Every change is a version, with when it was written and by whom. Any version can be restored, and edit_memory refuses a write when someone else changed the note first.
• Spaces and sharing. Keep memories in spaces, and share a space or a page with people by email as a Viewer or an Editor.
• A wiki and a graph. Memlo keeps a page for each person, project and tool your memories mention, with every line citing its memory.

Where Zep is the better choice

• You're building an agent for many users. Zep keeps memory per user and per thread, and returns a context block your app puts in the prompt. Memlo serves your own agents, not your product's users.
• You want to bring in company data. Zep is designed to combine business data and documents with conversations.
• You want SDKs. Zep has Python, TypeScript and Go SDKs. Memlo has none.
• You need enterprise terms. Zep lists SOC 2 Type II, a HIPAA BAA, role-based access control, audit logs and bring-your-own-cloud on Enterprise.
• You want to start today. Zep has open sign-up and a free plan. Memlo is by invitation.

Where Memlo is the better choice

• You want memory for the agents you already use, with no code. Add one URL to Claude Code, Codex, claude.ai or ChatGPT and sign in.
• You want to read and correct each memory. Memories are short titled notes you can open, edit and roll back.
• You want to see which agent wrote what, and roll it back. Every version names the person and the connected app or agent, and any version can be restored.
• You want an audit trail without an enterprise plan. Memory versions and sharing changes are recorded for everyone. Zep lists audit logs on Enterprise.
• You share with people by role. Share a space or a single page by email as a Viewer or an Editor.

What Memlo doesn't do yet

• Cursor. Memlo's sign-in doesn't work from Cursor yet.
• Automatic capture. Agents save memories on purpose; nothing extracts memory from every message, as Zep does.
• An SDK or API keys. Memlo is reached over MCP with your own sign-in, while Zep has SDKs and an API.
• Business data and documents at scale. Memlo imports files and forwarded email, but it isn't built to sync company systems.
• Open sign-up. Accounts are by invitation for now; you can join the waitlist.

Frequently asked questions

Can I self-host Zep?

Not the platform: Zep's FAQ says "Zep Community Edition, which allows you to host Zep locally, is deprecated and no longer supported." Enterprise customers can run Zep in their own cloud. To run graph memory yourself, use Graphiti, Zep's open-source engine.

How much does Zep cost?

On October 31, 2026, Zep listed Free (10,000 credits a month), Flex ($125 a month with 50,000 credits, then $25 per 10,000), Flex Plus ($375 a month with 200,000 credits, then $75 per 40,000) and Enterprise (custom). One credit covers an episode of up to 350 bytes.

Does Zep have an MCP server?

Yes. Zep's Context MCP Server is at https://api.getzep.com/mcp, and end users sign in through Google Workspace or your identity provider. It uses MCP seats per account.

How is Zep different from Mem0?

Both sell memory to developers building agents. Zep builds a temporal Context Graph that also takes in business data and documents, with credit-based pricing. Mem0 extracts memories from what you add, has an open-source version you can self-host, and offers a Free and a Custom plan. See Mem0 vs Memlo.

Is there a Zep alternative for Claude Code and Codex?

Memlo is one if you want memory for your own agents rather than a platform for your product: Claude Code, Codex and chat apps connect to the same server. See also Graphiti vs Memlo and Letta vs Memlo.

Sources

Checked on October 31, 2026:

• Zep and Zep pricing
• Zep overview and FAQ
• Zep SDKs
• Zep Context MCP Server
• Role-based access control and audit logging
• Memlo: the setup page, how it works and terms