Skip to content
Flag of Europe
Made in the European Union · Independently built · Released under EUPL 1.2

← jMemoria

How jMemoria compares

An honest placement, not a scoreboard — categories, not named products. Each approach is good at something. jMemoria is the only one built for review, provenance and reproducibility: an AI edit stays a proposal until a human confirms it, every change lands in an immutable history, and any model can read it.

Reviewed, not overwritten Immutable history, built in Any model, not per vendor Self-hosted

What only jMemoria does

Three things set jMemoria apart from a wiki, a built-in assistant memory and an agent memory layer alike.

Side by side

jMemoria is the highlighted column; the others are the categories it is most often confused with.

DimensionjMemoriaMarkdown wiki / vaultBuilt-in assistant memoryMemory layer for agents
Unitstructured items, relations, artifactsfree-form pagefacts the vendor storesextracted facts, graphs
Historyimmutable, built inexternal (git), optionalnot exposedupdated in place
AI writesproposals until a human confirmschange the truth immediatelychange the truth immediatelymerged automatically
Across modelsyesyes, if files are sharedno — per vendoryes
Hostingself-hosted onlylocal filesvendorcloud or self-hosted
Strengthreview, provenance, reproducibilityfree-form prose, zero setupalready thererecall quality, semantic search
Where jMemoria is not the right tool. jMemoria is not a semantic search engine. If your main need is recalling the most relevant snippet from a large unstructured corpus, a dedicated memory layer does that better today. jMemoria is for knowledge you want structured, reviewed and reproducible — and portable across whichever models you use.

In a wiki, an agent's edit becomes the truth immediately and is indistinguishable from yours. jMemoria keeps it a reviewed proposal, over an immutable history, that any model can read and build on.

← Back to jMemoria