Cognee Review: Open-Source AI Memory for Agents

Key highlights:

• Four-verb API: `remember`, `recall`, `forget`, `improve` — the whole mental model fits on a napkin

• Graph + vector: not just semantic search — it extracts entities and edges into a knowledge graph

• Self-hosted: runs locally, Postgres/PGVector or Neo4j backends, nothing gated behind a paid tier

• Multi-surface: Python SDK, TypeScript/Rust clients, a CLI, a web UI, and an MCP server

• Ships with an OpenAI-compatible API so it drops into existing stacks

Every developer building an agent hits the same wall: the context window is not memory. You can jam the last 20 messages back in on every turn, but that's a rolling buffer, not recall. Real memory needs three things a naive RAG pipeline doesn't give you:

1. Persistence — knowledge learned in session 1 is available in session 100 without re-ingestion.

2. Structure — "Acme's CTO is Dana, and Dana approved the migration" is two entities and a relationship, not a fuzzy blob of tokens.

The AI-memory space got crowded fast. The honest framing from the community is that these tools sit on a spectrum from "dead simple" to "explicit knowledge structures":

A widely-shared r/LocalLLaMA teardown of eight memory systems put it well: Mem0's core loop is "two LLM calls — the simplest architecture of the eight," Letta hands the agent tools to manage its own memory, while Cognee, Graphiti, Hindsight, and EverMemOS build explicit knowledge structures. If your data has real relationships — org charts, codebases, product docs, regulations — the explicit-structure camp tends to win. If you just want "remember what the user said last time," Mem0 is less to reason about.

On the self-hosting axis specifically, the recurring recommendation is that Cognee (Apache 2.0) and Hindsight (MIT) are the closest open matches to what Mem0 does — automatic extraction, vector plus graph retrieval, and nothing behind a paywall. For air-gapped or on-prem enterprise deployments, Cognee shows up on almost every "Mem0 alternative" shortlist.

Cognee has an unusually engaged following for an infra project — it spun up its own subreddit (r/AIMemory) and a Discord, and it consistently trends on Trendshift. The sentiment in the GraphRAG-comparison threads is telling. From an r/AIMemory user who tried all three:

> "I prefer Cognee (no affiliation) after trying Mem0 and Graphiti. Mem0 was easy-ish to get set up, but didn't offer the cutting-edge configurations I was looking for. It also appeared to me to be poorly maintained (my impression only)."

That's the pattern across threads: people who want control over the memory pipeline gravitate to Cognee; people who want the fastest possible "hello world" reach for Mem0 first. The counter-signal is real too — some users note that Cognee's flexibility comes with more moving parts, and that its published benchmark numbers lag competitors like Hindsight (91.4%) and Mem0 on temporal-reasoning tests, which makes apples-to-apples procurement comparisons harder.

This is a condensed version. The full article includes architecture diagrams, code examples, comparison tables, and practical use cases.

👉 Read the complete analysis on andrew.ooo

Topics: cognee, ai-memory, ai-agents, knowledge-graph, graphrag