StackMap
Subscribe

cortexdb alternatives

Curated alternatives to cortexdb — and why you'd switch.

engrim

Local SQLite episodic memory shared across Antigravity, Claude Code, Cursor, Windsurf and Codex: hooks/MCP capture decisions, FTS5+model2vec hybrid recall reloads ~1k tokens per session.

Why switchBoth are local SQLite memory shared across coding agents via hooks. Engrim stores episodes; CortexDB adds a typed knowledge graph with ontology constraints.
Full comparison →
agent-memory

Neo4j Labs' graph-native agent memory: conversations, a POLE+O entity knowledge graph and reasoning traces in one store, with a 16-tool MCP server and hosted or self-hosted backends.

Why switchBoth are graph-native agent memory with entities and reasoning traces. Neo4j Labs needs a Neo4j server; CortexDB is one SQLite file.
Full comparison →
latticedb

Embedded single-file graph database in Zig: graph traversal, HNSW vector search and BM25 full-text in one query language, plus a durable event log — built for Graph RAG and local agent memory.

Why switchBoth are embedded single-file graph stores agents can use as memory. latticedb is a general graph DB with vector search; CortexDB is a memory API with ontology rules.
Full comparison →
graphicle

One Rust program giving coding agents a code graph plus memory of docs, decisions and past sessions, served over MCP to Claude Code, Codex, Cursor and VS Code.

Why switchBoth are local, single-install memory for coding agents with structured recall. Graphicle ties memory to a code graph; CortexDB to a typed knowledge graph in SQLite.
Full comparison →