Honcho vs ai-memory vs Letta
Side by side, from each listing’s own data. A row where every column says the same is shown once, dimmed.
 Honchoby HonchoRemove Honcho from this comparison |  ai-memoryby Fabio AkitaRemove ai-memory from this comparison |  Lettaby LettaRemove Letta from this comparison | |
|---|---|---|---|
| Sets it apart | — |
|
|
| What it is | User state management platform for AI apps. Stores user context, preferences, and interaction history to enable personalized multi-session AI experiences. | Gives coding agents self-hosted shared memory and handoffs, so work carries across Claude Code, Codex, Cursor, and other harnesses, machines, and teammates. | Stateful agent framework with built-in memory. Agents persist context between sessions via structured memory blocks. Formerly MemGPT. Self-hosted or managed cloud. |
| Provider | Honcho | Fabio Akita | Letta |
| Official vendor | Not an official listingSame for all | ||
| Verified | YesSame for all | ||
| Access | API | API, MCP, CLI | API, CLI |
| Auth | API Key | Bearer Token | API Key |
| MCP server | No MCP server | In its setup guide | No MCP server |
| CLI install | No CLI | In its docs | In its docs |
| API base URL | In its docsSame for all | ||
| Skills | Persist user session state and conversation context across app restarts, Track evolving user preferences learned from interaction history, Share user context across multiple AI applications from one platform, Link user identity across sessions and devices for unified personalization, Store arbitrary personalization metadata alongside structured session records | Cross-Agent Handoffs, Session Capture, Markdown Wiki Memory, Memory Search, Memory Aging | Persist agent state between sessions using structured in-context memory blocks, Dynamically edit and archive memory to maintain coherent long-horizon agent behavior, Orchestrate multi-agent pipelines where agents pass typed memory between each other, Execute tool calls with full persistence of tool outputs across sessions, Deploy self-hosted or cloud agents with consistent stateful behavior at scale |
| Streaming | No | No | Yes |
| Push notifications | NoSame for all | ||
| Categories | Memory & State | Memory & State, Code & DevTools | Memory & State |
| Tags | memory, user-state, personalization, multi-session, python | long-term-memory, agent-handoffs, coding-agents, markdown-wiki, lifecycle-hooks, mcp-server, self-hosted, rust | memory, stateful-agents, memgpt, open-source, self-hosted, python, orchestration |
| Listed since | Apr 8, 2026 | Oct 31, 2026 | Apr 8, 2026 |
| Use it now | |||
Share this comparison
https://agentswitchboard.dev/compare?a=honcho&b=ai-memory&c=lettaMore comparisons
- GitHub Copilot vs Cursor vs Codeium / Windsurf
Three AI coding assistants, each an official listing. Cursor and Windsurf are editors with multi-file edits and autonomous coding; GitHub Copilot is a pair programmer with an agent mode.
- LangGraph vs CrewAI vs AutoGen
Frameworks for multi-agent systems. LangGraph builds stateful graph workflows, CrewAI teams of agents that delegate, and AutoGen conversational and human-in-the-loop agents in Python and TypeScript.
- Mem0 vs Zep vs Letta
Three ways to give agents long-term memory. Mem0 and Zep are memory layers your agent calls; Letta is a stateful agent framework with memory built in. Mem0 also has an MCP server.
- Pinecone vs Qdrant vs Weaviate
Vector databases for RAG and semantic search. Pinecone is fully managed; Qdrant and Weaviate are open source. Beyond the API, Qdrant has a CLI and Weaviate an MCP server.
- Browserbase vs Browser Use vs Browserless
Browsers for AI agents. Browserbase and Browserless run headless browsers you drive with Playwright or Puppeteer; Browser Use is an open-source Python library that controls websites from natural-language instructions.
- E2B vs Daytona vs Vercel Sandbox
Sandboxes where agents run untrusted code, each with an API and a CLI. E2B runs Python, JS and shell; Daytona provisions dev environments with git; Vercel Sandbox uses Firecracker microVMs.
- Firecrawl vs Crawl4AI vs Jina Reader
All three turn web pages into clean Markdown for LLMs. Firecrawl and Jina Reader take an API key; Crawl4AI needs no auth and adds deep crawling and browser session control.
- Figma MCP Server vs Figma Context MCP vs Talk to Figma MCP
MCP servers that bring Figma designs to coding agents. Figma's own server can also write back to the canvas; Framelink's reads layout and styles; Grab's edits nodes through a Figma plugin.
- Ollama vs LM Studio vs vLLM
Run open models on your own hardware behind an OpenAI-compatible API, with no auth. Ollama and LM Studio run models locally; vLLM is a high-throughput inference server.
- Asana MCP vs ClickUp MCP vs monday.com MCP
Official project-management MCP servers, all hosted with OAuth sign-in. monday.com also has a local npm package and its GraphQL API; ClickUp's is in public beta with no deletion tools.
- Groq vs Cerebras Inference
Fast inference APIs for open models, both OpenAI-compatible with streaming. Groq runs on its own LPU hardware; Cerebras serves models such as Qwen and GPT OSS on wafer-scale chips.
- Deepgram vs AssemblyAI
Speech-to-text APIs with real-time streaming. Deepgram adds text-to-speech for voice agents and a CLI; AssemblyAI adds audio intelligence such as summarization and redaction.
- Neon MCP vs PlanetScale MCP
MCP servers for managed SQL databases with branching. Neon's manages serverless Postgres with an API key; PlanetScale's signs in with OAuth and covers Vitess and Postgres.
