RunLocalAI
server
Open source
free (OSS Community) + Zep cloud

Zep (memory platform)

Long-term memory platform for AI agents. Sits above Graphiti as the application layer — sessions, facts, summaries, vector + graph hybrid retrieval. The 'memory backend you don't have to build' choice.

By Fredoline Eruo·Last verified May 6, 2026·4,000 GitHub stars

Overview

Long-term memory platform for AI agents. Sits above Graphiti as the application layer — sessions, facts, summaries, vector + graph hybrid retrieval. The 'memory backend you don't have to build' choice.

Stack & relationships

How Zep (memory platform) relates to other entries in the catalog — recommended pairings, alternatives, dependencies, and edges to avoid. Each edge carries a one-line operator note from our editorial team.

Zep (memory platform) ↔ ecosystem

Recommended stack

  • Pairs with
    OpenHands

    Zep memory provider integration is cleaner on OpenHands than on Goose or Aider. Picks up agent decisions across sessions automatically.

Alternatives

  • Competes with
    Mem0 (agent memory API)

    Mem0 emphasises drop-in API; Zep emphasises temporal knowledge-graph memory. Different mental models — pick by whether you want graph traversal or vector retrieval.

  • Competes with
    Letta (memory framework)

    Both target long-horizon agent memory. Letta is explicit memory hierarchy; Zep is temporal knowledge graph. Different mental models — pick by whether memory state is something you want to inspect or something you want to query.

  • Competes with
    Graphiti (Zep)

    Both store memory as temporal knowledge graphs. Zep is a hosted product with a strong API; Graphiti is OSS with deeper Neo4j integration. Pick Zep for fast wiring; Graphiti for full local control.

  • Alternative to
    Mem0 (agent memory API)

    Zep's temporal-graph approach handles 'what did Bob decide three sessions ago and why' better than Mem0's flat vector retrieval. Trade slower lookup for stronger multi-hop reasoning.

  • Alternative to
    Graphiti (Zep)

    OSS counterpart to Zep with similar temporal-graph design. Pick Graphiti when full local control + Neo4j integration matters; pick Zep when you want managed infra.

  • Alternative to
    MCP Memory Server

    MCP Memory is graph-shaped but simple; Zep is graph-shaped and sophisticated. The architectural difference shows up at scale — MCP Memory wobbles past a few thousand entities; Zep doesn't.

Pros

  • Drop-in API for sessions + facts
  • Graph + vector hybrid retrieval
  • OSS self-hostable

Cons

  • Coupled to specific Postgres + graph deps
  • Cloud version is the actively-maintained path

Compatibility

Operating systems
macOS
Linux
Docker
GPU backends
n/a
LicenseOpen source · free (OSS Community) + Zep cloud

Get Zep (memory platform)

Official site
https://www.getzep.com
GitHub
https://github.com/getzep/zep

Frequently asked

Is Zep (memory platform) free?

Zep (memory platform) has a paid tier (free (OSS Community) + Zep cloud). Check the pricing page for current terms.

What operating systems does Zep (memory platform) support?

Zep (memory platform) supports macOS, Linux, Docker.

Which GPUs work with Zep (memory platform)?

Zep (memory platform) supports n/a. CPU-only inference is also possible but slow.

Reviewed by RunLocalAI Editorial. See our editorial policy for how we evaluate tools.