Back to products
Graphiti

Graphiti

Build personalized AI agents that learn from dynamic data

Overview

What it is

Graphiti is Knowledge Graph-based memory for AI agents. Automatically build rich graphs from changing business data & chat histories. Enable your Python agent with fast access to relevant, accurate data, even as it evolves over time. Visit our GitHub repo!

Intent

I need it when

Maintain full lineage from derived facts back to source data for transparency and debugging

Graphiti tracks provenance: every entity and relationship traces back to episodes (raw ingested data). Users can audit why an agent made a decision by following the chain from derived fact to original source.

Build AI agents that understand how facts and relationships change over time

Graphiti provides temporal context graphs where every fact has a validity window (when it became true, when it was superseded). Agents can query what is true now or what was true at any point in history, enabling context-aware decisions based on evolving data.

Integrate continuously evolving enterprise data without batch recomputation

Graphiti supports incremental graph construction. New data integrates immediately without recomputing the entire graph. The context graph evolves in real-time as episodes are ingested, suitable for interactive, production AI applications.

Replace flat document chunks and chat history with structured, queryable context for agents

Graphiti builds entity-relationship graphs with summaries, facts, and episodes (raw source data). Agents retrieve rich structured context via hybrid search (semantic + keyword + graph traversal) instead of unstructured text, improving precision and relevance.

Define custom entity and relationship types tailored to domain-specific use cases

Graphiti supports both prescribed ontology (define types upfront via Pydantic models) and learned ontology (let structure emerge from data). Developers can start simple and evolve as patterns appear, avoiding rigid one-size-fits-all schemas.

Drop

Not a fit when

  • User needs a fully managed, enterprise-grade platform with SLAs and 24/7 support—Graphiti is self-hosted only; use Zep instead
  • User requires sub-200ms latency at scale without custom implementation—Graphiti requires custom setup; Zep provides pre-configured production-ready retrieval
  • User wants a static knowledge graph without temporal tracking—Graphiti is designed for evolving, time-aware context; traditional static KGs are better suited
  • User cannot operate Neo4j, FalkorDB, Kuzu, or Amazon Neptune—Graphiti requires one of these graph databases; no alternative backends available
  • User needs LLM services without Structured Output support—Graphiti works best with OpenAI or Gemini; other providers may cause ingestion failures
Commercials

Pricing

Open-source (free); commercial managed service (Zep) available separately