Mem0: what it remembers, who owns it, and what it costs
thecontinuitylayer.com/memory-systems/mem0A memory layer for AI agents: an open-source library and server, plus a hosted platform, that extracts, stores and retrieves memories per user, agent and session.
- 1Yes
Is Mem0 open source?
Yes, by Mem0's own page.
The repository is licensed Apache-2.0.
Yes means: The core is under an open-source license.
- 2Yes
Can you run Mem0 yourself?
Yes, by Mem0's own page.
The open-source version is described as the same memory engine as the platform, running on your own infrastructure as a library or a Docker Compose server.
Yes means: It runs on your own machine or server.
- 3Yes
Can you take your memory out of Mem0?
Yes, by Mem0's own page.
Self-hosted memory sits in a vector database you run; the platform adds a Memory Export API that returns memories shaped to a schema you supply, filtered by user, agent or run.
Yes means: An export, or the data sits in a standard store you own.
- 4Yes
Does Mem0 work with more than one model provider?
Yes, by Mem0's own page.
The model list includes OpenAI, Anthropic, Google, Mistral, DeepSeek, xAI, AWS Bedrock, Azure, Groq, Together, Ollama, LM Studio and more.
Yes means: It is not tied to one provider's models.
- 5Yes
Is there a hosted Mem0?
Yes, by Mem0's own page.
A hosted platform with managed infrastructure and a dashboard.
Yes means: A cloud or managed option exists.
- 6Partly
Does Mem0 have a free tier, and what is the entry price?
Partly, by Mem0's own page.
A free plan with monthly limits exists; beyond it the page shows usage-based overage and a custom plan, with the older Starter, Growth and Pro plans no longer sold to new accounts. No flat paid price is published.
Yes means: A free tier exists and the entry paid price is published.
- 7Yes
Does Mem0 scope memory per user and per session?
Yes, by Mem0's own page.
Memories are scoped by user_id, agent_id, app_id and run_id, where a run is a short-lived flow, ticket or session thread; any combination works on add and as a filter.
Yes means: Both per-user and per-session or per-agent memory are supported.
- 8Yes
Can you delete a user's memories from Mem0?
Yes, by Mem0's own page.
A delete endpoint removes memories by filter (user, agent, app, run or metadata); at least one filter is required.
Yes means: A documented way to delete everything for one user.
What these grades say about continuity, and what they do not.
Every grade on this site is read from the maker's own pages. The Continuity Framework asks five things of any system that carries state: that it carry, govern, evolve, prove and forget. These tests reach carry, govern and forget; they do not reach evolve or prove, which no maker's page documents in a gradeable way. A high letter is a good memory system, not a continuity layer.
- M1 Open sourceCarry
- Open source means the memory engine can outlive the vendor; the state is not hostage to a contract.
- M2 Self-hostCarry
- Self-hosting puts the store under the owner's control, which is the precondition for every other obligation.
- M3 ExportCarry
- An export is question C3: can the state leave in a form another system reads? A standard store you own answers it; a proprietary dump only partly.
- M4 Any modelCarry
- Working with more than one model provider is question C2: the memory, not the model, holds the state.
- M7 ScopingGovern
- Scoping per user, agent and session is question G2: who may read and write each item. It is the floor of governance, not the ceiling.
- M8 DeleteForget
- A documented delete for one user is rung 5 of the erasure ladder: the record leaves the store. Derived memories, the index and backups are not covered unless the maker says so. Rung 5 of the erasure ladder: delete the record.
License as stated: Apache-2.0. Every grade above is read from Mem0's own page on the day shown. If a page has changed, tell us.