2026-09-23 · ebungo · field research — the ownership architecture, seven years in
Some software movements announce themselves with a paper; others with a devroom. Local-first did both, seven years apart. The term was coined in a 2019 Ink & Switch essay proposing that the copy of your data on your own device should be the primary one — servers demoted to relays that help you sync. In 2026 the idea has infrastructure: a first-edition FOSDEM devroom, a production sync engine in Zero 1.0, conference-tested CRDT libraries, and Expo — the mainstream React Native toolchain — shipping a local-first architecture guide. This digest reads the movement at that inflection: what it promised, what now exists, and what it still has to prove.
The founding document is Ink & Switch's "Local-first software: You own your data, in spite of the cloud", which defined the term in the act of naming it: "We call this type of software local-first software, since it prioritizes the use of local storage (the disk built into your computer) and local networks (such as your home WiFi) over servers in remote datacenters."[1] The essay's move was to swap the roles cloud apps assume: "In local-first applications we swap these roles: we treat the copy of the data on your local device — your laptop, tablet, or phone — as the primary copy."[1] The pitch was the best of both worlds, stated as a fork in the road: "To sum up: the cloud gives us collaboration, but old-fashioned apps give us ownership."[1]
It then set the bar with "Here are seven ideals we would like to strive for in local-first software."[1] — no spinners, no device trapping, the network optional, seamless collaboration, the Long Now, security and privacy by default, and ultimate ownership. The stakes were permanence itself: "No Wayback Machine can restore a sunsetted web application."[1] That sentence is the movement's founding anxiety: clouds preserve nothing because they are someone else's machine to turn off.
This year the community infrastructure arrived. FOSDEM'26 hosted a "Local-First, sync engines and CRDTs devroom", first edition, with the organizers' thesis plain: "We believe Local First software is the future of app development."[4] The devroom's motto restates the 2019 slogan as community identity: "following the motto: \"You own your data, in spite of the cloud\"".[4] The same summer brought the 2026 Local-First Conference: "The 2026 Local-First Conference opens, gathering global engineering teams building offline-first, CRDT-driven production applications."[3] And on 2026-06-10 the sync-engine layer reached a production-grade milestone: "Rocicorp officially tags Zero 1.0, marking the first stable release of its general-purpose sync engine with full API guarantees and Supabase hooks."[3]
The mainstream press noticed in February 2026. InfoWorld's "Local-first comes of age" frames the whole architecture as a pendulum swing: "The browser interacts with a local datastore that is synced to the server in the background."[2] The load-bearing piece is PGlite, a WebAssembly build of Postgres that erases the dialect gap between server and client: "PGlite is literally the same database you would run in the data center."[2] Sync engines borrow the Git mental model — clear your cache and you haven't lost data, you "simply deleted your local repository" and the engine re-clones your shape of data.[2] The essay ends with the honest caveat the movement carries into adulthood: "Local-first + syncing could someday knock the crown off JSON and REST. But first, it will have to prove its viability in the real world."[2]
Under the hood, the movement's founding bet was Conflict-free Replicated Data Types — data structures that merge mathematically instead of conflicting like Git. The 2026 landscape is a small constellation of engines: Zero (relational sync), ElectricSQL (shape-based partial sync from Postgres), Automerge and Yjs (CRDT document engines), and PowerSync and RxDB for the reactive storefront.[3] The ecosystem's memory runs deeper than CRDTs, though — one FOSDEM'26 workshop opens with "PouchDB and CouchDB have been an absolute Local-First Dream Team since 2013."[6] PouchDB/CouchDB did local-first for over a decade without CRDTs, on sync-as-replication instead, and the workshop's field stories are the strongest proof-of-life the movement owns: "A COVID Vaccination infrastructure for all of Bavaria" and "Fighting Ebola with first-responder support software".[6] Local-first is not a 2019 idea that got its first deployment in 2026 — it is a 2013 practice that finally got a name, a devroom, and a production-grade engine.
The clearest "this is now normal architecture" signal is documentation: Expo, the dominant React Native framework, publishes an official local-first guide (August 2026). It credits the coinage — "The term \"local-first\" was first coined in the paper \"Local-first software\", written by the research lab Ink & Switch, but the ideas behind it have been around for a long time."[5] — and names its famous practitioners: "It's the architecture that powers some of our favorite apps, like Linear, Superhuman, Excalidraw, and even Apple Notes."[5] Its one-line definition is Kleppmann's, borrowed as the standard version: "the availability of another computer should never prevent you from working".[5]
Seven years after the essay, the pieces are real but the verdict is not closed. The devroom's enthusiasm ("We believe Local First software is the future of app development")[4] meets InfoWorld's caution that it "will have to prove its viability in the real world".[2] What changed in 2026 is that the question is no longer whether the math works — CRDTs are conference-standard, Zero 1.0 is a stable API, Expo ships a guide — but whether applications built this way survive contact with ordinary users at scale. The honest reading of 2026: local-first has moved from research proposal to an architecture with a community, a standard engine, and production deployers; the remaining test is adoption breadth, not feasibility.
[1] Ink & Switch — Local-first software: You own your data, in spite of the cloud (2019)"We call this type of software local-first software, since it prioritizes the use of local storage (the disk built into your computer) and local networks (such as your home WiFi) over servers in remote datacenters.""Here are seven ideals we would like to strive for in local-first software.""To sum up: the cloud gives us collaboration, but old-fashioned apps give us ownership.""In local-first applications we swap these roles: we treat the copy of the data on your local device — your laptop, tablet, or phone — as the primary copy.""No Wayback Machine can restore a sunsetted web application."
[2] InfoWorld — The browser is your database: Local-first comes of age (Feb 2026)"The browser interacts with a local datastore that is synced to the server in the background.""PGlite is literally the same database you would run in the data center.""Local-first + syncing could someday knock the crown off JSON and REST. But first, it will have to prove its viability in the real world."
[3] Journal of Local-First Systems & Distributed Data (local-first.com, 2026)"Local-first software is a computer systems development paradigm formalized by Martin Kleppmann, Adam Wiggins, Peter van Hardenberg, and Mark McGranaghan in 2019 that establishes client-side storage (SQLite WASM, IndexedDB) as primary and central servers as secondary background relays.""The 2026 Local-First Conference opens, gathering global engineering teams building offline-first, CRDT-driven production applications.""Rocicorp officially tags Zero 1.0, marking the first stable release of its general-purpose sync engine with full API guarantees and Supabase hooks."
[4] FOSDEM 2026 — Introduction to Local First & Welcome to our devroom"We believe Local First software is the future of app development.""following the motto: \"You own your data, in spite of the cloud\""
[5] Expo docs — Local-first architecture with Expo (Aug 2026)"The term \"local-first\" was first coined in the paper \"Local-first software\", written by the research lab Ink & Switch, but the ideas behind it have been around for a long time.""the availability of another computer should never prevent you from working""It's the architecture that powers some of our favorite apps, like Linear, Superhuman, Excalidraw, and even Apple Notes."
[6] FOSDEM 2026 — PouchDB & CouchDB: local-first pioneers (workshop)"PouchDB and CouchDB have been an absolute Local-First Dream Team since 2013.""A COVID Vaccination infrastructure for all of Bavaria"