Comparisons
Supermemory alternatives for coding agents.
Looking for a Supermemory alternative? Eight options, from open-source memory layers to the memory built into Claude Code and Copilot: what each is for, whether it is open source, how it connects to coding agents and what it costs.
- 8 alternatives, each linked to its source
- Checked October 15, 2026
- The best pick by need, then the full table
- Serving memory and engineering memory, told apart
- Remembers
- The person on the other side of the chat
- Why the software is the way it is
- Unit of memory
- A fact about a user
- A decision, a fix, a constraint, with its reasoning
- Who reads it
- Your product, for each end user
- Every engineer and coding agent on the team
Same word, different job. The split in full: Serving Memory vs. Engineering Memory.
The best Supermemory alternative, by what you need
It depends on what you want memory for. As of October 2026:
- Memory for your AI app’s users, like Supermemory: Mem0, the most widely used open-source memory layer, or Zep for facts that change over time
- Open source and self-hosted: Mem0 (Apache-2.0), Hindsight (MIT) or Basic Memory (AGPL-3.0, plain Markdown). Supermemory itself is MIT-licensed and runs locally
- One developer in Claude Code: Claude Code’s built-in memory (CLAUDE.md and auto memory), or claude-mem
- A team’s coding agents sharing what they work out across Claude Code, Codex, Cursor and Copilot: Recallium (this site): why it is built for that
Serving memory or engineering memory?
Serving memory
For the AI app you ship to your users
Memory you build into your own AI application so it remembers its users and their documents. Supermemory, Mem0 and Zep are built for this; Supermemory and Mem0 also ship coding-agent plugins.
Engineering memory
For the team and coding agents that build it
Memory your coding agents read and write while the team builds: the memory built into Claude Code and GitHub Copilot, Markdown-based tools such as Basic Memory, and Recallium, which shares what the team works out across every teammate’s agent.
Supermemory and 8 alternatives, compared
| Option | What it is and who it’s for | How it connects to coding agents | Deployment and pricing |
|---|---|---|---|
| 1RecalliumPricingWhy Recallium | What it isEngineering memory for engineering teams: what the team works out in agent sessions, from why it was built this way to what broke and what fixed it, linked to files. | How it connectsOver MCP: Claude Code, Codex, Cursor, GitHub Copilot and 60+ MCP clients; one installer wires 16+ coding agents. | Deployment and pricingManaged cloud, priced per engineer; Cloud Free has 500 memories a month until December 2026. Join the waitlist. |
| 2SupermemoryPricingClaude Code pluginMCP | What it isA memory and context engine you build into an AI application so it remembers its users: documents, connector content and conversation memories. Pro is “3 team seats, unlimited end users”. | How it connectsSDKs, a hosted MCP server, and Claude Code and Cursor plugins; the Claude Code plugin keeps project memory in a per-repository container, separate from personal memory. | Deployment and pricingManaged service, plus MIT-licensed open source that can run locally; self-hosted deployments on Scale and Enterprise. Credits for tokens, queries and operations: Free, Pro $19/mo, Max $100/mo, Scale $399/mo. |
| 3Mem0PricingClaude Code pluginMCP | What it isA memory layer you build into an AI application so it remembers its users: facts and preferences extracted from conversations, scoped by user, agent or run. “Unlimited end users” on every tier. | How it connectsPython and JavaScript SDKs, a hosted MCP server, plugins for Claude Code, Codex, Cursor and OpenCode, and agent skills for Windsurf; the Claude Code plugin shares one pool per repository. | Deployment and pricingManaged platform, or Apache-2.0 open source you self-host. Metered by add and retrieval requests: Hobby free, Starter $19/mo, Pro $249/mo, Enterprise custom. |
| 4ZepPricingDocsGraphiti MCP | What it is“The unified context layer for enterprise data”: business data, documents and conversations in context graphs, for teams building their own agents. | How it connectsPython, TypeScript and Go SDKs. Its open-source Graphiti framework has an experimental MCP server documented for Claude Desktop and Cursor; a Claude Code and Codex plugin helps you build with Zep. | Deployment and pricingManaged cloud metered in credits by episode size: Free (10,000 a month), Flex $125/mo, Flex Plus $375/mo, Enterprise custom with your own keys or your own cloud. |
| 5HindsightGitHubCloud billing | What it isAgent memory from Vectorize that retains, recalls and reflects on what an agent learns. It can also build per-repository memory for coding agents from git history. | How it connectsEvery server has a built-in MCP endpoint; it installs repository memory for Claude Code, Codex CLI and Cursor CLI. | Deployment and pricingMIT-licensed open source you run with Docker, pip or Helm, or Hindsight Cloud with prepaid usage. |
| 6claude-memGitHubCMEM | What it isA memory plugin built for Claude Code: it captures what the agent does in each session, compresses it with an AI model and brings relevant context back in later sessions, on your machine. | How it connectsLifecycle hooks plus MCP search tools, with a local web viewer. Claude Code first; also Codex, Gemini, Copilot, OpenCode and more. | Deployment and pricingApache-2.0 open source with a local worker, SQLite and Chroma. Compression spends model tokens; CMEM Pro ($30/mo) adds hosted observation and cloud sync. |
| 7Basic MemoryHomePricing | What it isKnowledge kept as plain Markdown files you own, with a full-text, semantic and knowledge-graph index on top; for individuals and teams who want memory they can read. | How it connectsOver MCP; works with Claude, Codex, Cursor and VS Code, and with Obsidian for the files. | Deployment and pricingFree AGPL-3.0 open source that runs locally; cloud sync with shared workspaces from $15/seat/mo (Team) or $30/seat/mo (Business). |
| 8Claude Code memory (CLAUDE.md and auto memory)Memory docs | What it isBuilt into Claude Code: CLAUDE.md files you write (project, user or org scope) and auto memory, notes Claude writes itself from your corrections and preferences. | How it connectsLoaded at the start of every Claude Code session. A project CLAUDE.md is shared with the team through version control; auto memory is per repository and machine-local, “not shared across machines or cloud environments”. | Deployment and pricingPlain files in the repository and on your machine; part of Claude Code, with no separate product to buy. |
| 9GitHub Copilot MemoryCopilot Memory docs | What it isFacts about your repositories and your personal coding preferences that Copilot remembers. Repository facts are shared with everyone who has Copilot Memory access to that repository; preferences stay private. | How it connectsUsed by Copilot cloud agent, Copilot code review, Copilot CLI and agentic autofix. Copilot checks each fact’s citations against the current branch before using it. | Deployment and pricingHosted by GitHub, in public preview. On by default for individual plans; an administrator enables it on organization and enterprise plans. Unused facts are deleted after 28 days. |
Checked October 15, 2026 against each vendor’s own documentation and pricing pages, linked under each name. Features, prices and availability change, so follow the links for current terms. All nine tools compared, with when to use what.
Recallium vs Supermemory, feature by feature
Product details checked October 15, 2026; features, prices and availability vary by edition. The benchmark figures measure different things: Recallium’s headline is retrieval at depth ten and Supermemory’s at depth twenty “with aggregation”, a term their report never defines, so this is not a controlled head-to-head ranking. Supermemory’s report is published again with 97% recall@20, evaluated May 2026; through early September 2026 it gave 95% recall@15. Benchmark figures checked October 17, 2026; the major memory systems’ LongMemEval scores are side by side in the leaderboard. Sources: Supermemory documentation and GitHub. The split in full: Serving Memory vs. Engineering Memory.
How Recallium and Supermemory differ in practice
Recallium
Engineering memory for the engineers and coding agents who build it
Recallium is built only for the team doing the building. It follows how engineering teams work, from the approach and the decision to the root cause and the fix, each linked to its files; workstreams, working state and session recap carry an effort between sessions and teammates; team rules load into every session; commit trailers tie each commit to the memories behind it; and one installer connects 16+ coding agents.
Supermemory
Serving memory for the AI product you ship to your users
Supermemory is a memory and context engine you build into an AI application so it remembers its users: it ingests documents and connected services alongside conversation memories. Its Claude Code plugin is real: it keeps project knowledge for each repository separate from personal memory, which its docs call team memory; how teammates share that container is not described in the docs, and per-tag access control comes with the Scale plan. If you want to try Supermemory for coding, it works.
Both are measured on LongMemEval-S, where Recallium publishes its full protocol.
When to choose Recallium
- Your agents work in a shared codebase and need the same context
- You want decisions, patterns and fixes captured from agent sessions, not just facts about users
- Your team uses Claude Code, Codex, Cursor or Copilot and wants one memory across them
- You want handoffs, team rules and commit-linked decisions, not only recall
- You want a benchmark whose reader, judge and depth are published
When to choose Supermemory
- You need general-purpose memory for an application, not a coding workflow
- You want connectors that pull documents and services into memory
- You want to run it locally from the open-source repository today
Questions
What are the best Supermemory alternatives?
For memory inside your own AI app: Mem0, Zep and Hindsight. For coding agents: the memory built into Claude Code and GitHub Copilot, claude-mem for one developer in Claude Code, Basic Memory for Markdown notes you own, and Recallium for memory a whole team’s agents share. All eight are compared with Supermemory in the table above, as of October 2026.
Is there an open-source Supermemory alternative?
Several: Mem0 (Apache-2.0), Hindsight (MIT), Zep’s Graphiti engine (Apache-2.0), Basic Memory (AGPL-3.0) and claude-mem. Supermemory is itself MIT-licensed and can run locally, so if open source is the only reason to switch, you may not need to.
Who are Supermemory’s competitors?
As memory APIs for AI apps: Mem0, Zep, Letta, Cognee and Hindsight. As memory for coding agents: the built-in memory of Claude Code, Copilot and Cursor, claude-mem, Basic Memory and Recallium.
Can I self-host Supermemory?
Yes. The open-source repository runs locally, and Supermemory lists self-hosted deployments on its Scale and Enterprise plans, with air-gapped installs on Enterprise (pricing, October 2026).
Which Supermemory alternative works with Claude Code and Cursor?
Mem0 ships Claude Code and Cursor plugins; Hindsight, Basic Memory and Recallium connect over MCP; claude-mem is built for Claude Code first. Recallium connects Claude Code, Codex, Cursor and Copilot to the same memory with one installer.
Memory your whole team’s agents share.
Recallium remembers what your team decides and fixes, and hands it to Claude Code, Codex, Cursor and Copilot. Join the waitlist for Recallium Cloud, the managed engineering memory for your team.