Graphiti is Zep’s concrete open-source implementation for building and querying temporal context graphs. The framework continuously processes new episodes, manages temporal validity and provenance, and combines semantic, textual, and graph-based search for dynamic knowledge and agent contexts.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Graphiti is an open-source Python library for building temporally aware knowledge graphs from unstructured and structured information.
Graphiti emerged at Zep from the need to manage continuously arriving facts and temporal changes in a knowledge graph for AI applications. The project was released as open source and targets context-rich, updateable memory for agents.
Episodes from text, messages, or JSON are decomposed into entities, relationships, and time points. A graph backend stores these elements; retrieval combines semantic similarity, keywords, and graph structure, while new episodes extend or supersede existing statements over time.
New textual or structured data enters the graph as time-bound events.
Validity and observation times distinguish older from current statements.
Semantic, textual, and graph search returns relevant context.
Graphiti supports agents that need to remember changing facts and relationships. Extraction errors, conflicting statements, and privacy require provenance, update rules, and oversight.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.