Runtime Governance Layer
Exogram + Zep
“Conversation history is not governed ledger.”
What Zep Does
- •Zep provides long-term ledger through conversation history management and automatic summarization.
- •Enriched context retrieval from past conversations.
- •Stores conversation threads — not governed facts. No encryption. No conflict detection.
What Exogram Does
- ▸Exogram stores governed facts — not conversation threads.
- ▸Every entry is verified, encrypted, conflict-checked, and attributed with full provenance.
- ▸Facts are different from conversations. Conversations are raw. Facts are verified.
Key Differences
| Dimension | Zep | Exogram |
|---|---|---|
| Storage Unit | Conversations | Verified facts |
| Verification | None | Conflict detection + constraint enforcement |
| Encryption | None | AES-256-GCM per-user |
The Verdict
Use Zep for chat history. Use Exogram when you need facts, not conversations.
Interception Latency Benchmark
Unlike standard LLM-based guardrails that invoke external APIs on every single tool execution, Exogram compiles policies to execute in-memory inside the client runtime.
Zep (LLM / API Check)~220.00 ms
Exogram Authority Runtime (In-Memory Intercept)0.07 ms
Is Zep vulnerable to execution drift?
Run a static analysis on your LLM pipeline below.
STATIC ANALYSIS
Frequently Asked Questions
What's the difference between storing conversations and storing facts?
Conversations are raw dialogue. Facts are extracted, verified, conflict-checked, and attributed claims. A conversation might contain "the sky is blue" and "the sky is green" — Exogram would detect the contradiction. Zep would store both.