Persistent memory of patient charts from a single local SQLite file — no cloud vector database, no embeddings API. PHI stays inside your four walls, so there's no third-party data processor to add to a BAA — and you can prove it.
The whole chart memory is one SQLite file on the device. No vector DB to stand up inside your compliance perimeter — or breach.
Retrieval runs in-process. The air-gapped build fuses outbound connections off, so chart text physically cannot reach an external API.
Every recall shows its per-facet score (content · keyword · salience · temporal) — auditable retrieval, not an opaque embedding service.
One SQLite file per patient or workspace. MIT licensed, no per-seat fees, no vendor in the PHI path.
The same engine for PHI that legally cannot leave the device — and what your security team can test.
# one file per patient — PHI never leaves the box curl -fsSL https://locamem.com/install | bash # then point Claude Code / Codex / any MCP client at it
Demo content is fictional and synthetic — no real patient data or PHI. Locamem is software, not compliance advice; your HIPAA posture depends on your overall deployment.