Back to Gap Map Product / UX / Agent memory & context stores

Zep

Zep
closed / Overall score: 4.4(strong)

Zep is a hosted context and memory service for AI agents. It turns each user's messages, documents and business data into a temporal context graph and returns a prompt-ready context block for the next turn, with user and thread management, access policies, retention rules and connectors to company systems. Zep runs it in its own cloud or a customer's, built on its open Graphiti framework.

Scored as the hosted service. Graphiti, the open graph framework inside it, is a separate entry.

Openness

1 high confidence
1.0
license
Proprietary (Zep Cloud is used under Zep's terms of service, which forbid deriving its source)
source
closed (the Context Lake, graph construction service and Konig graph database run only as Zep's service; getzep/zep says it is "not Zep's product or service" and holds examples and integrations)
clients
Apache-2.0 (getzep/zep-python and getzep/zep-js publish the zep-cloud and @getzep/zep-cloud SDKs, clients of the hosted service)
deployment
Zep Cloud by default (own-key encryption and bring-your-own-cloud deployment in a customer VPC are Enterprise arrangements)
open-engine
Graphiti (the Apache-2.0 temporal graph framework inside Zep, scored as its own entry)

Zep runs as a hosted service, or inside a customer's cloud under an Enterprise agreement, and its service code is not published; its terms forbid deriving the source. What Zep publishes under Apache-2.0 is the SDKs that call the service, example code, and Graphiti, the graph framework inside Zep, which is listed separately. The self-hostable Zep Community Edition is no longer maintained.

Adoption

4 medium confidence
4.0

Adoption is counted as monthly downloads of Zep's own SDKs, zep-cloud on PyPI and @getzep/zep-cloud on npm, which exist only to call the hosted service. The Go SDK is not counted, and use of the open Graphiti framework is measured on its own entry.

Capability

5 medium confidence
5.0

Zep extracts facts from each user's messages and business data, merges duplicates, invalidates facts that newer information contradicts and returns a prompt-ready Context Block for the next turn. It runs on the same temporal graph design as Graphiti and adds per-user observations, summaries and retention policies as a hosted service.

  • https://help.getzep.com/v4/agent-memory-solution.md recorded 2026-11-20

    "A Zep user owns a user Context Graph. Threads group conversations for that user"; "thread.get_context" retrieves a Context Block for the next model request.

  • https://help.getzep.com/v4/context-retention.md recorded 2026-11-20

    Context is removed by a caller, by account deletion, or when "A retention policy deletes the context"; the page describes "how retention policies delete idle context".

  • https://help.getzep.com/v4/facts.md recorded 2026-11-20

    Each fact carries valid_at, invalid_at and expired_at timestamps, and Zep "attempts to invalidate" a fact that newer data contradicts.

  • https://help.getzep.com/v4/how-graph-creation-works.md recorded 2026-11-20

    An "LLM-driven pipeline" extracts entities and facts from each episode; when resolving facts, "duplicates merge, and contradictions invalidate older facts"; observations and thread summaries are derived over time.

Verified 2026-11-20, except some scores, still awaiting re-confirmation