Home / Compare / mem0

Lians vs Mem0: benchmark and audit controls.

LoCoMo: Lians reports 92.9%; Mem0 reports 92.5%. Settings differ. A separate test covers five audit-critical invariants.

Credit first

Where mem0 is genuinely strong.

Mem0 offers strong developer experience, open source, hosted service, and a respected benchmark harness. It is a solid default for consumer personalization.

Recall quality · LOCOMO · run 2026-07-09

Current reported top-200 results: Lians 92.9, Mem0 92.5.

92.9%Lians · LLM-judged QA accuracy 92.5%Mem0 · current published top-200 score

Lians retrieval was scored by the unmodified mem0ai/memory-benchmarks ↗ answer and judge pipeline across all 10 LoCoMo conversations. Each product uses its own memory construction and retrieval settings, so these are comparable reported results rather than a controlled head-to-head experiment. Full Lians protocol and caveats →

Regulated-memory eval · last run 2026-07-04

The five invariants.

Regulated invariantLiansmem0
Stale revision suppressedpassfail
Point-in-time (as-of) recallpassabsent
Provable erasure (crypto-shred + cert)passpartial
Lookahead / backtest guardpassabsent
Audit-state snapshot at Tpassabsent
Score (pass = 1, partial = ½)5.0 / 50.5 / 5

Both columns executed live: mem0 OSS in its default documented config returned superseded and current revisions side by side, unmarked. Behavioral evidence in the methodology doc ↗.

Where the lanes diverge

Different jobs, different guarantees.

Mem0 accumulates revisions and resolves updates with an LLM. It lacks event-time modeling, as-of recall, and proof-producing deletion.

The honest recommendation

Which should you pick?

Choose Mem0 for consumer personalization. Choose Lians when someone may ask what the agent knew at a past moment.

Migration guide ↗

Open methodology

Mem0 has a public right of reply.

We asked Mem0 to review the configuration, evidence, and scoring in public. If a default behavior, documented capability, or result is wrong, we will rerun the adapter and correct this page.

Read or respond to the public fact-check request ↗

Bring the numbers to your compliance officer.

Get an API key →