기본 콘텐츠로 건너뛰기

Mem0 vs Zep vs Letta: Choosing an AI Agent Memory Layer

Summary: Mem0, Zep and Letta all promise that your AI agent will "remember" users between sessions, but they solve different problems. Mem0 is a lightweight add-and-search memory API with a generous free tier, Zep builds a temporal context graph and bills by the size of the data you send it, and Letta makes the agent itself the long-lived object, with memory stored as files the agent edits. This guide compares how each one works, what the free plans really include, and which one fits which kind of project.

Why "memory" is a separate layer at all

A chat model only knows what is inside its current context window. If a user told your support bot last week that they are vegetarian, or that their account is on the annual plan, that fact is gone the moment the conversation ends unless you store it somewhere and feed it back in. You can do this yourself with a vector database (we compared the main options in Pinecone vs Qdrant vs Weaviate for Your First RAG App), but then you also have to decide which sentences are worth keeping, how to resolve conflicts when a fact changes, and how to rank old facts against new ones.

Memory layers package those decisions. The three tools below take noticeably different positions on who decides what to remember: a service-side extractor (Mem0), a knowledge graph that tracks when facts were true (Zep), or the agent itself (Letta).

Mem0: add messages, search facts

Mem0's hosted Platform has the smallest learning curve of the three. The official quickstart boils down to four steps:

  1. Install the SDK with pip install mem0ai (Python) or npm install mem0ai (JavaScript). A CLI is also available as @mem0/cli or mem0-cli.
  2. Create a MemoryClient with the API key from the Mem0 dashboard.
  3. Call client.add(messages, user_id="user123") with a normal list of user and assistant messages.
  4. Later, call client.search("What are my dietary restrictions?", filters={"user_id": "user123"}) and pass the returned memories to your model.

The interesting part is step 3. Mem0 does not store your messages verbatim; it extracts separate facts. In the docs example, one user sentence ("I'm a vegetarian and allergic to nuts") becomes two stored memories, each returned later with a relevance score and categories. You never write extraction prompts yourself.

Mem0 also ships an open-source version (the Memory class) for self-hosting, and the docs say some Platform features such as advanced retrieval and custom categories may not be available there. Check which one a tutorial assumes before copying its code.

Zep: a temporal context graph

Zep is heavier but more structured. Its v4 agent memory quickstart works like this:

  1. Install zep-cloud (Python), @getzep/zep-cloud (TypeScript) or the Go SDK, and set ZEP_API_KEY.
  2. Create a Zep user for each of your app's users with client.user.create(...), including at least a first name, and store the returned UUID next to your own user ID.
  3. Create a thread per conversation with client.thread.create(user_uuid=...).
  4. Send each message with client.thread.add_messages(...). You can also push business events (a purchase, a support ticket, a played song) as JSON or plain text with client.graph.episode.add(...).
  5. Before each model call, fetch a "Context Block" with client.thread.get_context(thread_uuid) and place it in the prompt.

The Context Block is assembled from semantic, full-text and graph search, using the four most recent thread messages as the query, and it can include a user summary plus facts with date ranges showing when each one was valid. That date tracking is Zep's main selling point: if a customer changed plans in March, the graph can tell the old fact from the current one. You can also define a context template (for example, a profile section, the top 10 facts and the top 5 entities) to control the format.

One detail from the docs that many guides skip: Zep tells you to treat the Context Block as untrusted data and keep it out of system or developer messages, because it can contain text written by end users or pulled from documents.

Letta: the agent is the durable object

Letta has moved well beyond being "a memory API". Its current product is an agent harness with a web app, a CLI and an Agent SDK, built on the idea that you create an agent once and resume it from anywhere. Memory belongs to the agent:

  • You can set starting memory at creation time with persona and human shortcuts, or a full memory list of label and value pairs.
  • Each memory entry becomes a Markdown file in a git-backed repository the agent owns (Letta calls this MemFS). Files under system/ are in the system prompt every turn; everything else stays out of context until the agent reads it.
  • "Dreaming" runs background subagents that review recent conversations and update memory, triggered after a set number of steps or on context compaction.

The SDK is JavaScript/TypeScript (@letta-ai/letta-agent-sdk). The cloud backend needs a Letta API key, while the local backend needs no account; running the runtime yourself requires Node.js 22.19 or newer. If you only want to bolt memory onto an existing chatbot, Letta asks you to rethink more of your app than Mem0 or Zep do. If you are building long-running assistants or coding agents, that is exactly the point.

Plans and free limits compared

All figures below come from each vendor's official pricing page on the verification date. Prices are in US dollars per month.

Item Mem0 Zep Letta
Free plan Free: unlimited end users; first 30 days 10,000 adds and 1,000 retrievals a month with model calls on Mem0; with your own LLM key 50,000 adds and 10,000 retrievals a month 10,000 credits a month, no rollover or auto top-up; 2 projects; variable rate limits; lower-priority processing $0: limited agents, 5 MiB storage per memory repository, limited Letta Auto usage, bring your own API keys
First paid tier No public paid tier; usage-based billing past free limits with a monthly cap you set, then Custom Flex $125 (50,000 credits, then $25 per 10,000); Flex Plus $375 (200,000 credits, then $75 per 40,000) Pro $20 (Letta Auto quota, up to 20 stateful agents, 50 MiB storage); API Plan $20 plus $0.10 per active agent and $0.00015 per second of tool execution
What you pay for Add and retrieval requests Data ingested: 1 credit per Episode up to 350 bytes, +1 per extra 350 bytes; retrieval and storage cost 0 credits Model usage through Letta, active agents and tool time
Best fit Adding user memory to an existing chatbot quickly Apps where facts change over time and business data matters Long-lived agents that should learn and manage their own memory

Zep's billing model deserves a closer look. Because you pay for what you send in, not for reads, the size of each message matters. The pricing FAQ gives the examples itself: a 640-byte Episode costs 2 credits, a 1,200-byte Episode costs 4. If you push long JSON events into the graph, trim fields you do not need before sending them. Mem0 is the reverse: retrievals are the scarcer free resource (1,000 a month in the first 30 days without your own key), so cache search results within a session instead of searching on every turn.

Editor's note

Who it's for: Mem0 suits solo developers and small teams who want user memory working in an afternoon. Zep suits support, sales and account tools where the "current truth" about a customer changes and you have CRM or event data to feed in. Letta suits people building persistent assistants or coding agents in TypeScript who are fine adopting its whole agent model.

Who it's not for: If your bot only answers questions from fixed documents, you need retrieval over documents, not user memory; a RAG setup like the one in our Dify help-docs chatbot playbook is simpler.

Gotchas and fixes:

  • Mem0 returns an empty list after add. According to Mem0's FAQ this is often expected: definitional questions ("What is backpropagation?") and general knowledge without personal context are not extracted as memories. Test with a personal statement before assuming a bug.
  • Old Mem0 code fails on the current SDK. Mem0's docs note that parameters such as output_format, api_version, async_mode and enable_graph were removed in the current major version; follow the migration guide instead of patching calls one by one.
  • Zep mixes up people. The quickstart warns to give at least a first name (ideally a last name) when creating users, and to include the user's name or ID in business data, so the graph links facts to the right person.
  • Zep Context Block in the system prompt. Don't put it there. Place it after the conversation history and before the latest user request, and replace the previous block each turn rather than appending another one.
  • Letta memory not visible to the agent. Only files under system/ are always in context; anything else must be read on demand, so put must-know facts there.

How to choose in five minutes

Pick Mem0 if

You already have a working chatbot and want it to stop asking returning users the same questions. Its add/search API maps cleanly onto an existing message loop, and the free tier with your own LLM key (50,000 adds a month) is enough to run a real beta.

Pick Zep if

Facts about your users change and you care about which version is current, or you want to merge chat history with events from your product. Budget for at least the $125 Flex plan once you leave prototyping, since the free plan has variable rate limits and lower-priority processing.

Pick Letta if

The agent itself is your product: a teammate-style assistant that runs for weeks, uses tools, and should get better over time. Start on the free plan with your own model keys, and remember that heavy tool use drains Letta Auto quota faster, which Letta's own pricing page says plainly.

Whichever you choose, log what memory is being injected and what it costs per conversation. A tracing tool makes that easy; see our Langfuse playbook for finding costly and bad LLM answers. The official pricing screenshots are at the end of this post.

FAQ

Q: Can I try all three without paying?
A: Yes. Mem0 and Letta both have $0 plans, and Zep gives 10,000 free credits a month. The limits differ a lot, so check the table above before you plan a launch on a free tier.

Q: Does Zep charge me every time my agent reads memory?
A: No. Zep's pricing page lists 0 credits for retrieval, storage, threads, users and graph storage; credits are used when you send Episodes (messages or data) in, and webhook invocations cost 1/8 credit where available.

Q: Can I self-host instead of using the cloud?
A: Mem0 has an open-source Memory class, Letta's agent harness is open source with a local backend and a self-hosted App Server, and Zep offers deployment in your own VPC on its Enterprise plan.

Start with the smallest tool that solves today's memory problem, and switch only when your data model actually outgrows it.

Official screenshots: Mem0 pricing page, Zep pricing page (plans and credits), Letta pricing documentation, captured by lightmind24.

Last verified: 2026-11-04
Sources: Mem0 pricing, Mem0 Platform quickstart, Mem0 FAQs, Zep pricing, Zep agent memory quickstart, Letta pricing, Letta Agent SDK memory.

Uploaded Image Uploaded Image Uploaded Image Uploaded Image

댓글

이 블로그의 인기 게시물

브루(Vrew) 요금제 정리: 무료 200크레딧으로 어디까지 쓸 수 있나

요약: 영상 자막 편집기 브루(Vrew)는 2026년 4월 22일부터 기능별 사용량 대신 '통합 크레딧' 하나로 요금을 매겨요. 무료 플랜은 매달 200크레딧이 들어오는데, 음성 분석(자동 자막)만 쓰면 최대 200분 분량이라 짧은 영상 몇 편은 충분하지만, 영상 초반의 Vrew 마크를 지우려면 유료 플랜이 필요해요. 이 글은 브루 공식 가격 페이지와 고객센터 공지를 2026년 10월 23일에 다시 확인해, 크레딧 계산법과 플랜 고르는 기준을 정리했어요. 목차 브루 요금 구조: 통합 크레딧이란 1크레딧으로 할 수 있는 일 무료 플랜으로 되는 것과 안 되는 것 유료 플랜 4종 비교표 월 구독·연 구독·기간 이용권, 무엇이 이득일까 상황별 추천: 학생·직장인·유튜버 크레딧이 모자랄 때: 사용 기록 지우개 업그레이드·환불 전에 알아둘 규칙 운영자 메모, 자주 묻는 질문 1. 브루 요금 구조: 통합 크레딧이란 예전 브루는 플랜마다 음성 분석 몇 분, AI 목소리 몇 자, 번역 몇 자처럼 기능별 한도를 따로 줬어요. 그런데 보이저엑스(브루 운영사)가 실제 이용 데이터를 보니 한두 가지 기능만 집중해서 쓰는 사람이 훨씬 많았다고 해요. 그래서 2026년 4월 22일 업데이트부터는 플랜마다 정해진 크레딧을 받고, 어떤 기능에 쓸지는 내가 정하는 방식으로 바뀌었어요. 플랜별 매달 지급량은 Free 200 · Light 2,000 · Standard 10,000 · Business 12,000크레딧 이에요. 공식 공지에 따르면 무료 사용자는 매달 1일에, 유료 사용자는 매월 결제일에 충전되고, 남은 크레딧은 다음 달로 넘어가지 않아요. 바뀐 뒤 무엇이 좋아졌나 공지에 나온 예시가 이해하기 쉬워요. Standard 플랜에서 AI 목소리만 쓰면 예전에는 최대 50만 자였지만, 지금은 1만 크레딧을 모두 AI 목소리에 몰아 쓸 수 있어 최대 100만 자가 돼요. 반대로 여러 기능을 골고루 쓰는 사람은 크레딧이 기능끼리 ...

에이닷 전화 vs 익시오: 통화 녹음·AI 요약, 내 통신사·폰에 맞는 앱 고르기

