Cloud apps are popular because they make collaboration and multi-device access effortless — but they concentrate your data on someone else's servers.[1] If the service shuts down, "the software stops functioning, and data created with that software is lost."[1] The local-first answer is software that keeps the collaboration but hands ownership back to the user: "a set of principles for software that enables both collaboration and ownership for users," with the ideals of working offline, collaborating across devices, and improving security, privacy, long-term preservation, and user control of data.[1]
The movement's founding essay, published by Ink & Switch in April 2019, lays out seven ideals — no spinners (your work at your fingertips), multi-device, offline, collaboration, privacy and access control, long-term preservation, and user control of the data itself.[1] Together they reframe the default: instead of "your files live on my server," the premise becomes "your data is yours; I only help you sync it."[1]
The enabling idea is the conflict-free replicated data type (CRDT): "a data structure that is replicated across multiple computers in a network." Any replica can be updated independently and concurrently, without coordinating with the others; an algorithm that is part of the data type automatically resolves inconsistencies, and although replicas may differ at any instant, "they are guaranteed to eventually converge."[2]
This matters because it is the thing Google Docs-style collaboration got by centralizing. CRDTs let many devices edit the same data and merge automatically — the collaboration without the central server — which is precisely what the local-first ideals call for.[2][1] The concept was formally defined in 2011 by Marc Shapiro, Nuno Preguiça, Carlos Baquero, and Marek Zawirski.[2]
The ideas are not academic anymore; the tooling is real and shipping. Automerge, one of the better-known CRDT libraries, is described as "a JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically."[3] It is an MIT-licensed, actively-maintained JavaScript project — last pushed 2026-08-18, roughly 6,500 stars — a concrete sign that the local-first toolbox has live, production traction seven years after the founding essay.[3] The pattern now spans note-taking, collaborative documents, and offline-first apps: the building blocks are mature enough to build on.
Local-first is easy to file under "developer trends," but the stakes are ordinary-user stakes: when a cloud service closes or revokes access, users lose the ability to reach their own work — the founding essay's exact warning that with centralized storage, "data created with that software is lost."[1] Software that keeps a local copy and treats the cloud as a sync layer changes that relationship: your data survives the service. That is a property worth valuing in an era where more of life is mediated by someone else's server — and it is the reason the movement has outlasted its original manifesto and become durable engineering practice.
[1] inkandswitch.com/essay/local-first — Local-first software (Ink & Switch), verified 2026-08-19
"we propose "local-first software": a set of principles for software that enables both collaboration and ownership for users. Local-first ideals include the ability to work offline and collaborate across multiple devices, while also improving the security, privacy, long-term preservation, and user control of data."[2] en.wikipedia.org/wiki/Conflict-free_replicated_data_type — Conflict-free replicated data type (Wikipedia), verified 2026-08-19
"In distributed computing, a conflict-free replicated data type (CRDT) is a data structure that is replicated across multiple computers in a network, with the following features: The application can update any replica independently, concurrently and without coordinating with other replicas. An algorithm (itself part of the data type) automatically resolves any inconsistencies that might occur. Although replicas may have different state at any particular point in time, they are guaranteed to eventually converge."[3] github.com/automerge/automerge — Automerge (GitHub), verified 2026-08-19
"A JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically."