The deciding difference is operational: Zep can run on infrastructure you control, Supermemory cannot. If that constraint is real for you, it settles the choice before anything else is considered.
Temporal knowledge graph memory — facts with validity windows, not just embeddings.
Memory graph plus automatic user profiles, with connectors that sync from Drive, Gmail, Notion and GitHub.
Closest thing here to memory and RAG in one product: the graph tracks contradictions and recency, and the connectors mean you are not writing an ingestion pipeline first.
| Zep | Supermemory | |
|---|---|---|
| Licence | Open source | Proprietary |
| Pricing | freemium | freemium |
| Self-hostable | Yes | No |
| Languages | Python, TypeScript | TypeScript, Python |
| Install | — | — |
| Keys required | ZEP_API_KEY | SUPERMEMORY_API_KEY |
The deciding difference is operational: Zep can run on infrastructure you control, Supermemory cannot. If that constraint is real for you, it settles the choice before anything else is considered. Zep: Temporal knowledge graph memory — facts with validity windows, not just embeddings. Supermemory: Memory graph plus automatic user profiles, with connectors that sync from Drive, Gmail, Notion and GitHub.
Zep can run on your own infrastructure. Supermemory is a hosted service only.
Zep is open source (freemium). Supermemory is proprietary (freemium).
Every page here answers to Accept: text/markdown and returns the same content at roughly a tenth the tokens. No separate site, no toggle — same URL.
curl -s -H "Accept: text/markdown" https://newagent.build/compare/zep-vs-supermemory