요약: 통화 녹음과 AI 요약을 쓰고 싶다면 먼저 내 통신사와 휴대폰 종류부터 확인해야 해요. LG유플러스 고객은 무료 앱 익시오, SKT 고객은 에이닷 전화가 가장 기능이 많고, 다른 통신사의 아이폰 사용자는 iOS에 들어 있는 기본 통화 녹음·전사 기능이 현실적인 선택이에요. 이 글은 2026-10-30에 SKT·LG유플러스·Apple 공식 페이지와 도움말을 직접 확인해 세 가지를 비교했어요. 왜 '앱 기능'보다 '내 조건'을 먼저 봐야 할까요 통화 요약 앱 비교 글을 보면 기능 목록부터 나열하는 경우가 많아요. 그런데 실제로 써 보려는 사람에게 가장 먼저 걸리는 건 기능이 아니라 이용 조건 이에요. 익시오는 LG유플러스 고객 전용이고, 에이닷 전화는 누구나 설치할 수 있지만 통역콜·baro 같은 기능은 SKT 고객에게만 열려 있어요. 아이폰은 운영체제 구조상 앱이 통화를 마음대로 녹음하기 어려워서, 통신사 앱이 안 되면 iOS 기본 기능에 기대야 해요. 그래서 이 글은 "어떤 앱이 제일 좋은가"보다 "내 통신사·내 폰에서 무엇을 쓸 수 있나" 순서로 정리했어요. 기능 차이는 그다음이에요. 한눈에 비교: 에이닷 전화 vs 익시오 vs 아이폰 기본 통화 녹음 구분 에이닷 전화 (SKT) 익시오 ixi-O (LG유플러스) 아이폰 기본 통화 녹음 (Apple) 누가 쓸 수 있나 통신사 구분 없이 앱 설치 가능. 단, 통역콜·baro·그룹통화 발신 등은 SKT 고객 전용 U+ 모바일 고객. 타 통신사, 만 14세 미만, 선불요금제 고객은 제한 (공식 사이트 FAQ상 알뜰폰 중 KB리브엠은 예외) 지원 국가·언어의 iPhone 사용자. 1명과 통화할 때만 녹음 가능 지원 OS·기기 Android 10 이상, iOS 16 이상 iOS 17 이상 iPhone 12 이상 / Android...

타입캐스트 vs 클로바더빙: 수익 나는 채널에 쓸 때 무료·유료 조건 비교

요약 타입캐스트와 클로바더빙은 둘 다 글만 입력하면 한국어 AI 목소리를 만들어 주는 서비스지만, 무료로 쓸 수 있는 범위가 꽤 다릅니다. 클로바더빙 무료는 매달 15,000자까지 쓸 수 있는 대신 수익이 생기는 채널에는 쓸 수 없고, 타입캐스트 무료는 처음에 주는 약 5분 분량의 다운로드로 끝나는 체험판에 가깝습니다. 광고 수익이 붙은 유튜브나 쇼핑몰 영상에 넣을 목소리라면 처음부터 유료 플랜 조건을 보고 고르는 편이 안전합니다. 왜 이 두 서비스를 같이 비교하나 쇼츠 내레이션, 수업 자료 더빙, 상품 소개 영상처럼 "내 목소리 대신 AI 목소리"가 필요할 때 한국 사용자들이 가장 많이 찾는 곳이 네오사피엔스의 타입캐스트 와 네이버의 클로바더빙 입니다. 기능 소개만 보면 비슷해 보이지만, 실제로 문제가 되는 건 음질보다 "이 목소리를 내 채널에 써도 되나" 입니다. 그래서 이 글은 기능 나열보다 무료 사용 범위, 출처 표기 의무, 유료 플랜 가격과 다운로드 한도를 중심으로 정리했습니다. 모든 수치는 2026년 10월 25일에 두 서비스의 공식 요금 페이지와 고객센터 도움말에서 직접 다시 확인한 내용입니다. 한눈에 보는 비교표 항목 타입캐스트 무료 타입캐스트 베이직 클로바더빙 Free 클로바더빙 Standard 월 요금 0원 9,900원 (연간 결제 시 10% 할인) 0원 19,900원 (네이버 클라우드 플랫폼에서 결제) 무료·포함 사용량 음성 생성·재생 무제한, 다운로드는 최초 3,000크레딧(약 5분) 1회 지급 월 30,000크레딧(약 60분) 월 15,000자, 다운로드 월 20회, 프로젝트 누적 5개 (매월 1일 갱신) 월 30,000자, 다운로드 월 40회, 프로젝트 누적 20개 쓸 수 있...