Rift vs Zep
Zep builds graphs of dated facts from conversations and business data and serves them from Zep Cloud. Rift syncs files between machines.
Zep
Rift
What Zep is
Zep is a context service for agents. It takes chat messages, JSON and text, and builds a graph for each user, and shared graphs for context that no one user owns, in which every fact has dates and is marked invalid when newer data contradicts it. An agent gets the context relevant to its task in one call, and each fact can be traced to the source it came from. Enterprise plans add policies that limit which actions and which classes of data each API key can reach. Zep is a managed cloud service, and its graph framework, Graphiti, is open source.
How they differ
Zep stores facts and relationships that it extracts from what you send, in graphs on Zep Cloud, where its services decrypt the data to process it. Rift stores files as they were written and shares them one folder at a time with keys that the receiving machines hold.
Which to choose
Choose Zep when
- Agents need facts that change over time, with a record of when each was true.
- Several agents should draw on one body of business context.
- You need policies on what each agent can retrieve, and logs of its requests.
Choose Rift when
- The state is files, such as reports, datasets and video.
- The files have to be on the agent's own disk.
- A cloud should store the files and be unable to read them.
Using them together
An agent can keep facts in Zep and files in Rift.
Based on Zep's documentation, read in October 2026. Sources: concepts, agent access, bring your own key, support access, security, Zep and Graphiti.