On-device · behind your information barrier · no egress

Client and deal memory that never leaves the box.

Persistent memory of client accounts and live deals from a single local SQLite file — no cloud vector database, no embeddings API. Client PII and MNPI stay inside your information barrier, with no third-party processor in the data path — and you can prove it.

Live · runs in your browser

Ask a client account or a live deal. Watch where the data goes — nowhere.

One file, not a stack

17a-4-friendly

The whole book of memory is one SQLite file — copy, encrypt, retain, shred. No vector DB inside your compliance perimeter to secure or breach.

No egress, provably

Zero network calls

Retrieval runs in-process. The air-gapped build fuses outbound connections off, so MNPI and client PII physically cannot reach an external API.

Auditable ranking

For reviewers, not black boxes

Every recall shows its per-facet score (content · keyword · salience · temporal) — auditable retrieval for compliance.

How it deploys

Self-host the library — or run it air-gapped for data that can't cross the barrier.

Recommended · self-host

Inside your perimeter

One SQLite file per client, deal, or desk. MIT licensed, no per-seat fees, no vendor in the PII/MNPI path.

Strict mode · air-gapped

Egress fused off

The same engine for restricted/MNPI work that legally cannot leave the device — and what compliance can test.

# one file per client/deal — nothing crosses the barrier
curl -fsSL https://locamem.com/install | bash
# then point Claude Code / Codex / any MCP client at it
Install LocamemTalk to us about on-prem

Demo content is fictional and synthetic — no real client data or MNPI. Locamem is software, not compliance advice; your regulatory posture depends on your overall deployment.