Rank #5 of 6 in AI Memory Layers
Showcase


Try itExperimental
See what an agent can do with Cognee before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$uvx --from cognee cognee-cli demo && uvx --from cognee cognee-cli forget --dataset demorecorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Data lifecycle — stories about data lifecycle in this arenaData lifecycleevidence →
Stories about data lifecycle in this arena
Deployment self host — stories about deployment self host in this arenaDeployment self hostevidence →
Stories about deployment self host in this arena
Graph entity memory — stories about graph entity memory in this arenaGraph entity memoryevidence →
Stories about graph entity memory in this arena
Memory recall quality — stories about memory recall quality in this arenaMemory recall qualityevidence →
Stories about memory recall quality in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plansevidence →
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Retrieval performance — stories about retrieval performance in this arenaRetrieval performanceevidence →
Stories about retrieval performance in this arena
Sdk integrations — stories about sdk integrations in this arenaSdk integrationsevidence →
Stories about sdk integrations in this arena
Session context — stories about session context in this arenaSession contextevidence →
Stories about session context in this arena
Tenancy permissions — stories about tenancy permissions in this arenaTenancy permissionsevidence →
Stories about tenancy permissions in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 34 free · 0 paid · 0 enterprise · 2 not stated in evidence
Follow the green: where the map greys out is where Cognee stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓7/10
unlocks → Webhooks · Scoped API keys · Machine-readable spec · Versioning policy · Drop the memory layer into agent frameworks like LangChain, LangGraph, CrewAI, or the Vercel AI SDK via documented first-party integrations · Wire memory into real-time voice pipelines (e.g. LiveKit, Pipecat, ElevenLabs) with documented integrations fast enough for live conversation
Subscribe to events via webhooks
—–
Build against official SDKs
~6/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~6/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—0/10
Operate the product with natural-language commands
✓7/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~6/10
Set up automations that run autonomously in the background
~4/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Data lifecycle — stories about data lifecycle in this arenaData lifecycle
Stories about data lifecycle in this arena
Deployment self host — stories about deployment self host in this arenaDeployment self host
Stories about deployment self host in this arena
Graph entity memory — stories about graph entity memory in this arenaGraph entity memory
Stories about graph entity memory in this arena
Memory recall quality — stories about memory recall quality in this arenaMemory recall quality
Stories about memory recall quality in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Retrieval performance — stories about retrieval performance in this arenaRetrieval performance
Stories about retrieval performance in this arena
Sdk integrations — stories about sdk integrations in this arenaSdk integrations
Stories about sdk integrations in this arena
Session context — stories about session context in this arenaSession context
Stories about session context in this arena
Context assembly
Tenancy permissions — stories about tenancy permissions in this arenaTenancy permissions
Stories about tenancy permissions in this arena
Govern who and what can read or write memory with roles, policies, or access-control lists, and audit that access
~5/10
Scope memories per user, agent, or application so one tenant's memories never leak into another's retrieval
~7/10
Share selected memory across multiple agents or users (team or group memory) while keeping private memory private
~7/10
Sorted by importance (agentic first) (high → low) · 57/57 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | fullfree | 8/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | fullfree | 7/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | fullfree | 8/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | fullfree | 7/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partialfree | 6/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partialfree | 6/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partialfree | 6/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partialfree | 6/10 | Cclaimed | |
Add memories from conversations and retrieve them later with semantic search, so context persists across sessions C Core memory | developer | Memory recall quality — stories about memory recall quality in this arenaMemory recall quality | 3 | fullfree | 8/10 | Xcommunity | |
My agent can manage its own memory mid-conversation — adding, searching, updating, and deleting memories through tools or API calls it invokes itself C Agent memory | ai-native user | Memory recall quality — stories about memory recall quality in this arenaMemory recall quality | 3 | fullfree | 8/10 | Tprobed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | fullfree | 8/10 | Xcommunity | |
Self-host the memory layer from open-source code (e.g. via Docker) on infrastructure I control C Self host | platform-engineer | Deployment self host — stories about deployment self host in this arenaDeployment self host | 3 | fullfree | 8/10 | Cclaimed | |
Store memories as a knowledge graph of entities and relationships so multi-hop and entity-centric questions are answerable C Knowledge graph | ml-engineer | Graph entity memory — stories about graph entity memory in this arenaGraph entity memory | 3 | fullfree | 8/10 | Xcommunity | |
Get summaries of past sessions or threads so an agent can pick up where the last conversation left off C Context assembly | developer | Session context — stories about session context in this arenaSession context | 3 | partialfree | 7/10 | Cclaimed | |
Scope memories per user, agent, or application so one tenant's memories never leak into another's retrieval C Isolation | developer | Tenancy permissions — stories about tenancy permissions in this arenaTenancy permissions | 3 | partialfree | 7/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partialfree | 5/10 | Cclaimed | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | partialfree | 5/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | fullfree | 8/10 | Cclaimed | |
Delete a user's memories on demand — single memory, per-entity, or full erasure — to satisfy privacy requirements C Forgetting | platform-engineer | Data lifecycle — stories about data lifecycle in this arenaData lifecycle | 2 | fullfree | 8/10 | Cclaimed | |
Ingest documents, JSON, and business data into memory — not just chat transcripts C Ingestion | developer | Session context — stories about session context in this arenaSession context | 2 | fullfree | 8/10 | Cclaimed | |
Connect off-the-shelf assistants (Claude, ChatGPT, Cursor) to the same memory so every tool I use shares what it knows about me C Agent memory | ai-native user | Sdk integrations — stories about sdk integrations in this arenaSdk integrations | 2 | partialfree | 7/10 | Tprobed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partialfree | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partialfree | 6/10 | Tprobed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partialfree | 6/10 | Cclaimed | |
The memory layer decides for itself what is worth remembering — extracting salient facts from raw conversation and consolidating them in the background C Agent memory | ai-native user | Memory recall quality — stories about memory recall quality in this arenaMemory recall quality | 2 | partialfree | 6/10 | Cclaimed | |
Govern who and what can read or write memory with roles, policies, or access-control lists, and audit that access C Governance | platform-engineer | Tenancy permissions — stories about tenancy permissions in this arenaTenancy permissions | 2 | partialfree | 5/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partialfree | 5/10 | Cclaimed | |
Rely on the memory layer to update, supersede, or merge memories when new information contradicts what was stored C Core memory | developer | Memory recall quality — stories about memory recall quality in this arenaMemory recall quality | 2 | partialfree | 5/10 | Cclaimed | |
Retrieve a token-budgeted, prompt-ready context block assembled from relevant memories in one call C Context assembly | developer | Session context — stories about session context in this arenaSession context | 2 | partialfree | 5/10 | Cclaimed | |
Steer retrieval with metadata filters, keyword/hybrid search modes, or reranking instead of accepting a single fixed similarity search C Retrieval controls | developer | Memory recall quality — stories about memory recall quality in this arenaMemory recall quality | 2 | partialfree | 5/10 | Cclaimed | |
See published pricing with a free tier and per-unit rates so I can project memory costs before committing G Pricing | platform-engineer | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 2 | partial | 4/10 | Cclaimed | |
Build against official SDKs in at least Python and TypeScript with equivalent memory APIs C Sdks | developer | Sdk integrations — stories about sdk integrations in this arenaSdk integrations | 2 | partial | 3/10 | Tprobed | |
Drop the memory layer into agent frameworks like LangChain, LangGraph, CrewAI, or the Vercel AI SDK via documented first-party integrations C Frameworks | developer | Sdk integrations — stories about sdk integrations in this arenaSdk integrations | 2 | none | 0/10 | ||
Export memories in a machine-readable format so the memory store is portable and not a lock-in trap C Portability | platform-engineer | Data lifecycle — stories about data lifecycle in this arenaData lifecycle | 2 | none | 0/10 | ||
Ingest at scale with async or batch processing and check the status of background memory operations C Scale | platform-engineer | Retrieval performance — stories about retrieval performance in this arenaRetrieval performance | 2 | none | 0/10 | ||
Make memories expire or decay — via TTL, expiration dates, or recency weighting — so stale facts stop surfacing C Forgetting | developer | Data lifecycle — stories about data lifecycle in this arenaData lifecycle | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
See documented retrieval-latency targets or measured numbers (e.g. p50/p95) backing the product's speed claims C Latency | platform-engineer | Retrieval performance — stories about retrieval performance in this arenaRetrieval performance | 2 | none | untested | none yet | |
See published memory-quality benchmark results (e.g. LongMemEval, LoCoMo) backing the product's recall-accuracy claims C Benchmarks | ml-engineer | Memory recall quality — stories about memory recall quality in this arenaMemory recall quality | 2 | none | untested | none yet | |
Track when facts became valid or invalid (temporal reasoning) so the memory distinguishes current from outdated information C Knowledge graph | ml-engineer | Graph entity memory — stories about graph entity memory in this arenaGraph entity memory | 2 | none | untested | none yet | |
Run the memory layer fully locally — embedded in-process or against local models — without any cloud dependency C Self host | developer | Deployment self host — stories about deployment self host in this arenaDeployment self host | 1 | partialfree | 7/10 | Cclaimed | |
Share selected memory across multiple agents or users (team or group memory) while keeping private memory private C Sharing | developer | Tenancy permissions — stories about tenancy permissions in this arenaTenancy permissions | 1 | partialfree | 7/10 | Cclaimed | |
Customize the memory schema — entity types, edge types, or ontology — to match my domain C Schema customization | ml-engineer | Graph entity memory — stories about graph entity memory in this arenaGraph entity memory | 1 | partialfree | 6/10 | Xcommunity | |
Store images, PDFs, or other files as memory inputs and recall information from them later C Ingestion | developer | Session context — stories about session context in this arenaSession context | 1 | partialfree | 6/10 | Cclaimed | |
Wire memory into real-time voice pipelines (e.g. LiveKit, Pipecat, ElevenLabs) with documented integrations fast enough for live conversation C Frameworks | developer | Sdk integrations — stories about sdk integrations in this arenaSdk integrations | 1 | none | 0/10 | ||
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 43 stories with headroom
What would move Cognee’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
Cognee positions itself as a memory/knowledge-graph backend that other AI assistants (Claude, Cursor, Cline) connect to via MCP, not as a product with its own built-in assistant that users delegate tasks to.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Evidence only shows Cognee shipping its own MCP server so external AI tools (Claude, Cursor, Cline) can call Cognee's memory tools — the reverse direction of the story.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
Cognee's evidence pack shows manual operations (remember, recall, improve, forget) invoked via API, CLI, or MCP calls, but no evidence of a rules/trigger engine that fires actions automatically on events (e.g., webhooks, event listeners, conditional automations).
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Missing: aPI key/credential issuance mechanism, scoping/least-privilege token model, documentation of credential lifecycle management.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
No evidence anywhere in the pack mentions webhooks, event subscriptions, or push notifications; Cognee's integrations (Slack, GitHub, Linear) are described as data sources to ingest, not as an event/webhook subscription mechanism for users.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
Missing: any interactive/runnable API explorer (e.g., Swagger UI, Postman collection, live code sandbox) and independent confirmation of one working.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
Cognee has an 'api-reference' section referencing a REST API and Docker deployment, but a direct probe for OpenAPI/Swagger specs at all standard locations (openapi.json, swagger.json, etc.) returned 404s, and no documentation page links to a downloadable machine-readable spec.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Missing: any versioning scheme documentation, explicit deprecation policy, changelog/migration guides for breaking changes.
Showing the top 8 of 43 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map13 surfaces · 38 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Core concepts docs25 stories
- Drive the product through a documented public API
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Delete a user's memories on demand — single memory, per-entity, or full erasure — to satisfy privacy requirements
- Store memories as a knowledge graph of entities and relationships so multi-hop and entity-centric questions are answerable
- Customize the memory schema — entity types, edge types, or ontology — to match my domain
- My agent can manage its own memory mid-conversation — adding, searching, updating, and deleting memories through tools or API calls it invokes itself
- The memory layer decides for itself what is worth remembering — extracting salient facts from raw conversation and consolidating them in the background
- Add memories from conversations and retrieve them later with semantic search, so context persists across sessions
- Rely on the memory layer to update, supersede, or merge memories when new information contradicts what was stored
- Steer retrieval with metadata filters, keyword/hybrid search modes, or reranking instead of accepting a single fixed similarity search
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Control data retention and deletion
- Build against official SDKs in at least Python and TypeScript with equivalent memory APIs
- Retrieve a token-budgeted, prompt-ready context block assembled from relevant memories in one call
- Get summaries of past sessions or threads so an agent can pick up where the last conversation left off
- Ingest documents, JSON, and business data into memory — not just chat transcripts
- Store images, PDFs, or other files as memory inputs and recall information from them later
- Govern who and what can read or write memory with roles, policies, or access-control lists, and audit that access
- Scope memories per user, agent, or application so one tenant's memories never leak into another's retrieval
- Share selected memory across multiple agents or users (team or group memory) while keeping private memory private
Cognee CLI docs13 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Use an official CLI
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Run the memory layer fully locally — embedded in-process or against local models — without any cloud dependency
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Prevent my data from being used to train AI models
- Build against official SDKs in at least Python and TypeScript with equivalent memory APIs
- Get summaries of past sessions or threads so an agent can pick up where the last conversation left off
Pricing docs10 stories
- Set up automations that run autonomously in the background
- Run the memory layer fully locally — embedded in-process or against local models — without any cloud dependency
- Self-host the memory layer from open-source code (e.g. via Docker) on infrastructure I control
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
- See published pricing with a free tier and per-unit rates so I can project memory costs before committing
- Choose where my data is stored (region/residency)
- Prevent my data from being used to train AI models
- Ingest documents, JSON, and business data into memory — not just chat transcripts
API reference8 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Test against a sandbox environment without touching production data
- Run the memory layer fully locally — embedded in-process or against local models — without any cloud dependency
- Self-host the memory layer from open-source code (e.g. via Docker) on infrastructure I control
- Export all of my data in open formats and leave
- Self-host the core product
- Choose where my data is stored (region/residency)
Cognee cloud docs8 stories
- Test against a sandbox environment without touching production data
- Run the memory layer fully locally — embedded in-process or against local models — without any cloud dependency
- Self-host the memory layer from open-source code (e.g. via Docker) on infrastructure I control
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Self-host the core product
- Choose where my data is stored (region/residency)
- Prevent my data from being used to train AI models
Getting started docs6 stories
- Point an agent at llms.txt or agent-oriented docs
- Perform bulk operations across many items at once
- Store memories as a knowledge graph of entities and relationships so multi-hop and entity-centric questions are answerable
- The memory layer decides for itself what is worth remembering — extracting salient facts from raw conversation and consolidating them in the background
- Ingest documents, JSON, and business data into memory — not just chat transcripts
- Store images, PDFs, or other files as memory inputs and recall information from them later
Python API docs6 stories
- Drive the product through a documented public API
- Build against official SDKs
- Add memories from conversations and retrieve them later with semantic search, so context persists across sessions
- Build against official SDKs in at least Python and TypeScript with equivalent memory APIs
- Retrieve a token-budgeted, prompt-ready context block assembled from relevant memories in one call
- Store images, PDFs, or other files as memory inputs and recall information from them later
Cognee MCP docs5 stories
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Operate the product with natural-language commands
- My agent can manage its own memory mid-conversation — adding, searching, updating, and deleting memories through tools or API calls it invokes itself
- Connect off-the-shelf assistants (Claude, ChatGPT, Cursor) to the same memory so every tool I use shares what it knows about me
Hacker News4 stories
- Store memories as a knowledge graph of entities and relationships so multi-hop and entity-centric questions are answerable
- Customize the memory schema — entity types, edge types, or ontology — to match my domain
- Add memories from conversations and retrieve them later with semantic search, so context persists across sessions
- Self-host the core product
OpenAPI spec3 stories
Llms integrations docs3 stories
cognee.ai2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$uvx --from cognee cognee-cli demo && uvx --from cognee cognee-cli forget --dataset demoreproduced$ uvx --from cognee cognee-cli demo && uvx --from cognee cognee-cli forget --dataset demo
Loading the bundled demo knowledge graph (no API [redacted] required)...
Success: Demo graph loaded into dataset 'demo' (47 nodes, 86 edges).
Query: Who works at Anthropic?
1. Recall queries can traverse this graph: "who works at Anthropic" returns Alice, "what does Cognee depend on" returns litellm and Ladybug,
2. the results in a graph database plus a vector store. For example, Alice works at Anthropic in San Francisco. She contributes to the Cognee project.
3. Cognee is an open-source AI memory platform. It transforms raw text, files, and URLs into a persistent knowledge graph that agents can query.
Query: What does cognee depend on?
1. Recall queries can traverse this graph: "who works at Anthropic" returns Alice, "what does Cognee depend on" returns litellm and Ladybug,
2. The Cognee project depends on litellm for LLM routing and on Ladybug as its default graph backend.
3. the results in a graph database plus a vector store. For example, Alice works at Anthropic in San Francisco. She contributes to the Cognee project.
This demo uses [redacted]word search (CHUNKS_LEXICAL) — it needs no LLM and no embeddings. LLM answers over your own data need LLM_API_[redacted] set.
Next: cognee-cli search "your question" -t CHUNKS_LEXICAL -d demo
Then: set LLM_API_[redacted] and run cognee-cli remember "<path-or-text>" to build memory from your own data.
Clean up with: cognee-cli forget --dataset demo
Success: Done: {'dataset_id': '2c17f96f-27cf-56e7-a036-5592dcc8b4fd', 'status': 'success'}
Next: cognee-cli remember <path-or-text> -d demo to start a new session.
$echo '<jsonrpc initialize>' | uvx cognee-mcpreproduced$ echo '<jsonrpc initialize>' | uvx cognee-mcp
⠋ Resolving dependencies...
⠙ Resolving dependencies...
⠋ Resolving dependencies...
⠙ Resolving dependencies...
⠙ cognee-mcp==0.5.5
⠙ cognee==1.5.4
⠙ cognee==1.5.4
⠙ ladybug==0.19.0
⠙ ladybug==0.19.0
⠙ cognee==1.5.4
⠙ cognee==1.5.4
⠙ httpx==0.28.1
⠙ mcp==1.29.1
⠙ uv==0.12.10
⠙ aiofiles==25.1.0
⠙ aiohttp==3.14.3
⠙ aiolimiter==1.2.1
⠙ aiosqlite==0.22.1
⠙ alembic==1.19.2
⠙ cbor2==6.1.4
⠙ cryptography==50.0.1
⠙ datamodel-code-generator==0.76.2
2026-09-05T00:47:02.614301 [info ] Log file created at: /Users/judegomila/.cognee/logs/2026-09-04_17-47-02.log [cognee.shared.logging_utils] log_file=/Users/judegomila/.cognee/logs/2026-09-04_17-47-02.log
2026-09-05T00:47:02.614462 [warning ] Cognee 1.0 changes: New API — remember/recall/forget/improve (V1 add/cognify/search still work). Session memory enabled by default (CACHING=false to disable). Multi-user access control on by default (ENABLE_BACKEND_ACCESS_CONTROL=false to disable). Agents (@cognee.agent) auto-verified on registration. See https://docs.cognee.ai/ [cognee.shared.logging_utils]
2026-09-05T00:47:02.614531 [info ] Logging initialized [cognee.shared.logging_utils] cognee_version=1.5.4 database_path=/Users/judegomila/.cache/uv/archive-v0/Zc-zBsYgUxmmVznI/lib/python3.13/site-packages/cognee/.cognee_system/databases os_info='Darwin 25.5.0 (Darwin Kernel Version 25.5.0: Tue Jun 9 22:28:34 PDT 2026; root:xnu-12377.121.10~1/RELEASE_ARM64_T6050)' python_version=3.13.15 structlog_version=25.5.0
2026-09-05T00:47:02.614585 [info ] Database storage: /Users/judegomila/.cache/uv/archive-v0/Zc-zBsYgUxmmVznI/lib/python3.13/site-packages/cognee/.cognee_system/databases [cognee.shared.logging_utils]
2026-09-05T00:47:02.770852 [info ] auth posture: authentication=required, multi_tenant=enabled (default (no env vars set)) [get_authenticated_user]
2026-09-05T00:47:04.314340 [info ] Cognee client initialized in direct mode [cognee.shared.logging_utils]
2026-09-05T00:47:04.314474 [info ] MCP transport security: using SDK defaults (localhost only) [cognee.shared.logging_utils]
2026-09-05T00:47:04.314520 [info ] Running database migrations... [cognee.shared.logging_utils]
setup plugin alembic.autogenerate.schemas
setup plugin alembic.autogenerate.tables
setup plugin alembic.autogenerate.types
setup plugin alembic.autogenerate.constraints
setup plugin alembic.autogenerate.defaults
setup plugin alembic.autogenerate.comments
setup plugin alembic.ext.checkconstraint_byname
Using database: sqlite+aiosqlite:////Users/judegomila/.cache/uv/archive-v0/Zc-zBsYgUxmmVznI/lib/python3.13/site-packages/cognee/.cognee_system/databases/cognee_db
Context impl SQLiteImpl.
Will assume non-transactional DDL.
Relational migrations applied (target head).
2026-09-05T00:47:04.484187 [info ] Database migrations done. [cognee.shared.logging_utils]
2026-09-05T00:47:04.484315 [info ] Running MCP server with stdio [cognee.shared.logging_utils]
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"experimental":{},"prompts":{"listChanged":false},"resources":{"subscribe":false,"listChanged":false},"tools":{"listChanged":false}},"serverInfo":{"name":"Cognee","version":"1.29.1"}}}
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
5 of 15 testable claims verified · 0 contradicted → integrity 33/100
20 distinct capability claims found in Cognee’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
5
Verified
10
Unverified
0
Contradicted
23
Undersold
Verified (6)
“The .remember operation ingests text, files, or URLs in one call, auto-chunking, extracting entities, and building a knowledge graph”
Add memories from conversations and retrieve them later with semantic search, so context persists across sessionsfullproof ↗
“.recall is the main retrieval entry point, searching memory via the best available source for the request”
Add memories from conversations and retrieve them later with semantic search, so context persists across sessionsfullproof ↗
“The cognee-cli tool lets you remember data, enrich memory, and query — all from the terminal without writing Python”
“An optional RDF/OWL ontology file can be supplied to align extracted entities and types to canonical domain concepts”
Customize the memory schema — entity types, edge types, or ontology — to match my domainpartialproof ↗
“cognee.start_ui() runs the full UI and pipelines locally, for free, with no account required”
“An official Cognee MCP server brings persistent AI memory into MCP-compatible tools like Claude, Cursor, Cline, Continue, and Codex”
Unverified (14)
“The .remember operation ingests text, files, or URLs in one call, auto-chunking, extracting entities, and building a knowledge graph”
Ingest documents, JSON, and business data into memory — not just chat transcriptsfullproof ↗
“remember() can write directly into a per-session cache for fast short-term retrieval during a conversation”
Get summaries of past sessions or threads so an agent can pick up where the last conversation left offpartialproof ↗
“A session, keyed by (user_id, session_id), stores an ordered list of recent interactions as short-term memory”
Get summaries of past sessions or threads so an agent can pick up where the last conversation left offpartialproof ↗
“When no search type is given, recall() automatically classifies the query and picks the best retrieval strategy”
Steer retrieval with metadata filters, keyword/hybrid search modes, or reranking instead of accepting a single fixed similarity searchpartialproof ↗
“.improve enriches an existing knowledge graph after data has already been ingested”
Rely on the memory layer to update, supersede, or merge memories when new information contradicts what was storedpartialproof ↗
“improve() can be run at the end of a session to bridge short-term session memory into permanent long-term memory”
Get summaries of past sessions or threads so an agent can pick up where the last conversation left offpartialproof ↗
“.forget is the unified deletion command, supporting single-item, whole-dataset, or full user-scope cleanup deletion”
Delete a user's memories on demand — single memory, per-entity, or full erasure — to satisfy privacy requirementsfullproof ↗
“cognee-cli report generates a Graph Insight Report summarizing what a dataset's knowledge graph contains”
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
“Cognee can be run as a single Docker container for local development, testing, or custom deployment”
Self-host the memory layer from open-source code (e.g. via Docker) on infrastructure I controlfullproof ↗
“Dataset-scoped permissions and per-dataset storage give multi-user/org data isolation and access control on one instance”
Scope memories per user, agent, or application so one tenant's memories never leak into another's retrievalpartialproof ↗
“Dataset-scoped permissions and per-dataset storage give multi-user/org data isolation and access control on one instance”
Govern who and what can read or write memory with roles, policies, or access-control lists, and audit that accesspartialproof ↗
“Cognee is open source and can run the full memory engine locally or on your own infrastructure for free, forever”
Self-host the memory layer from open-source code (e.g. via Docker) on infrastructure I controlfullproof ↗
“Cognee is open source and can run the full memory engine locally or on your own infrastructure for free, forever”
Read the product's source under an open licensepartialproof ↗
“Cognee connects to Slack, Notion, Linear, and Google Drive to bring company data sources into agent-accessible memory”
Ingest documents, JSON, and business data into memory — not just chat transcriptsfullproof ↗
Undersold (23)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandsfullproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Run the memory layer fully locally — embedded in-process or against local models — without any cloud dependencypartialproof ↗
Store memories as a knowledge graph of entities and relationships so multi-hop and entity-centric questions are answerablefullproof ↗
My agent can manage its own memory mid-conversation — adding, searching, updating, and deleting memories through tools or API calls it invokes itselffullproof ↗
The memory layer decides for itself what is worth remembering — extracting salient facts from raw conversation and consolidating them in the backgroundpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
See published pricing with a free tier and per-unit rates so I can project memory costs before committingpartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Prevent my data from being used to train AI modelspartialproof ↗
Connect off-the-shelf assistants (Claude, ChatGPT, Cursor) to the same memory so every tool I use shares what it knows about mepartialproof ↗
Build against official SDKs in at least Python and TypeScript with equivalent memory APIspartialproof ↗
Retrieve a token-budgeted, prompt-ready context block assembled from relevant memories in one callpartialproof ↗
Store images, PDFs, or other files as memory inputs and recall information from them laterpartialproof ↗
Share selected memory across multiple agents or users (team or group memory) while keeping private memory privatepartialproof ↗
Claims outside our story set (3)
Real capability claims found in Cognee’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“cognee-cli push uploads a local dataset's knowledge graph to Cognee Cloud”
source ↗“The browser UI lets you upload data, explore knowledge graphs, run searches, and manage datasets”
source ↗“Cognee can index code repositories into memory”
source ↗
Business model
Apache-2.0 open-source core you can run anywhere; Cognee Cloud offers a free developer tier then usage-priced managed plans and custom enterprise deployments.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)
