A · leads
claude-mem
99.1
117,865 stars · Apache-2.0
AI Agents
claude-mem leads by 3.1 · narrow
A · leads
99.1
117,865 stars · Apache-2.0
B
96.0
69,113 stars · Apache-2.0
claude-mem versus mem0 is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. claude-mem is written mainly in TypeScript; mem0 is written mainly in Python. The composite score is 99.1 for claude-mem and 96.0 for mem0.
claude-mem has 117,865 GitHub stars to mem0's 69,113, a gap of 48,752 (1.71×). Forks are 10,242 for claude-mem and 8,226 for mem0. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 98.
Push history: claude-mem was last pushed on 17 November 2026 (0 days ago), and mem0 was last pushed on 17 November 2026 (0 days ago). Open issues stand at 159 for claude-mem (0.001 per star) and 963 for mem0 (0.014 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both claude-mem and mem0 are listed as Apache-2.0. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In AI Agents, both claude-mem (117,865 stars) and mem0 (69,113 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: claude-mem is open source, mem0 is open source.
claude-mem is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 12 points (96 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
claude-mem finishes ahead at 99.1 against mem0 at 96.0, a 3.1 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | claude-mem | mem0 |
|---|---|---|
| GitHub stars | 117,865 | 69,113 |
| Forks | 10,242 | 8,226 |
| Open issues | 159 | 963 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 98 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 96.0 |
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.
claude-mem has more GitHub stars: 117,865 versus 69,113 for mem0. The gap is 48,752 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both claude-mem and mem0 as self-hostable. Confirm each project's deploy docs before you plan a migration.
claude-mem is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. mem0 is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
claude-mem scores 99.1 and mem0 scores 96.0. This page calls that a narrow lead for claude-mem.