Kemory vs Honcho

A model of the conversation.
A governed memory across contexts.

Honcho, from Plastic Labs, reasons over the messages your app stores to model the people and agents in it. Kemory starts from the user: it captures chats across the major AIs, recalls them over MCP, and governs sharing between people.

Last verified 7 November 2026 against primary sources

The verdict

Two good answers.
Different jobs.

Choose Honcho if…
  • Modelling users and agents over time is central to your product, and you want natural-language answers about a peer.
  • You want open-source, self-hostable memory infrastructure and can work with AGPL-3.0.
  • You want multi-peer perspectives: what one agent or user knows about another.
Choose Kemory if…
  • You want your own chats in ChatGPT, Claude, Gemini, Perplexity, Manus and Grok captured automatically, then recalled or continued in another AI.
  • You need to share memory with other people across organisations, with accept-to-receive, revocation and audited reads.
  • You want consumer and team plans at a fixed price per seat, rather than usage-based billing.
Ideal for

See each one
doing its job.

Public homepage, captured 7 November 2026.
Honcho is ideal for
Apps built around reasoning over conversations.
Peer modellingStateful agentsSelf-hosted server
Kemory Kemories view: memories and chats from every AI in one place, filtered by AI.
Kemory is ideal for
Governed memory across agents and AIs.
Namespace rulesTamper-evident auditCross-AI capture

Screenshots taken 7 November 2026. Honcho is a trademark of its owner, shown here to identify the product.

At a glance

The same rows on every comparison, so you can read one page against another.

Feature
This siteKora + Kemory
Honcho
Capture
Kora, an AI chief of staff, included
Yes
—
Pulls in your AI chats automatically
Yes(6 AIs)
Via plugins
Keeps whole chats and distilled memories
Yes
Yes
Keeps chat artefacts — files, code, images
Yes
—
Use
Native in Claude and ChatGPT (MCP connector)
Yes
Manual
Protocols
MCP · REST · CLI · SDK
MCP · API · SDK
Ask across everything, with sources
Yes
Yes(dialectic)
Continue a chat in another AI
Yes
—
Counsel — many models, one answer
Yes
—
WhatsApp
Yes(Coming Soon)
Third-party only
Builds a model of you
Yes
Yes
Share & govern
Two-way memory sharing between people
Yes(across orgs)
—
Fine-grained memory permissions
Yes
Scoped keys
Audit trail and provenance
Yes
Sources
Shows contradictions, lets you resolve them
Yes
—
Privacy & trust
Private by default — private tags, secrets stripped
Yes
—
Delete and prove it's gone
Yes(crypto-shred)
—
Data residency on every plan
Yes(India · Switzerland)
Self-host
Measured token savings
Yes
—
Version history and restore
Yes
—
Openness
You hold the keys (community edition only)
Yes
Partial
Integrated with SeKondBrain's Cognition Layer
Yes(Coming Soon)
—
Open-source
Yes(community)
Yes(AGPL-3.0)
Proof & price
Published benchmark
89.6% LongMemEval-S*
Not verified
Pricing shape
Free to start
Usage-based

*89.6% end-to-end answer accuracy on LongMemEval-S, open-weight Llama-3.3-70B reader, six runs. See the benchmarks or the full method on docs.sekondbrain.ai. A dash means not documented, not proven absent.

Where they differ

The same job,
done two ways.

Synthesis
HonchoBackground reasoning builds conclusions and peer representations
KemoryRaw memories, namespace summaries, then one synthesised context
Getting material in
HonchoYour app stores messages; agent plugins and import guides
KemoryKora for Chrome captures six AIs in the background, with history import
Governance
HonchoAPI keys scoped to workspace, peer or session; row-level tenant isolation
KemoryGatekeeper, just-in-time consent and a hash-chained audit log
Where Honcho is ahead
Credit where it’s due.

Honcho's peer-centric model is purpose-built for reasoning about people and agents over time. The whole server is open source and self-hostable today, and each derived conclusion cites the messages it came from.

Benchmarks

The numbers,
and how each was run.

These rows use different datasets, splits, readers and retrieval budgets, so they cannot be compared directly. We publish the method, every run including the lower ones, and use an open-weight reader rather than a frontier model.

ProductBenchmarkScoreWhat it measuresSetupReader modelRuns
KemoryLongMemEval‑S89.6%End-to-end answer accuracy500 questions, oracle splitLlama-3.3-70B (open-weight)Six, with variance
HonchoLongMemEval, LoCoMoNot verifiedSelf-reported (“Pareto frontier”)Not verifiedNot verifiedNot verified
Read the Kemory benchmark on docs.sekondbrain.aiHoncho’s published figuresOther products’ figures are their own, self-reported, and not re-run by us.

