Head to head · Memory store · October 2026 research run
Cognee vs Hindsight
Cognee has a score of 54.6 (C) against Hindsight's 50.4 (D). Both do memory store. The largest gap is reliability, 25 points.
Which one, for what
Pick Cognee for
- reliability (+25)
- schema & documentation (+17)
- payments & pricing (+5)
- transparency & trust (+19)
Pick Hindsight for
- security & auth (+19)
Score by category
| Category | Weight this run | Cognee | Hindsight | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 50 | 25 | Cognee +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 68 | Cognee +17 |
| Agent ergonomics | 13%16.2 | 59 | 57 | Cognee +2 |
| Security & auth | 14%17.5 | 39 | 58 | Hindsight +19 |
| Payments & pricing | 10%12.5 | 35 | 30 | Cognee +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 82 | 80 | Cognee +2 |
| Transparency & trust | 7%8.8 | 67 | 48 | Cognee +19 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 54.6 · C | 50.4 · D |
Facts side by side
| Fact | Cognee | Hindsight |
|---|---|---|
| Kind | Model platform | HTTP API |
| Vendor | Cognee | Vectorize |
| Hosted endpoint | https://<tenant>.aws.cognee.ai/api/v1 | https://api.hindsight.vectorize.io |
| Transports | HTTP, stdio, SSE (legacy) | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 7 | 27 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | not listed |
| Last release | 2026-09-29 | 2026-09-29 |
| Popularity | 31k stars, 21k PyPI/wk | 43k stars, 44k npm/wk, 227k PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
Verdicts
Cognee
Apache-2.0 library, REST server and MCP server, all self-hostable, with local models and no LLM key since 1.6.0. No status page, rate limits, SLA or SOC 2 for Cloud, and Cloud runs in AWS us-east-1 with no EU region.
Hindsight
API keys support bank-level restrictions, expiry and child-key revocation. Retain ingestion costs $10 per million tokens.
Before you call either
Cognee
- Use remember, recall and forget. The older cognify, search and delete MCP tools are gone
- Always include /api/v1 in REST paths
- Check cognify_status before querying data you added with background=true
- Never pass everything=true to forget unless you mean to wipe all of the user's memory
- Set a client timeout on Cloud calls and treat HTTP 402 as an empty balance, since an empty balance has also shown up as hangs
Hindsight
- Scope the MCP URL to one bank (/mcp/{bank}/) so every call lands in the right memory and three bank-admin tools drop out
- Use recall for lookups and keep reflect ($0.05 a call) for questions that need reasoning
- Pass
async: trueon large retains so the call returns before extraction finishes - Treat HTTP 402 as out of credit and 403 as a key that can't reach that bank
Other comparisons with Cognee or Hindsight
Machine-readable
/api/v1/tools/cognee.json·/api/v1/tools/hindsight.json- This page as Markdown,
/compare/cognee-vs-hindsight.md