Hindsight (Vectorize) vs Zep & Graphiti
Hindsight (Vectorize) vs Zep & Graphiti: side-by-side comparison of two dedicated memory layers systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.
Cost & capability
| Hindsight (Vectorize) | Zep & Graphiti | |
|---|---|---|
| Capability band | competent | competent |
| Capability composite | 68 | 68 |
| Cost tier | free | free |
| $/Mtok input | 0 | 0 |
| $/Mtok output | 0 | 0 |
| Use cases | Long Running Session, Memory Augmented Chat, Offline Capable | Long Running Session, Memory Augmented Chat, Multi Agent Coordination, Analytical Summarization |
Where they differ (14)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| Hindsight (Vectorize) | Zep & Graphiti | |
|---|---|---|
| Use cases | Long Running Session, Memory Augmented Chat, Offline Capable | Long Running Session, Memory Augmented Chat, Multi Agent Coordination, Analytical Summarization |
| Type | Vector + reflection / summarisation | Bi-temporal knowledge graph |
| Created | 2025-10 | 2024-08 |
| Latest release | v0.6.0 2026-05-05 | v0.29.0 2026-04-27 |
| License | MIT | Apache-2.0 |
| GitHub | 12.3k★ +121/mo Python | 25.7k★ +137/mo Python |
| Funding | $4M total Seed · 2024-10 | $3M total Seed (additional) · 2024-04 |
| Backend storage | custom | Postgres + Neo4j (Graphiti) |
| Deployment | Both | Managed-only |
| API surface | REST, SDK: Python, TS | REST, SDK: Python, JS/TS, Go |
| Multi-tenancy | namespace | Logical namespace per user/session; AWS VPC self-hosted option for full data residency; HIPAA BAA on Enterprise plan |
| MCP | native (first-party) — Hindsight MCP | native (first-party) — Graphiti MCP server |
| Optimised for | retrieval engineering + reflection / summarisation as service | memory operation tracing + drift / poisoning detection |
| Anti-fit | searched not found | not for use cases that don't run agent workloads in production |
At a glance
| Hindsight (Vectorize) | Zep & Graphiti | |
|---|---|---|
| Section | Dedicated memory layers | Dedicated memory layers |
| Tier | T1 | T1 |
| Type | Vector + reflection / summarisation | Bi-temporal knowledge graph |
| Created | 2025-10 | 2024-08 |
| Latest release | v0.6.0 2026-05-05 | v0.29.0 2026-04-27 |
| License | MIT | Apache-2.0 |
| GitHub | 12.3k★ +121/mo Python | 25.7k★ +137/mo Python |
| Pricing | Free + paid | Free + paid |
| Funding | $4M total Seed · 2024-10 | $3M total Seed (additional) · 2024-04 |
| Backend storage | custom | Postgres + Neo4j (Graphiti) |
| Deployment | Both | Managed-only |
| API surface | REST, SDK: Python, TS | REST, SDK: Python, JS/TS, Go |
| Embedding | multiple supported | multiple supported |
| Multi-tenancy | namespace | Logical namespace per user/session; AWS VPC self-hosted option for full data residency; HIPAA BAA on Enterprise plan |
| MCP | native (first-party) — Hindsight MCP | native (first-party) — Graphiti MCP server |
| A2A | not documented publicly | not documented publicly |
| OpenTelemetry | not documented publicly | not documented publicly |
| Optimised for | retrieval engineering + reflection / summarisation as service | memory operation tracing + drift / poisoning detection |
| Anti-fit | searched not found | not for use cases that don't run agent workloads in production |
Taxonomy
| Axis | Hindsight (Vectorize) | Zep & Graphiti |
|---|---|---|
| storage | vector | graph |
| retrieval | similarity | graph-traversal |
| persistence | long-term | long-term |
| update | consolidation | append-only |
| unit | episode | episode |
| governance | opaque | auditable |
| conflict | none | bi-temporal |
Pros & cons
Hindsight (Vectorize)
Pros: Built on Vectorize's RAG pipeline expertise — retrieval tuning is a first-class concern; strong Pydantic-AI integration story.
Cons: Newer entrant with smaller adoption; positioning straddles RAG and memory which can muddy the value prop vs pure-play layers.
Zep & Graphiti
Pros: Bi-temporal graph captures event time + ingestion time, making contradiction tracking and chronological reasoning correct by construction.
Cons: KG storage is heavier than vector for the same data volume; smaller funding base than Mem0 ($2.3M vs $24M).