Our Mission
Versatile. Lean. Powerful.
NovaCortex is the memory system we needed for our own AI agents — and couldn't find. No lock-in, no forced cloud, no bloat. A system that fits any stack, saves tokens instead of burning them, and still delivers state-of-the-art retrieval.
Architecture
Engineered for Speed
Built for AI-agent workloads from day one — not retrofitted.
Token Intelligence
NovaCortex retrieves only what the agent needs right now — no full-context dumps. Salience decay model learns what to forget. Typical savings: 85–95% fewer input tokens.
Graph-Native Memory
Four typed memory kinds (Episodic, Semantic, Procedural, Working) stored in a force-directed relation graph. Not a flat vector store — a real knowledge graph.
PMF — Portable Memory Format
Open RFC-001 standard for vendor-neutral AI memory interchange. Export everything to a single PMF file, import into any compatible system. Merkle-verified. No lock-in.
Knowledge Buckets
Organize memories into named buckets with per-agent access control. Fine-grained isolation for multi-agent systems. Namespace federation across deployments.
MCP Built-In
Native Model Context Protocol server — zero configuration. Works with Claude Desktop, Cursor, Windsurf, and any MCP-compatible client out of the box.
Free Self-Hosting
docker compose up. Runs on any VPS, Unraid, Raspberry Pi, or bare metal. Full stack — API, web UI, vector DB, graph DB, cache — in one command.
Standard
Portable Memory Format (PMF)
PMF is NovaCortex's answer to the AI memory fragmentation problem. Every system stores memories differently. PMF defines an open, machine-readable format for AI memory snapshots — with schema validation, versioning, and compatibility across all major systems.
- Full export in a single file: memories, namespaces, relations, embeddings
- Import into any PMF-compatible system — no migration scripts
- RFC process open for community contributions
- Native Obsidian export: memories as a Markdown vault for Graphify integration
Efficiency
Stop the Token Bleeding
Context stuffing burns thousands of tokens on every request. NovaCortex delivers only what the agent needs right now — no full-context dumps.
Measured on a ~26K-token KB (gpt-4o-mini, top-5 retrieval) · reproducible — see the benchmark below
Benchmarks
Measured. Published. Reproducible.
LongMemEval_S: 500 questions, each against its own ~115K-token conversation history. We publish every raw per-question record, the judge prompt, and the harness — run it yourself.
| Question category | Cloud reader (gpt-4o) | Fully local (qwen3:8b) |
|---|---|---|
| Knowledge updates (fact changed over time) | 93.6% | 66.7% |
| Temporal reasoning (when / how long / order) | 81.2% | 72.2% |
| Single-session recall (user / assistant) | 97.1% / 89.3% | 84.3% / 87.5% |
| Multi-session aggregation | 72.2% | 42.9% |
Honest fine print: competitor numbers are self-reported (Zep 71.2 with a gpt-4o reader; mem0 reports 94.4 via a non-public evaluation framework — with the same reader class, gpt-5-mini, we measure 80.0 and publish the raw records). Our judge allows numeric/order equivalence — disclosed in the docs, worth ~1–2 points. The fully-local run keeps every byte on one 70W machine; only grading used a cloud model. Full methodology & raw data →
Retrieval beats dumping your KB
Same questions, same model. Dumping the whole knowledge base into context vs NovaCortex fetching only the top-5 relevant memories. Dump tokens grow with the KB; retrieval stays flat.
| KB size | Dump tokens | Retrieval tokens | Reduction |
|---|---|---|---|
| 42 facts (~2K) | 2,028 | 305 | 85% |
| 220 facts (~10K) | 10,157 | 305 | 97% |
| 560 facts (~26K) | 25,675 | 305 | 98.8% |
15 questions, gpt-4o-mini, top-5. Answer accuracy at parity (100% dump / 93% retrieval); retrieval recall@5 = 100% even with 518 unrelated distractor facts. Reproducible: node scripts/benchmark/run.mjs.
Comparison
Why NovaCortex?
The only self-hosted AI memory system with a full admin UI, graph memory, and an open portability standard.
| Feature | NovaCortex | Mem0 | Cognee | Supermemory |
|---|---|---|---|---|
| Free self-hosted (full) | ⚠ | ⚠ | ||
| Self-hosted admin UI | ||||
| Graph memory (self-hosted) | ||||
| Open source / auditable | ||||
| PMF open RFC standard | ||||
| MCP server built-in | ||||
| 4 typed memory kinds | ||||
| Salience decay model | partial | |||
| Token-efficient context | partial | |||
| Merkle-verified exports | ||||
| Namespace federation |
✓ Full support · ⚠ Partial/limited · ✗ Not available
Based on public documentation, April 2026. ⚠ Mem0 OSS: no admin UI, no auth, graph behind $249/mo SaaS Pro. ⚠ Cognee: experimental UI, not production-ready.
Integrations
Works with your Stack
FAQ
Questions, answered
What is NovaCortex?
NovaCortex is an open-source, self-hostable memory layer for AI agents. It gives agents persistent, queryable memory — typed memories linked by a relation graph, with semantic and text retrieval — exposed through a native MCP server, a REST API, TypeScript/Python SDKs, and a CLI. It runs entirely on your own infrastructure via Docker.
Does my data leave my infrastructure?
No. NovaCortex is self-hosted, so your knowledge base lives on your own servers and never goes to a third-party cloud. Retrieval also sends only the few relevant snippets to the model per query, instead of your whole knowledge base — so even less of your data is exposed than with context-dumping approaches.
How is NovaCortex different from Mem0 and Zep?
Mem0 and Zep are cloud-first. NovaCortex is privacy-first and self-hostable: your data stays on your infrastructure, and a portable open format (PMF) lets you export the entire memory graph at any time with zero lock-in. It is also MCP-native, so it plugs directly into Claude and Cursor.
How much does NovaCortex cost?
The full engine is free and open source (Apache-2.0) to self-host, with 3 namespaces. Pro is a one-time $10 license that unlocks 10 namespaces, namespace federation, and higher limits while staying self-hosted. Enterprise is custom, with unlimited namespaces and an SLA.
How much does retrieval save versus putting everything in context?
In a reproducible benchmark (15 questions, gpt-4o-mini, top-5 retrieval), retrieving only the relevant memories used 85% to 98.8% fewer input tokens than dumping the whole knowledge base into the prompt — about 65x cheaper per query on a 26K-token knowledge base — at parity answer accuracy and 100% retrieval recall. Dump cost grows with the knowledge base; retrieval stays flat.
Does NovaCortex work with Claude and Cursor?
Yes. NovaCortex ships a native Model Context Protocol (MCP) server with 15 tools, so Claude, Cursor, or any MCP-compatible agent can store and retrieve memory directly. You can also use the REST API, the TypeScript or Python SDK, or the CLI.
Can I export my memory, or am I locked in?
You can export everything. The Portable Memory Format (PMF) exports the full graph — memories, relations, and embeddings — as JSON, compact binary (MessagePack), or AES-256-GCM-encrypted, all with integrity hashes. There is no lock-in.