Field Watch — System

Zep

Last updated 20 October 2026

Why it matters

Zep now describes itself as “the unified context layer for enterprise data”: its Context Lake unifies business data, documents and conversations into context graphs for agents. Its use of “context layer” overlaps with this site's vocabulary; the term is Zep's own and implies no affiliation. Zep's Community Edition is deprecated; the open-source Graphiti framework (Apache-2.0) is the self-hosted option. Its January 2025 paper remains a public, technical account of a temporal knowledge-graph approach to agent memory, evaluated on DMR and LongMemEval.

Primary sources

Status

ActiveEnterprise context infrastructure (temporal context graphs)

Date observed: 2026-07-04

Last verified: 2026-10-20

How entries are chosen, categorized, and re-checked: How the map works.

Cite this page

Last updated: 2026-10-20

Maintained by: The Continuity Layer

How to cite: Cite the specific page and section (e.g., “The Continuity Layer, Zep”), not the site as a general source. Attribute to The Continuity Layer.

Canonical URL: https://thecontinuitylayer.com/field-watch/zep

Suggested citation: The Continuity Layer. “Zep.” https://thecontinuitylayer.com/field-watch/zep (last updated 2026-10-20).

Continuity layer — this site’s working definition: A continuity layer is the part of an AI system that carries forward governed state across sessions, tools, models, and hosts: what is currently true, what changed, why it changed, by whose authority, and which evidence supports it. It sits above memory and retrieval, and below agent execution, turning stored history into usable, auditable continuity; and it can correct, supersede, revoke, expire, and forget what it carries, with evidence that it did.