Graphiti: what it remembers, who owns it, and what it costs
thecontinuitylayer.com/memory-systems/graphitiAn open-source framework for building real-time temporal knowledge graphs for agents; the engine inside Zep, run on your own graph database.
- 1Yes
Is Graphiti open source?
Yes, by Zep's own page.
The repository is licensed Apache-2.0.
Yes means: The core is under an open-source license.
- 2Yes
Can you run Graphiti yourself?
Yes, by Zep's own page.
Self-hosted only: you supply the graph database, the model and the embedder.
Yes means: It runs on your own machine or server.
- 3Yes
Can you take your memory out of Graphiti?
Yes, by Zep's own page.
Data lives in a graph database you run: Neo4j, FalkorDB or Amazon Neptune.
Yes means: An export, or the data sits in a standard store you own.
- 4Yes
Does Graphiti work with more than one model provider?
Yes, by Zep's own page.
Defaults to OpenAI, with Anthropic, Gemini and Groq supported, plus OpenAI-compatible endpoints such as Ollama and Azure OpenAI.
Yes means: It is not tied to one provider's models.
- 5Partly
Is there a hosted Graphiti?
Partly, by Zep's own page.
There is no hosted Graphiti; the README points to Zep as the managed service built on it.
Yes means: A cloud or managed option exists.
- 6Not stated
Does Graphiti have a free tier, and what is the entry price?
Zep's pages do not say.
No pricing page: an open-source library where you pay your own model and database costs.
Yes means: A free tier exists and the entry paid price is published.
- 7Not stated
Does Graphiti scope memory per user and per session?
Zep's pages do not say.
The README and welcome page do not describe per-user or per-session scoping.
Yes means: Both per-user and per-session or per-agent memory are supported.
- 8Not stated
Can you delete a user's memories from Graphiti?
Zep's pages do not say.
Zep's deletion page covers Zep Cloud only and says it does not document deletion in Graphiti.
Yes means: A documented way to delete everything for one user.
What these grades say about continuity, and what they do not.
Every grade on this site is read from the maker's own pages. The Continuity Framework asks five things of any system that carries state: that it carry, govern, evolve, prove and forget. These tests reach carry, govern and forget; they do not reach evolve or prove, which no maker's page documents in a gradeable way. A high letter is a good memory system, not a continuity layer.
- M1 Open sourceCarry
- Open source means the memory engine can outlive the vendor; the state is not hostage to a contract.
- M2 Self-hostCarry
- Self-hosting puts the store under the owner's control, which is the precondition for every other obligation.
- M3 ExportCarry
- An export is question C3: can the state leave in a form another system reads? A standard store you own answers it; a proprietary dump only partly.
- M4 Any modelCarry
- Working with more than one model provider is question C2: the memory, not the model, holds the state.
- M7 ScopingGovern
- Scoping per user, agent and session is question G2: who may read and write each item. It is the floor of governance, not the ceiling.
- M8 DeleteForget
- A documented delete for one user is rung 5 of the erasure ladder: the record leaves the store. Derived memories, the index and backups are not covered unless the maker says so. Rung 5 of the erasure ladder: delete the record.
License as stated: Apache-2.0. Every grade above is read from Zep's own page on the day shown. If a page has changed, tell us.