What Zep is
Zep provides agent memory on a temporal knowledge graph (Graphiti). Reasons to evaluate alternatives include wanting a simpler recall-oriented API, different scoping primitives, or a different deployment model.
What Auld is
Auld is a memory service. Your systems send time-stamped records; Auld extracts memories, reconciles changes into current state with history, and returns cited memories scoped to the viewer, over REST or MCP.
What to test in any alternative
- Validity: can you ask what was true at a given time, and get the source?
- Scope: can you express team-, customer- and matter-level visibility per record?
- Operations: who runs the graph database, backups and upgrades?
- Schema: do you need to design entity types, or is a default enough?
- Cost model: what is metered — ingestion, recall, storage, seats?
How Auld approaches each
| Requirement | Auld design |
|---|---|
| Data model | Records → memories with validity; entities and relationships |
| Schema | Default; customizable on Enterprise |
| Scope | Identities, audiences, visibility |
| Metering | Ingested bytes; recall unmetered on Flex and Enterprise |
| Deployment | Managed or own cloud |
Evaluate and verify
Trade-offs depend on your data. Run the same test set against each option — the methodology page has a checklist — and confirm current capabilities in the official documentation.
Sources: Zep website · Graphiti on GitHub