What changed at Honcho

Products move quickly. These are the dated changes this comparison has been checked against.

  1. August–November 2026Releases 3.1 to 3.6, every week or two.
  2. 29 October 2026v3.5.0: conclusions cite the messages they came from; peer chat answers in a single turn.
  3. 5 November 2026v3.6.0: optional multi-tenancy with Postgres row-level security; Representation History.
The bigger picture

Specialists do one job well.
Kemory holds the thread across them all.

Every year brings better models and you will keep trying them. Kemory sits above the models rather than inside any one of them, so what you have worked out goes with you.

01
One memory every AI shares.

Tell one AI something once, and every AI you use just knows it. Start a thought in one and carry on in another, mid-sentence.

02
Permissioned, auditable AI memory.

Every memory is permissioned and every change is provable. We do not train on your data. Delete anything, and prove it is gone.

03
Save tokens and time.

Compaction runs on an open-weight model, so the frontier model only ever sees the compacted version — not the pile.

Already using Honcho? You do not have to replace it to try Kemory. Kemory connects to the AIs you use over MCP and Kora for Chrome.

Your call

Choosing Honcho instead?
Good — it fits you better right now.

Come back to Kemory when cross-AI, governed memory is what you need.

Questions

Five questions,
Kemory vs Honcho.

What is the difference between Kemory and Honcho?
Honcho is memory infrastructure for developers. It reasons over the messages your app stores to model users and agents. Kemory is a cross-AI memory for people and teams. It captures chats from the major AIs, recalls them over MCP, and governs sharing with consent and audit.
Does Honcho support more than one kind of peer?
Yes. Honcho's documentation describes peers as users, agents, groups, projects and ideas. When configured, it can model what one peer knows about another.
Can I self-host Honcho?
Yes. The server is open source under AGPL-3.0. You can run it with honcho start, with Docker Compose, or from source. A managed service also runs at api.honcho.dev, with a dedicated instance for each organisation.
How are Honcho and Kemory priced?
Honcho is usage-based: new accounts get a $5 credit, then $5 a month with a card on file. Kemory is free for 2,000 memories and two AIs, with Pro at $19.99 a month, Team at $30 a seat and Business at $55 a seat.
How do Honcho's benchmarks compare with Kemory's?
Not directly. Honcho's README cites evaluations on LongMemEval and LoCoMo, but we could not verify the scores, split or reader. Kemory publishes 89.6% end-to-end answer accuracy on the LongMemEval-S oracle split with an open-weight Llama-3.3-70B reader, across six runs.

More comparisons

Credit where it’s due. The real difference, either way.

Memory platformsvs NessieA searchable record of your AI work. A governed memory that travels between AIs.Memory platformsvs MemoryPluginOne person’s memory across 21+ AI tools. A governed memory you can share and audit.Memory platformsvs AI Context FlowContext you save once and carry into any AI. Memory that fills itself, with audited sharing.Memory platformsvs MaximemTwo products: Vity for people, Synap for agents. One governed memory for both, shared with audit.Memory platformsvs SupermemoryA fast memory API. A governed memory across your AIs.Memory platformsvs Living BrainA readable wiki. A memory that travels.Memory platformsvs Mem0A quick start. A shared memory with permissions.Viewing nowvs HonchoA model of the conversation. A governed memory across contexts.Assistantsvs ChatGPT and Claude memoryMemory built into your assistant. Or memory across your assistants.Personal memoryvs PiecesYour working day, on your machine. Your AI conversations, shared under rules.Personal memoryvs MinimiAmbient recall on your Mac. Or conversations you can carry forward.Memory platformsvs MemPalaceVerbatim recall on your own machine. Governed memory across AIs and people.Frameworksvs CogneeA knowledge graph your agents can search. A governed memory across AIs and people.Frameworksvs Basic MemoryA Markdown knowledge base you and your AI write. A memory that fills itself from your chats.Frameworksvs EverOSAn open memory runtime for agents. A governed memory for people, teams and agents.Frameworksvs Zep / GraphitiContext graphs for enterprise agents. A shared memory for people across AIs.Frameworksvs AWS AgentCore MemoryManaged memory for agents you run on AWS. A cross-AI memory people and agents share.Frameworksvs Google Memory BankManaged memory for agents on Google Cloud. A cross-AI memory people and agents share.
Compared against Honcho as of 7 November 2026. Products change — tell us if we’re wrong.Sources:Honcho GitHub READMECHANGELOGQuickstartDashboard and platformMCPReasoninghoncho-ai on PyPI
Cite this comparisonKemory vs Honcho. SeKondBrain. Last verified 7 November 2026. https://sekondbrain.ai/products/kemory/compare/honcho