HyperMemory vs Zep
Both give AI agents long-term memory. The difference is how they structure it — and what happens when you grow.
| Aspect | HyperMemory | Zep |
|---|---|---|
| Architecture | Hypergraph (multi-way relationships) | Temporal Knowledge Graph (binary edges) |
| Pricing Model | Nodes + Queries (transparent) | Credits / Episodes (opaque) |
| Free Tier | 1,000 nodes, 10,000 queries | 1,000 credits |
| Entry Paid Tier | $29/mo (50K nodes, 100K queries) | $25/mo (20K credits) |
| Mid Tier | $99/mo (unlimited nodes, 1M queries) | $475/mo (300K credits) |
| Price Jump | 3.4x ($29 → $99) | 19x ($25 → $475) |
| Storage Fees | None | None |
| Overage Pricing | $0.50/1K queries (smooth) | Must upgrade tier (cliff) |
| Relationship Model | Hyperedges (3+ nodes per relationship) | Binary edges (A → B only) |
| MCP Support | Native (built for MCP) | Available (add-on) |
| Billing Unit | Nodes and queries (intuitive) | Episodes / credits (variable) |
| Large Data Penalty | None — a node is a node | Episodes >350 bytes billed as multiples |
| Credit Rollover | N/A (no credits) | 60-day rollover |
| Enterprise | Custom pricing | Custom pricing |
| SSO/SAML | Enterprise tier | Enterprise tier |
What happens when you grow
Zep's pricing has a cliff. HyperMemory's doesn't.
| Monthly Usage | Zep Cost | HyperMemory Cost | Difference |
|---|---|---|---|
| 20K operations | $25 | $29 | Zep is $4 cheaper |
| 30K operations | $475 (must upgrade) | $29 + overage ≈ $34 | Save $441 |
| 50K operations | $475 | $29 + overage ≈ $44 | Save $431 |
| 100K operations | $475 | $99 | Save $376 |
| 300K operations | $475 | $99 + overage ≈ $159 | Save $316 |
Binary edges vs. hyperedges
Zep uses a Temporal Knowledge Graph — a powerful upgrade over pure vector search, and a legitimate approach to structured memory. But its relationships are binary: A connects to B, and that's it.
HyperMemory uses a hypergraph. A single relationship can connect three, four, or more concepts simultaneously. When your agent remembers that "Sarah, Marcus, and the API v2 project were all part of the Q3 planning decision" — that's one hyperedge, not six separate binary edges.
This matters because real knowledge is rarely just two things connected. Decisions involve multiple people. Projects span multiple teams. Context is multi-dimensional. Hyperedges capture that naturally.
Honest guidance
Choose Zep if:
- You're already deeply integrated with Zep's ecosystem
- Your usage stays comfortably under 20K episodes/month
- You need Zep's specific GraphRAG capabilities
- You're on an enterprise plan with negotiated pricing
Choose HyperMemory if:
- You're outgrowing entry-tier limits and can't justify a 19x price jump
- You need multi-way relationships (hyperedges), not just binary connections
- You want MCP-native integration with no adapters
- You want transparent, predictable pricing that scales with usage
- You value simple billing units (nodes and queries, not credits and episodes)
Competitor pricing last verified: 2026-03-01