Back to Gap Map Product / UX / Agent memory & context stores

MIRIX

MIRIX AI
open source / Overall score: 2.8

MIRIX is a memory server for LLM agents in which dedicated memory agents extract core, episodic, semantic, procedural, resource and knowledge-vault memories from conversations and tool traces, merge and correct them in Auto-Dream passes, and serve them back through keyword, embedding and optional graph search. The server self-hosts with Docker or runs as a hosted API, and agents reach it through a Python client. MIRIX AI builds it.

Read against the memory server on the main branch. The desktop personal assistant the repository first shipped is deprecated and kept on its desktop-agent branch, and is not scored.

Openness

5 high confidence
5.0
license
Apache-2.0 (the MIRIX server, memory agents, dashboard and Python client)
source
public
core features withheld
no — the 656-path tree at 9077e4b holds the FastAPI server, memory agents, Auto-Dream, graph memory, dashboard and client with one root LICENSE and no ee/, enterprise/, commercial/ or proprietary/ path; the hosted API at app.mirix.io is a separate service the same client reaches
commercial
hosted MIRIX API at app.mirix.io

The MIRIX memory server, including its memory agents, Auto-Dream consolidation and graph memory, is published in full and self-hosts with Docker Compose beside PostgreSQL and an optional Neo4j. MIRIX AI also runs a hosted API that the same client reaches, and nothing in the repository is held back for it.

Adoption

2 low confidence
2.0

GitHub stars are the only signal, because the MIRIX server ships as source and Docker images rather than through a package registry. The mirix package on PyPI is the client that reaches a hosted or self-hosted server, so its downloads count client installs rather than MIRIX deployments and are left out. A star is not a deployment.

Capability

4 medium confidence
4.0

MIRIX extracts six kinds of memory from raw messages with dedicated agents, merges and corrects them in Auto-Dream passes, and retrieves across the typed stores and an optional graph. Its only forgetting is a fade and expiry period the developer sets, so nothing retires a memory because it stopped being true.

Verified 2026-11-20, except some scores, still awaiting re-confirmation