Mem0

Persistent memory layer for AI agents and LLM apps

Freemium· Hobby free (10k add / 1k retrieval requests per month) / Starter $19 per month (50k / 5k) / Pro $249 per month (500k / 50k, unlimited projects, private Slack) / Enterprise custom (SLA, on-prem, SSO, audit logs)AgentsModel-agnostic — pluggable via OpenAI, Anthropic, Gemini, Ollama, LiteLLM (no in-house LLM)

Visit website →

Best for

Teams shipping stateful AI agents, copilots, or long-running chat apps where cross-session recall of user facts, preferences, and history is a product requirement rather than a nice-to-have.

Skip if

One-off single-turn chatbots, stateless RAG-over-docs apps, or hobby projects where a short conversation buffer inside the prompt is already enough — the extra infra is not worth it.

Mem0 is an open-source memory layer that gives LLM agents and chat apps persistent, cross-session context without stuffing every prior turn into the prompt. It sits between your model and your data flow: you call add() with a conversation or event, Mem0 runs a hierarchical distillation pass that extracts durable facts, preferences, and entities, and stores them in a vector-and-graph backed store; you then call search() at inference time to pull only the fragments that matter for the current query. The result is smaller prompts, lower token spend, faster latency, and agents that actually remember what a user told them three sessions ago. It ships as a Python and TypeScript SDK plus a managed cloud (with REST API, CLI, and dashboards) and a self-hostable OSS core, and it plugs into common stacks including OpenAI, Anthropic, Google, and open-weights models via LiteLLM, plus vector stores like Qdrant, Pgvector, Chroma, Weaviate, and graph stores like Neo4j. Typical adopters are teams building customer support copilots, personal AI companions, healthcare and education assistants, sales/CRM enrichment, or long-running autonomous agents where losing state between sessions is the difference between a demo and a product. The managed tier adds project isolation, analytics, SOC 2 Type I, HIPAA readiness, and enterprise governance (audit logs, SSO, air-gapped deployment) for teams that outgrow the OSS install.

Editor's take

Mem0 is the memory layer I reach for first when an agent needs to remember a user across sessions without me building a custom summariser and vector-store pipeline. The OSS-plus-managed split is honest, and the distillation approach genuinely does what it says on the tin. Just be deliberate about which model does the extraction — cheap out there and your 'memory' is mostly noise.

— The AI Tool Bible editorial team

Pros

✅ Open-source core with a permissive Apache-2.0 license and a large community — you can self-host end to end if you don't want a managed dependency
✅ Model-agnostic and vector-store-agnostic: works with OpenAI, Anthropic, Gemini, Ollama, Qdrant, Pgvector, Chroma, Weaviate, Neo4j and more via drop-in providers
✅ Genuine token savings — the hierarchical distillation writes compact facts instead of raw transcripts, which shrinks retrieval prompts and speeds up long-lived agents
✅ Both hosted and self-hosted paths, so you can prototype on the free tier and later move to Kubernetes / air-gapped / on-prem without rewriting
✅ Enterprise-grade governance on paid tiers: SOC 2 Type I, HIPAA, audit logs, SSO, project isolation — rare in the memory-layer space
✅ Simple, well-documented Python and TypeScript SDKs with a small surface (add / search / update / delete) that drops into existing agent frameworks

Cons

⚠️ Extraction quality is only as good as the LLM you point it at — cheap models produce shallow or noisy memories and can miss nuance
⚠️ Managed pricing scales quickly if your agent writes memory aggressively; the $19 Starter's 50k add-cap is easy to blow past on chatty workloads
⚠️ Adds an extra hop and its own vector/graph infra to reason about — for small single-session chatbots it is real overkill
⚠️ Graph memory features are newer and less battle-tested than the flat vector-memory path; expect some rough edges on complex ontologies
⚠️ Self-hosted setup with graph + vector + LLM providers has meaningful ops surface if you were hoping for a one-line install

Use cases

Long-lived customer support copilotsPersonal AI companions and journaling agentsHealthcare intake and follow-up assistantsSales and CRM enrichment agentsEducation tutors with per-student progressMulti-session coding agentsAutonomous research agentsE-commerce shopping assistants