If local-first aims to reconstruct software without needing the cloud by inverting ideas data ownership, credible exit, reliance of authoritative servers, software longevity, etc. than the co-option that I think is happening is energy of local-first will be funneled towards sync engines...
Nov 13, 2025 at 6:13 AM
Local-first software: You own your data, in spite of the cloud
A new generation of collaborative software that allows users to retain ownership of their data.
Local-first software: You own your data, in spite of the cloud
A new generation of collaborative software that allows users to retain ownership of their data.
Local-First Software: Taking Back Control of Our Data | a mini-doc
LocalFirst: You Keep Using That Word
If you’ve been following the local-first scene over the past few years, you already know a good definition for the term “local-first” is hard to pin down. Part of the reason is that most people write software for money … and true local-first software is harder to capitalize. “Local-first” is a direct attack on vendor lock-in of all forms: data, formats, protocols, apps, services, and even environments. But the fact your employer can’t exploit this technology with a new revenue model (yet) is a minor problem.
Adam Wiggins (Ink & Switch) - Local-First Software: Pragmatism vs Idealism
Peter Van Hardenberg - Local First: the secret master plan
The past, present, and future of local-first - Martin Kleppmann (Local-First Conf)
The past, present, and future of local-first - Martin Kleppmann (Local-First Conf)
Local-first software: you own your data, in spite of the cloud
As part of the Digital Library's transition to Open Access, new features for researchers are available in the Premium Edition. Click here to learn more.
Local-first software: pragmatism vs idealism
Peter van Hardenberg - Ink and Switch, Automerge
Brendan O'Brien (number 0) - Can Sync Be Network-optional?
Zero is Not Local-First. It's Better.
Zero's partial sync approach gives us more control, better performance, and fewer headaches when building apps with lots of data. Here's why, and how I've been using it.
Mitigating Geopolitical Risks with Local-First Software and atproto
Martin Kleppmann discusses the urgent need for technological sovereignty in modern infrastructure. Exploring the shifting landscape of global tech dependencies, he shares how engineering leaders can leverage multi-cloud architecture, de facto API standardization, the AT Protocol, and local-first development paradigms to reclaim user agency and build highly resilient systems.
