Zep

Zep assembles the context an agent needs before it acts. You send business records, documents and conversations in, and it builds a graph for each user, customer, account or domain, dates the facts inside it and updates them as the sources change; retrieval then returns only what a given task depends on, filtered by policy. The vendor calls the aggregate a context lake and says it runs on a graph database service of its own. Around this sit access and retention policies enforced in the data layer, tracing from each fact back to the message it came from, and a query log kept for audit. The graph engine underneath is a separate open-source framework with its own versioned documentation and an interface for connecting assistants to it.

It suits enterprises that want one governed body of context shared by many agents rather than each agent keeping its own notes, and it suits cases where facts go out of date and a stale answer is worse than no answer. Deployment is offered as a hosted service, as a hosted service where you hold the encryption keys, or inside your own network, with the usual compliance attestations named. It suits less well a small project that just needs to remember a conversation or two, where a simpler store and a shorter bill would do, and it suits less well anyone who wants to run the graph stack without the platform around it — that is a different product, and you should read its documentation rather than this one.

Not verified: no context was ingested and no query was made, so the quality of the graph, the effect of policy filtering and the accuracy of the retrieval were not tested. Figures on the page — the promised reduction in token use, the claim that retrieval stays under a stated time regardless of graph size, and the counts in the vendor's own dashboard illustration showing active graphs and facts — are the vendor's own numbers or mock-up data, not measurements taken here. The pricing page was not opened, so tiers and prices are unknown. The compliance attestations and the deployment options are statements on the vendor's own enterprise page, and the open-source framework's repository was read only through the hosting service's interface, which reported about 31,654 stars, the Apache-2.0 licence and a push on 11 October 2026; its documentation was read only as far as its introduction.