Hermes Memory Providers — Comparison of 9 External Backends

Source: ai-research/agentwikis-hermes-memory-providers-2026-06-12.md — compiled by Agent Wikis from official v0.16.0-era docs; sourced 2026-06-12

Hermes ships with a built-in memory store and, since v0.7.0, a pluggable memory provider interface that third-party backends implement. Only one external provider is active at a time, running alongside (never replacing) the built-in MEMORY.md/USER.md layer and FTS5 session search. v0.16.0-era docs list 9 external providers. No cross-provider migration — memories don’t migrate between providers, so plan before committing; hermes sessions export before switching is the safety net.

Key Takeaways

• Don’t optimize prematurely — built-in is fine for most solo developers until “repeating context or losing long-term recall” becomes a pattern
• Holographic is now the recommended first upgrade — zero dependencies, one command, no API key, trust-scored facts + contradiction detection; the old advice of jumping straight to a cloud provider no longer holds
• Four architectural styles — document store (built-in), identity modeling (Honcho/Supermemory), structured knowledge (Hindsight/OpenViking/ByteRover), hands-off extraction services (Mem0/RetainDB/Memori)
• “Third-party” no longer means less supported — Hindsight is the most actively maintained third-party provider across Hermes release history; OpenViking carries Volcengine/ByteDance weight
• Field signal — a 3-month daily driver reverted to built-in (2026-06). [Reddit r/hermesagent] An operator who tried “every memory provider connected to Hermes, plus a few open-source ones from GitHub” turned them all off and settled on the built-in markdown USER / MEMORY / SOUL layer (USER + MEMORY short and agent-editable, SOUL immutable), framing the lesson as “agents don’t remember, agents read.” A concrete reversion case behind the “don’t optimize prematurely” recommendation above. (Source: raw/reddit-1u8fm0t.md.)

Cost, Hosting, Trust

Provider	Hosting	Cost	Trust
Built-in	Local ~/.hermes/	Free	First-party (Nous)
Honcho	Cloud or self-hosted	Cloud metered; self-hosted free	First-party reference plugin
OpenViking	Self-hosted only	Free (AGPL-3.0)	Volcengine (ByteDance)
Mem0	Cloud only	Mem0 pricing	Third-party
Hindsight	Cloud or local (embedded PostgreSQL)	Cloud paid / local free	Third-party; most actively maintained
Holographic	Local only (SQLite)	Free	Official plugin; zero dependencies
RetainDB	Cloud only	$20/mo flat	Third-party; only published flat price
ByteRover	Local-first; optional cloud sync	Free local / paid sync	Third-party; SOC2 Type II cloud
Supermemory	Cloud only	Supermemory pricing	Third-party; added v0.8.0
Memori	Cloud	Free tier + paid	Third-party; new v0.16.0; no entity page yet

Capability Matrix

Provider	Retrieval Style	Unique Feature
Built-in	FTS5 + curated markdown	Always on; human-auditable plain text
Honcho	Semantic + dialectic LLM reasoning	Dialectic user modeling; per-profile AI peers; 3 tunable cost knobs
OpenViking	Tiered L0 (~100 tok) → L1 (~2k) → L2 (full)	viking:// filesystem hierarchy; first-class URL/doc ingestion
Mem0	Semantic + reranking	Server-side LLM fact extraction with auto-dedup — fully hands-off
Hindsight	Semantic + graph + temporal	Knowledge graph + hindsight_reflect cross-memory synthesis
Holographic	FTS5 + HRR compositional algebra	probe/reason/contradict algebraic queries; trust scoring
RetainDB	Hybrid: vector + BM25 + reranking	Delta compression; 7 memory types with importance scores
ByteRover	Fuzzy text first, LLM-driven when needed	Pre-compression extraction — saves insights before context compaction discards them
Supermemory	Semantic; hybrid/memories/documents modes	Context fencing + multi-container partitioning for multi-tenant use
Memori	Structured recall	Tool-aware turn capture + project/session attribution (docs-only)

Setup Difficulty

Provider	Difficulty
Built-in	Trivial (already configured)
Holographic	Trivial — hermes config set memory.provider holographic. No API key, no server, no pip install
ByteRover	Easy — install brv CLI (script or npm), no API key for local mode
Mem0 / RetainDB / Supermemory	Easy — hermes memory setup + API key in ~/.hermes/.env
Honcho (cloud)	Easy — hermes memory setup wizard
Hindsight (cloud)	Easy — wizard auto-installs; local = Medium (embedded PostgreSQL + LLM API key)
Honcho (self-hosted)	Medium — run your own Honcho instance, set baseUrl
OpenViking	Medium — pip install openviking, run openviking-server, set OPENVIKING_ENDPOINT

Four Architectural Styles

1. Document store + FTS (built-in) — cheapest, simplest; single-user/machine; always-on baseline.
2. Identity modeling (Honcho, Supermemory) — builds explicit per-peer/profile structures; Honcho goes deepest with per-profile AI peers, observation toggles, and three orthogonal cost knobs (contextCadence, dialecticCadence, dialecticDepth).
3. Structured knowledge (Hindsight, OpenViking, ByteRover) — organizes memory as navigable structure: knowledge graph with entity resolution (Hindsight), filesystem hierarchy with tiered token-cheap loading (OpenViking), hierarchical knowledge tree (ByteRover). Best when you want the agent to browse what it knows.
4. Extraction + retrieval services (Mem0, RetainDB, Memori) and local algebra (Holographic) — Holographic is the outlier: pure local FTS5 + HRR compositional queries with no embedding model at all.

Recommendations by Use Case

Situation	Pick
Just getting started	Built-in — don’t optimize prematurely
Memory pressure, zero new infrastructure	Holographic — one command, no API key, trust-scored facts + contradiction detection
Solo dev, wants portable memory	ByteRover — local-first brv tree, pre-compression extraction, travels to other tools
Agent should deeply model you (or many users)	Honcho — first-party, dialectic user modeling, per-profile AI peers
Explicit knowledge graph + cross-memory synthesis	Hindsight — hindsight_reflect is unique; free local mode
Data residency, self-hosted structured knowledge	OpenViking — free AGPL-3.0, viking:// hierarchy, first-class URL/doc ingestion
Multi-tenant gateway with work/personal partitioning	Supermemory (multi-container + {identity} tags) or Honcho profiles
Hands-off extraction, nothing to curate	Mem0 — server-side LLM extraction with dedup
Predictable budget	RetainDB — flat $20/mo, hybrid vector + BM25 + rerank
Maximum vendor neutrality	Built-in + hermes sessions export

Profile Isolation

Each provider handles multi-instance isolation differently: local-path providers (Holographic, ByteRover) inherit $HERMES_HOME separation; config-file providers (Honcho, Mem0, Hindsight, Supermemory) use per-profile credentials; RetainDB auto-derives profile-scoped project names; OpenViking is configured per-profile via .env. See Profiles & Multi-Instance for the full isolation model.

Try It

• Check your current provider: hermes config get memory.provider
• Switch to Holographic (safest first upgrade): hermes config set memory.provider holographic
• Set up a cloud provider: hermes memory setup → follow wizard
• Before switching: hermes sessions export to preserve session history
• Check what Hermes remembers: /memory in any session

Related

• Hermes GAPA — the self-improvement loop that writes to memory
• Profiles & Multi-Instance — how profiles isolate memory per agent instance
• Hermes MemoryKit — community 8-layer memory stack built on top of these providers
• Nate Herk 1-Hour Course — notes that stale memory is the #1 cause of weird agent behavior
• agentmemory — alternative memory architecture for coding agents (4-tier, BM25+vector+KG)