- Not local but hosted, meaning the memory will be stored remotely on their servers via an API. - Not directly integrated with your codebase but with the agent itself, which means that memory is automatically injected and captured within Claude Code, Cursor or Codex without any custom code of your own. Their offerings are SDKs which you have to integrate yourself. - Tool agnostic, since it uses MCP, meaning that memory is not tied to one specific app.
Summary: if privacy and "works in my existing agent with no code" is what you care about, go for PMB. If you need a hosted service for your own product, go for theirs.
Two things that do make it different from their solutions:
1. An adaptive per-project lexicon that is created from your own memories and adjusts the weighting to give more relevance to your project's lexicon. It focuses on one codebase only. I have never seen that in both.
2. Memories are rule-aware: "lesson" is a first-class citizen, and the retrieval process tries to show the rule rather than the event where it was applied and whether the rule was followed.
Thus, the advantage is in project specialization and rule awareness.
oleksiijko•1h ago
oleksiibond•1h ago
Write: while working, PMB stores facts, decision, and learnings on MCP (automatically using hooks). Everything is saved to SQLite, gets embedded, and the entities get linked to a graph.
Read: before answering the prompt, a hook does a search (BM25 + embedding + entities graph using RRF) and provides the best matches. No manual recall required.
All on-premises: SQLite + LanceDB, embedder on-premises, and optionally Ollama.