Mem0

Open source memory layer that extracts, stores and retrieves user facts for LLM agents across sessions.

Open SourceSelf Hosted
0.0 (0)

About

Long-term memory for LLM apps is the problem Mem0 targets: after each exchange it asks an LLM to pull out facts worth keeping, embeds them, and files them under a user, session or agent, so later prompts retrieve only the relevant history instead of replaying whole transcripts. The current algorithm appends new memories rather than rewriting old ones, links named entities across records, and at query time combines vector similarity, BM25 keyword scoring and entity matches. You get a Python package (mem0ai), a TypeScript SDK, and a Docker Compose server with a dashboard and API keys for team use; the separate CLI is documented against the hosted API. It needs an LLM and an embedding model, defaulting to OpenAI but working with Ollama, Anthropic, Groq and others, plus a vector store such as Qdrant, Chroma, pgvector, Milvus or FAISS, so a fully local setup is possible. The code is Apache 2.0; the company also sells a hosted platform, and its published benchmark scores include proprietary optimizations the open version lacks. Agent builders who want recall across sessions without designing a memory schema are the audience.

Should you use Mem0?

Pick it when

Use Mem0 when an existing assistant or support bot needs to remember user preferences and facts across sessions, and you want a drop-in memory layer with Python and JavaScript SDKs rather than a new agent framework.

Look elsewhere when

Skip it if you are starting fresh and want memory built into the agent runtime itself, as Letta provides, or if you need to know when facts changed over time, which Graphiti's temporal knowledge graph models explicitly.

Alternatives to Mem0

  • Letta

    Complete stateful agent platform where agents edit their own memory; more opinionated and heavier, but you do not bolt memory onto another framework.

  • Graphiti

    Temporal knowledge graph that tracks when facts became true or were superseded; richer history, but needs a graph database such as Neo4j.

  • Cognee

    Builds knowledge graphs plus vector indexes for agent memory; better for structured knowledge over documents, more setup than a preference store.

  • Agno

    Persists sessions and memory in PostgreSQL as part of a full agent service stack; pick it if you also want the runtime, not just the memory.

Reviews (0)

Leave a Review

No reviews yet. Be the first to review!