Mem0, Zep and Letta alternatives
A disclosure first: we build one of the tools named below. Every claim about the three building blocks is dated and links to their public repository, and two times out of three this page will tell you to pick something other than us.
"Mem0 alternatives", "Zep alternative", "Letta alternative": the query is the same, the situation behind it almost never is. Before listing names, sort the reasons. There are three, and they do not lead to the same place.
The three reasons to look for an alternative
| Your reason | The right category | The short answer |
|---|---|---|
| You want another building block, with different technical trade-offs | Developer building block | The three are each other's alternatives, see below for who wins on what |
| You wanted to self-host Zep and that path is closing | Open source building block | Mem0 or Letta, both Apache 2.0 and self-hostable |
| You discovered that a building block demands months of work around it | Finished product | Change category, that is where we are |
The rest of the page unfolds those three rows, in order.
Reason 1: you are staying in the building block category
If somebody at your company writes code and memory is the core of your product, the right alternative to one of these blocks is one of the other two. Here are the real trade-offs, recorded on 4 August 2026 from their public repositories.
Mem0 wins on ease of starting. A pip or npm library under Apache 2.0, self-hostable with docker compose (Mem0 repository, checked 04/08/2026). It is the shortest path between "I want memory in my agent" and "it runs".
Zep wins on the temporal model, and that should be said plainly. Graphiti, which powers it, gives every fact a validity window, automatically invalidates contradicted facts without deleting them, keeps the full history, and lets you query the state of knowledge at any date (Graphiti, checked 04/08/2026). On that specific point it is the best block on this list, and no alternative does better, ourselves included among the blocks.
Letta wins on independence. A local or self-hosted server, model-agnostic, under Apache 2.0, driven from the command line or through its SDK (Letta repository, checked 04/08/2026). If you want to switch model providers without switching memories, that is the argument.
The detailed comparison of the three, with Verbasil, lays out the full table line by line.
Reason 2: you are looking because of self-hosting
This is the most common reason behind "Zep alternative" in particular: Zep's community edition is deprecated in favour of the managed offering (Zep repository, checked 04/08/2026). If your requirement is to read the code, modify it and host it yourself, that path is closing.
The answer fits in one sentence: Mem0 and Letta are both under Apache 2.0 and self-hostable, the former via docker compose, the latter as a local or self-hosted server. Between the two, the trade-off is the one from reason 1: ease of starting versus model independence.
And an honest warning: we are not the alternative for this reason. Verbasil is neither open source nor self-hostable. If that is your requirement, take Mem0 or Letta, sincerely.
Reason 3: you discovered the real cost of a building block
This is the reason nobody types into a search bar, and the most widespread one outside developer teams. It looks like this: you installed a block, it works, and you understood that for it to become your company's memory, there is still the ingestion from your emails and meetings to write, an interface to build, a definition of what a decision means at your company, the logic that surfaces what matters, permissions, and maintenance. These blocks are excellent engines. You are missing the car around them.
If that is your case, none of the three is the alternative to the other two: swapping engines does not build the car. The alternative is a change of category, towards a finished product.
That is Verbasil's category. A finished product for a founder or a small team, with no code to write and nothing to configure before it is useful. It dates the validity of decisions, ties them to their evidence, detects recurrences nobody configured, and delivers a daily brief of what deserves attention. An MCP server connects ChatGPT, Claude, Cursor or Gemini to the memory, which the building blocks leave you to integrate yourself.
And the difference no table shows: a building block serves memory to an agent at the moment it answers. A memory product returns it to a human first. Mem0, Zep and Letta do the first job very well. Nobody gets a morning brief from a library, because a library has nobody to warn.
What we do not do, so the choice stays clean: no open source, no self-hosting, no control over the engine. In exchange, portability is unreserved: full export from day one of the trial, and the MCP server lets several AI tools read the same memory without any of them owning it. Whatever happens to us, you leave with everything.
How to verify instead of believing
This page is still a text written by an interested party. Three checks that take an afternoon:
- If you are choosing between blocks, stand up Mem0 and Letta with the same test data, and measure the time between installation and the first useful answer inside your agent.
- If you are choosing between block and product, count what remains to be built after installing the block, item by item, and put a number of weeks in front of each.
- If you are testing a memory product, ours or another, feed it two weeks of real material then ask nothing, and watch what it surfaces on its own. The eight selection criteria detail each of these tests.
Book a memory audit: free, 30 minutes, we look together at what you have already forgotten, whether you are one person or fifteen.
FAQ
What is the best Mem0 alternative?
It depends on why you are looking. For another developer block: Zep if the temporal model is your priority, Letta if it is independence from the model provider. If the reason is that nobody at your company will write the ingestion, the interface and the retrieval around the block, the alternative is not another library but a finished company memory product, such as Verbasil.
What is a self-hosted alternative to Zep?
Mem0 or Letta. Zep's community edition is deprecated in favour of the managed offering, while Mem0 self-hosts via docker compose and Letta runs as a local or self-hosted server, both under Apache 2.0. Verbasil is not an answer to this requirement: the product is neither open source nor self-hostable.
Is there an alternative to these blocks without writing code?
Yes, but it is a different category: company memory products, usable without a developer. The fundamental difference is that a block serves an agent that answers, while a product returns the memory to a human, with dated decisions, their evidence, and the surfacing of what nobody asked for. Verbasil is in that category; the full landscape is in the best company memory tools.
Are Mem0, Zep and Letta competitors of Verbasil?
Rarely in practice. They are building blocks that developers assemble into their own product, while Verbasil is a finished product for a team that will assemble nothing. The only real overlap is the memory engine itself, and on the temporal model Zep is excellent. The question that decides is not engine sophistication, it is who does the work around it.
How do you migrate from a memory building block to a finished product?
Do not try to transfer the accumulated memory: it is structured for an agent, not for a team to read. Start again from your real sources, emails, meetings, chat threads, and give the product two weeks of material. That is also the best purchase test: what it surfaces on its own after two weeks tells you whether it is worth its price.