Compare/Memory APIs
ContxOS vs Zep: Temporal Knowledge Graph or Project Knowledge Base?
Zep builds temporal context graphs for enterprise agents and shipped a Memory MCP server in August 2026. ContxOS keeps typed decisions, handoffs and workflows. Side by side.
Jose R. Gonzalez, CPA · Founder of ContxOS
Updated · 2 min read
In short
Zep turns conversations and business data into a temporal knowledge graph, in which facts carry validity windows and are invalidated rather than deleted. Since August 2026 its Memory MCP server gives Claude, ChatGPT, Cursor and SDK agents one shared, policy-governed memory. ContxOS works one level up, at the level of the work: decisions with rationale, handoffs between sessions, and workflows with tracked runs. Zep fits enterprise context infrastructure. ContxOS fits teams whose agents run projects.
Side by side
| Capability | ContxOS | Zep |
|---|---|---|
| What it is | A hosted knowledge base that AI agents read and write while they work on your projects. | A context layer for enterprise agents, built on temporal context graphs (open-source engine: Graphiti). |
| Where it works | Any MCP client with OAuth sign-in (Claude.ai, Claude Code and others). One memory, shared by every connected agent. | Memory MCP server (GA Aug 2026) for Claude, Cowork, ChatGPT, Cursor, plus SDK agents. |
| How memory is written | Deliberately: when a session closes, in a handoff, when you say "record this", or as a workflow step. No transcript ingestion. | Automatically, from conversations and ingested data, as graph facts. |
| Structure | Typed entries (decision, result, plan, TODO, bug, finding, note…) joined by typed links (supersedes, resolves, implements, supports, refutes…), each with an authority level. | Entities and fact triplets in a graph, with source-episode traceability. |
| Keeping memory current | Every search result shows its date and whether it is superseded (with a pointer to the replacement), expired or in conflict. Weak matches are labeled low confidence. | Bi-temporal validity windows; old facts invalidated, not deleted. |
| Session handoffs | Structured handoffs (accomplishments, pending work by priority, blockers by severity, decisions). "resume" restores one in a single step. | Not documented. |
| Procedures | Workflows (stages, steps, per-client variants). Runs track position, verified facts and holds outside the chat, and proven steps can go to subagents. | Agent Skills for Agent Memory accounts (Sep 2026). |
| Separation and governance | Projects, optional buckets within a project, per-project members, seats. | Per-user graphs plus shared organization graphs gated by user-group policy. Audited configuration. |
| Self-host | Hosted only. | Graphiti is open source. The Zep platform is cloud or BYOC. |
| Price | Free plan with one project and one seat. Paid plans add projects and seats (see contxos.com/pricing). | Free (2 projects, 1 MCP seat); Flex $125; Flex Plus $375; Enterprise custom. |
Competitor details come from their own documentation as of September 29, 2026 (see Sources). Products change quickly; tell us if something here is out of date.
Two kinds of "temporal"
Zep’s graph knows when a fact was true. Its validity windows are precise and automatic, which is ideal when agents need the current state of a customer, an account or a system.
ContxOS knows why knowledge changed. A decision supersedes another by an explicit link, made in a named session, often with a stated reason. That precision matters for project work, where the reason behind a change is often what the next agent needs most.
Which one fits
ContxOS fits when
- You want a light setup: connect, sign in, and your agents share a record today.
- You care about decisions, handoffs and procedures more than entity facts.
Zep fits when
- You need enterprise context infrastructure over many data sources, with group policies, BYOC or HIPAA.
- You want to self-host the graph engine (Graphiti).
Sources
- Zep documentation — Zep
- Agent memory over MCP — Zep, August 19, 2026
- Memory MCP server — Zep
- Zep changelog — Zep
- Graphiti on GitHub — GitHub
- Pricing — Zep
Frequently asked questions
Is ContxOS a knowledge graph?
ContxOS entries are linked by typed relationships, so you can traverse them like a graph, but you work with them as records (decisions, results, workflows) rather than as triplets.
Give your agent a memory that lasts
Connect ContxOS to Claude in about a minute. The free plan includes one project.
Product names belong to their owners. ContxOS is not affiliated with the companies named here.