memory for code agents, with provenance
Stop re-teaching agents the same repo decisions.
membl records durable engineering facts from agent sessions, keeps evidence and status with each fact, and recalls only the active project-scoped context the next agent needs. The core engine runs locally; Cloud adds the managed dashboard and team review flow.
how it works
The value is smaller, cleaner context.
membl is for teams that run coding agents repeatedly on the same codebase. It reduces the setup tax at the start of a session and makes memory review explicit instead of magical.
Capture what should survive the chat
Hooks, imports, and the CLI turn agent sessions into candidate memories instead of another pile of transcript text.
Keep state with every fact
A memory is not just a string. It has project scope, kind, confidence, source evidence, and a lifecycle status.
Return a small packet
The next agent gets an active, project-scoped recall packet instead of raw notes, stale decisions, or the whole history.
pricing
Run the engine. Or let us run it for you.
The recall engine is open source and free to run yourself. The dashboard, shared graph, and managed operations come with Cloud. That's what you're paying for.
Open Source
The engine, on your machine. Terminal-only, no hosted dashboard.
- Rust recall and conflict-resolution engine
- CLI: capture, recall, review, savings
- Claude Code and Codex adapters
- Local SQLite store, self-managed
- Community support through GitHub issues
Cloud
Same engine, hosted by us, plus the visual dashboard, shared graph, and team workflows.
- Everything in Open Source
- Web dashboard: inbox, conflicts, recall trace, savings
- Shared graph across teammates, scoped per project
- Conflict review queue with assignment
- Managed upgrades, backups, observability
- Meridian7 onboarding path for first-customer testing
Enterprise
The full Cloud experience, dashboard included, running inside your perimeter.
- Everything in Cloud, self-hosted
- SAML, SCIM, custom retention policy
- Procurement paperwork, MSA, DPA
- Priority support and a shared Slack channel
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.