security & privacy
Same engine, three ways to run it.
The architecture is the same whether you self-manage, use Cloud, or self-host. Six defaults you don't have to configure.
You choose where the engine runs
Open Source on your laptop, our managed Cloud, or self-hosted Enterprise inside your VPC. The recall and conflict logic is identical across all three.
Provenance on every memory
Memories can link back to raw events, session payloads, or imported evidence. The dashboard exposes that evidence instead of hiding it inside a vector.
Never used as training data
Your memories, sessions, and code are not used to train any model. Not ours, not anyone else's.
Conflicts surface, never silently win
When two captures disagree, membl flags the conflict instead of picking. Stale, contradicted, or superseded facts drop out of recall automatically.
Open, portable storage
The M1 store is SQLite with documented tables for events, memories, edges, recall, review, and savings. Backups and exports stay straightforward.
Measured before claimed
Savings are logged as events. Repeated recall is measured directly; broader context savings stay labeled as estimates until benchmarks prove them.