Graphicle vs Graphiti: coding-agent memory in one SQLite file.
Graphiti, from Zep, builds temporal knowledge graphs for agent memory in a graph database. Graphicle adapts parts of it and keeps a repository's memory and code graph in one SQLite file.
Checked against Graphiti's own pages on 27 October 2026
Graphiti and Graphicle.
Graphiti, from Zep, is an open-source framework for temporal knowledge graphs of agent memory, in a graph database you bring. Zep runs it managed, or in your own cloud.
| Graphiti | Graphicle | |
|---|---|---|
| Built for | Agent memory as a temporal graph | Coding agents |
| Storage | Neo4j, FalkorDB, Amazon Neptune or FalkorDB Lite | One SQLite file |
| Code graph | Not in its README | Built in |
| Model needed | Yes; OpenAI's by default | Only to propose memories; local models work |
| Licence | Apache-2.0 | Apache-2.0 |
What we measured.
- 87.66 vs 46.49LoCoMo-10, against graphiti-core 0.30.2Graphicle ahead
- 67.32 vs 39.43BEAM-100K, mean rubric scoreGraphicle ahead
- 12 vs 1,363estimated model calls per conversation while ingesting LoCoMo-10
A pre-release comparison with seven memory systems: development sets; one open model as every system's reader, judge and model; a pre-release build of Graphicle, not its released defaults. These scores cannot be set against any vendor's published numbers, and the call counts per conversation are estimates. graphiti-core is the open-source library, not Zep's hosted service; Graphiti was not run on LME-84 because of its cost.
Which one fits.
Choose Graphiti if
- You are building a product around a temporal knowledge graph.
- You want it managed by Zep.
Choose Graphicle if
- You want coding-agent memory in one file, next to the code graph.
- You want memories to wait for your approval.
Graphicle's memory library adapts parts of Graphiti (Apache-2.0): its rank fusion and the time intervals of contradicted facts, credited in NOTICE.
Checked on 27 October 2026. Product names are trademarks of their owners; no affiliation or endorsement is implied.