Personal CRM basics
Local-first software
Local-first software keeps the primary copy of your data on your own device — apps work offline, sync is optional, and no server outage can lock you out.
Local-first software is an architecture in which the copy of your data on your own device is the primary one — not a cache of some server's truth. The app works fully offline, responds instantly because nothing waits on a network, and treats the cloud as an optional convenience for sync and backup rather than the place your data lives.
The term comes from a 2019 essay by Martin Kleppmann, Adam Wiggins, Peter van Hardenberg and Mark McGranaghan at the research lab Ink & Switch, which named the model, articulated seven ideals for it — from offline operation to long-term data preservation — and identified CRDTs (conflict-free replicated data types) as the technology that could make multi-device collaboration work without a central authority.
The core motivation is ownership: in a cloud app, your access to your own work depends on a company's servers, business model and goodwill. Local-first inverts that dependency. If the vendor disappears tomorrow, the app on your device keeps working and the files remain yours.
The Ink & Switch essay and the seven ideals
'Local-first software: You own your data, in spite of the cloud' set out seven ideals as a test for the label: work is instant (no spinners), work is not trapped on one device, the network is optional, collaboration with others remains possible, data outlives the apps and companies of today ('the Long Now'), security and privacy come by default, and the user retains ultimate ownership and control. The authors graded existing software against the list — Git plus text files scored remarkably well; Google Docs scored well on collaboration and poorly on ownership — and reported their experiments using CRDTs to merge concurrent edits without a master server. The essay became the founding document of a movement now spanning sync engines, conferences and a growing catalog of products.
Local-first vs. offline-first vs. self-hosted
Three terms get conflated. Offline-first is a weaker promise about availability: the app tolerates network loss, but the server usually remains the source of truth and your local copy a cache — many offline-first apps are unusable once your account is closed. Self-hosted moves the server under your control but keeps the client-server shape: you own the data because you operate the infrastructure, with the ops burden that entails. Local-first removes the privileged server entirely — the device copy is authoritative, and any server involved in sync is a replaceable relay, ideally one that only ever sees encrypted blobs. Quick test: turn off the vendor's servers in your imagination. Offline-first limps, self-hosted doesn't care because you are the vendor, local-first doesn't care because there was nothing essential to turn off.
What local-first looks like in a personal CRM
Relationship notes are a near-perfect fit for the architecture: they are deeply private, they are written and read by one person, and they should outlive any app — notes about your closest people are decades-scale data. Endearist is built local-first for exactly these reasons: the contact database lives on your device and is fully functional with no account and no connection; sync across devices is opt-in and end-to-end encrypted with AES-256-GCM, with an EU-hosted relay for those who want their ciphertext under European jurisdiction; and Markdown export honors the essay's longevity ideal, since plain text is the format most likely to be readable in 2056. The model has limits worth naming — real-time multi-user collaboration is harder without a central server — but a personal CRM rarely needs it: the collaboration in your friendships happens between people, not between replicas.
Frequently asked questions
- Does local-first mean my data is never in the cloud?
- Not necessarily — it means the cloud is optional and subordinate. Many local-first apps offer sync through a server, but the device copy stays primary and, in well-designed systems, the server only ever stores end-to-end encrypted data it cannot read. You can usually decline sync entirely and run purely on-device, which is the configuration with the smallest possible trust footprint.
- What happens to a local-first app when the company shuts down?
- The app keeps working, because nothing essential ran on the company's servers — that is the architecture's central promise. You lose future updates and the hosted sync relay, but your data and the current version remain functional indefinitely. Contrast with a cloud app, where shutdown means a download-your-data deadline and then nothing. Export formats still matter for the very long term, when old binaries stop running on new systems.
- Is local-first slower or less capable than cloud software?
- Usually the opposite on speed: every action hits local storage, so there is no network latency — the essay's first ideal is 'no spinners'. The genuine trade-offs lie elsewhere: real-time collaboration among many users is harder to engineer, server-side heavy computation isn't available, and multi-device conflict resolution must be designed carefully. For single-user tools like notes, journals and personal CRMs, those costs barely apply.
Last updated: 2026-06-10
Tend relationships, not records.
Endearist is a local-first personal CRM. Free up to 25 contacts.
Start free