EN
Back to the archive

The archive · AI & Models · Product decision · 2024–2026

Zep bets AI-agent memory is temporal, open-sources Graphiti; 30.6k stars

Zep open-sourced Graphiti in 2024 betting temporal knowledge graphs, not chunks, are agent memory; 30.6k GitHub stars by Sept 2026.

Zep

The betThat AI-agent memory is temporal: facts gain and lose validity, so agents need incrementally built knowledge graphs with provenance, not static RAG chunks.Live

What the business is

Zep is a context-infrastructure company for AI agents: it sells managed graph infrastructure (a proprietary Context Graph Engine built for millions of context graphs, sub-200ms retrieval, dashboards, Python/TypeScript/Go SDKs, SLAs) and maintains Graphiti, the open-source temporal-knowledge-graph framework at the core of that platform.

How it started

By September 2024 Zep was positioning Graphiti, launched via Show HN, as the fix for the weakness it saw in retrieval-augmented generation: RAG batch-processes and summarizes static document chunks, while agent memory is continuous — every interaction changes what is true. Graphiti instead gives every fact a validity window, invalidates superseded facts instead of deleting them, traces every edge back to the raw episode that produced it, and integrates new data incrementally without recomputing the graph.

What happened

Zep built Graphiti as the open-source core of a commercial stack: the managed Zep platform adds users, threads and message storage, a dashboard with graph visualization and API logs, enterprise SLAs, and a proprietary graph engine so production deployments need no third-party graph database. The repo grew support for Neo4j, FalkorDB, Amazon Neptune and Kuzu backends, OpenAI-compatible and local LLMs, an MCP server and a FastAPI service, and the team published the architecture paper 'Zep: A Temporal Knowledge Graph Architecture' (arXiv 2501.13956, January 2025). By the 2026-09-04 crawl Graphiti showed 965 commits and the README's hiring note showed Zep converting framework adoption into a commercial team.

How it ended up

Still running and scaling as of 2026-09-05: Graphiti sits at 30.6k stars and 3.1k forks while Zep sells the managed platform for production deployments; the material records no funding or revenue figures.

Background

Zep is an AI-agent infrastructure company whose bet is that agent memory is a temporal problem. Traditional RAG flattens documents into chunks and summaries, but what an agent needs to remember changes continuously: Kendra loved Adidas shoes in March 2026 and may not in June. Graphiti, the framework Zep open-sourced, treats every fact as having a validity window — when it became true and when it was superseded — keeps full provenance back to the raw episodes that produced it, and updates the graph incrementally as new data arrives.

Graphiti launched on Hacker News as a Show HN on 2024-09-04 (142 points, 21 comments). The pitch was deliberately anti-RAG: hybrid retrieval combining semantic embeddings, keyword search and graph traversal, no full-graph recomputation on ingest, prescribed or learned ontology, and sub-second historical queries. Zep positioned the framework as the open core of its own commercial platform, which manages context graphs at scale on a proprietary Context Graph Engine with sub-200ms retrieval, governance, dashboards and SDKs.

Adoption compounded through 2026: the GitHub repo reached 30.6k stars, 3.1k forks and 965 commits by the 2026-09-04 crawl, and the README's Zep-vs-Graphiti comparison shows the commercial mechanism — self-host the framework if you want flexibility, buy Zep if you want it operated. The January 2025 architecture paper formalized the design, and the repo's MCP server and FastAPI service kept the framework easy for agent developers to adopt.

What has to be true

  • Concrete traction: the 2024-09-04 Show HN drew 142 points and 21 comments, and the 2026-09-04 crawl recorded 30.6k stars, 3.1k forks and 173 watchers.
  • A sharp architectural bet: temporal validity and provenance replace static RAG chunks as the memory model for agents, which changes what infrastructure agent apps buy.
  • An open-core loop visible in one repository: the README gives away the framework and sells the managed Context Graph Engine, dashboards and SLAs.
  • The paper (arXiv 2501.13956) and MCP/REST surfaces show the team converting framework adoption into a hiring, enterprise product rather than a hobby.

What can be applied

When the data layer is the bet, open-source the framework and sell the managed engine: every developer building on Graphiti is a potential Zep production customer.

Aftermath

As of 2026-09-05 Zep is live and hiring: Graphiti recorded 30.6k stars, 3.1k forks, 173 watchers and 965 commits at the 2026-09-04 crawl, the README advertises open engineering and developer-relations roles at getzep.com/careers, and the platform page describes Zep as managed context-graph infrastructure for production agent deployments. The material contains no funding, revenue, customer-count or incorporation disclosures, so the commercial half of the bet is visible only through the framework's adoption and the careers page.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe what you are building, and see who is betting on the same thing.

Free account · 3 free questions · no card

Related cases