mem9.ai

The Panel's Take

mem9.ai is an open-source memory server (Apache-2.0) from the TiDB team that gives every agent in your stack a shared, cloud-persistent memory layer with hybrid vector and keyword search. It addresses the core limitation of agent-native memory: most solutions are file-backed and local, meaning memory doesn't follow the user across machines and can't be shared between different agents working on the same project. The system works as a kind: "memory" plugin for OpenClaw and similar frameworks, replacing local file-backed memory slots with a server-backed hybrid search system. Crucially, Claude Code, OpenCode, and OpenClaw agents can all read from and write to the same mem9 server — enabling genuine cross-agent knowledge sharing. Memory persists in the cloud, so it follows the user across laptops, CI environments, and team members. The TiDB team brings production-grade distributed database infrastructure to what is usually a hacky side project. The hybrid vector + keyword search (combining semantic similarity with exact-match retrieval) outperforms pure vector search for structured technical knowledge like code patterns, API schemas, and project conventions.

mem9.ai verdict: SHIP 🚀

3 ships · 1 skip from the expert panel

Full review: shiporskip.io/tool/mem9-ai-persistent-cloud-memory-agents-tidb-2026

Compare mem9.ai with Others

Builder

Ship

“The primitive is clean: a drop-in MCP-compatible memory server that swaps file-backed agent memory for a cloud-persistent hybrid search store backed by TiDB. The DX bet is right — complexity lives at the infrastructure layer (TiDB handles distributed storage and indexing), so the agent-side API stays thin. The moment of truth is connecting a second agent to the same server and watching it recall context the first agent wrote; that's the demo that earns the ship. You could not replicate genuine hybrid vector + keyword search with cross-agent consistency in a weekend script — the distributed consistency guarantees alone are a real engineering problem this solves.”

Skeptic

Ship

“Direct competitors are Zep, Mem0, and whatever LangChain Memory ships next — and mem9 beats them on one specific axis: the TiDB backend means you're not doing vector-only retrieval on structured technical knowledge, where BM25 keyword search materially outperforms cosine similarity. The scenario where this breaks is large teams with conflicting write patterns — there's no obvious memory conflict-resolution story yet, and shared mutable state across agents will produce garbage reads at scale. What kills it in 12 months: OpenAI or Anthropic ships native persistent memory into their API that frameworks adopt overnight — but until that happens, the open-source Apache-2.0 license and TiDB's infrastructure credibility make this the most defensible standalone memory layer I've seen.”

Futurist

Ship

“The thesis is falsifiable: within three years, multi-agent systems working on shared codebases will require a persistent, shared knowledge substrate the same way they require a shared filesystem today — and whoever owns that substrate owns a critical layer of the agent stack. The dependency that has to hold is that agents remain heterogeneous (different vendors, runtimes, frameworks), which keeps a neutral shared memory layer valuable versus each model provider building their own silo. The second-order effect nobody is talking about: if your CI pipeline agents and your local dev agents share the same memory, institutional knowledge stops living in Confluence and starts living in a queryable, semantically indexed store that actually surfaces when relevant — that's a genuine shift in how teams externalize context.”

Founder

Skip

“The buyer here is a platform or infrastructure engineer at a company already running multiple AI agents — a narrow, technical buyer who will self-host before paying for a cloud tier that doesn't exist yet. The moat is real (TiDB's distributed infra is not easily replicated and the Apache-2.0 open-core is a proven wedge strategy), but the monetization path is invisible: 'cloud hosted pricing TBD' is not a business model, it's a GitHub repo with ambitions. What would flip this to a ship is a credible hosted tier with pricing that scales on memory operations or agent seats — something that creates a natural land-and-expand motion from the indie dev who self-hosts to the enterprise team that pays for managed reliability.”