Docs › Memory
Sharing and the Memory server
Your research stays yours
Everything — memory, embeddings, journal, the cockpit — runs locally on your machine. CPU-only; no API keys, no telemetry, no cloud calls. Out of the box it uses a zero-download hashing embedder (Unicode-aware, so it works in any language) — nothing to fetch. Want stronger semantic recall? Opt in to a one-time ~127 MB model — or a ~130 MB multilingual one (50+ languages, cross-lingual recall) — that also runs entirely locally.
Sharing is a separate, deliberate step: export a pack and publish it to the Memory server at priorstates.com/w — browse shared packs, keep an account for your own, and share within groups. Nothing goes there unless you send it.