Software Is Quietly Moving Back to Your Device

After a decade of cloud-only apps, software is moving back onto your device. In 2026 the shift has a name — local-first — and momentum behind it. A document that lives on your own machine, in a format you can read, outlasts the company that made the app you wrote it in.¹

The phrase comes from a 2019 paper by Martin Kleppmann and three colleagues at Ink & Switch, titled "Local-First Software: You Own Your Data, in spite of the Cloud."¹ Its argument was simple and durable. "The cloud gives us collaboration," the authors wrote, "but old-fashioned apps give us ownership. Can't we have the best of both worlds?"² For years that read as a research wish. In 2026 it reads as a roadmap.

What most people believe about the cloud

For most of the last decade, "your data is in the cloud" felt like the safest answer. Your notes, photos, and documents lived on someone else's servers, synced to every screen, backed up automatically. The convenience was real. The default belief was that a remote server is more reliable than your own laptop, and for uptime, it often is.

That belief made sense while the trade was invisible. You got collaboration, sync, and a recovery story, and in exchange you accepted that the primary copy of your work lived somewhere you could not see. Nothing about tapping "save" suggested a problem. The file felt kept. The bargain only shows its edges when the company changes its terms, raises its price, or shuts the service down — and at that point the copy you depend on was never in your hands.

Why the cloud-only bargain fails

The flaw is structural, not accidental. When the primary copy of your data lives on a remote server, your access to your own work depends on a company staying solvent. "In a traditional SaaS model," one 2026 write-up put it, "if the provider goes bankrupt or decides to change their terms of service, your data is held hostage."³

We have watched this happen. A read-later service shuts down and queues every saved article for deletion. A note app changes its pricing or its file format. The pattern is the same each time: the app was the gatekeeper, and the data left when the gate closed. There is a privacy cost too. Centralizing everyone's data creates a single rich target — "In 2025, we witnessed record-breaking data breaches that exposed the personal information of billions," the same write-up noted, "primarily because data was stored in centralized honey-pots."⁴

The quiet reversal of 2026

Local-first is no longer a niche idea among researchers. It now has its own conference track. At FOSDEM 2026 in Brussels, on Sunday 1 February, organizers ran a dedicated devroom titled "Local-First, sync engines, CRDTs," with more than twenty sessions.⁵ A topic gets a room of its own when it stops being speculative and starts shipping.

The engineering caught up to the ambition. Automerge, one of the libraries that makes local-first apps practical, reported in its 3.0 release that it had "cut that down memory usage by over 10x."⁶ Its own benchmark is concrete: "pasting Moby Dick into an Automerge 2 document consumes 700Mb of memory, in Automerge 3 it only consumes 1.3Mb."⁷ Loading a heavy document that "hadn't loaded after 17 hours" now finishes "in 9 seconds."⁸ None of this is the spine of the case; that rests on the idea, not the benchmark. But it is the reason the idea is suddenly buildable. Through 2026 the pattern keeps repeating across the ecosystem: a steady stream of sync engines, each promising the same thing, your data on your device, syncing when it can.

What local-first actually means

Strip out the engineering and one definition does the work. "In local-first software," as the database project RxDB explains it, "the primary copy of your data lives on the client rather than a remote server."⁹ The server, if there is one, becomes a courier between your devices — not the vault that holds the original. You own the original.

This is not the same as "offline mode," though it includes it. The deeper change is about where the source of truth lives. Underneath, libraries called CRDTs let edits made on two devices merge cleanly without a central referee. That is the one technical sentence this needs. Kleppmann's paper laid out the goal in a single line: "In this article we propose local-first software, a set of principles for software that enables both collaboration and ownership for users."¹⁰

The seven ideals, in plain language

The 2019 paper named seven ideals for local-first software. Two matter most for anyone who keeps notes, and both concern durability rather than features. "The Long Now" asks that the documents you make today stay usable for decades, not just until the next subscription lapses.¹ "You Retain Ultimate Ownership and Control" asks that the data be fully yours.

The full list is worth reading once. The seven ideals named in the paper are: "No Spinners," "Your Work Is Not Trapped on One Device," "The Network Is Optional," "Seamless Collaboration with Your Colleagues," "The Long Now," "Security and Privacy by Default," and "You Retain Ultimate Ownership and Control."¹ Most cloud apps satisfy two or three. Local-first software is the attempt to satisfy all of them at once.

What this means for the notes you keep

The practical takeaway is small and old: keep what matters in a format you own, on a device you control. A note saved as plain Markdown on your own machine does not need the company that made the editor to stay in business. The architecture is the insurance. If the primary copy already lives with you, nothing can take it.

If you want to act on this today, three moves cover most of it:

1. Prefer tools where the file lives on your device, not only on a server.
2. Keep important notes in an open, plain-text format like Markdown.
3. Once in a while, confirm you can open your notes with no internet and no account.

That is the whole discipline. Local-first is not a product you buy — it is a question you ask of every tool: if this company disappeared tomorrow, would I still have my work?

Frequently Asked Questions

What is local-first software?

Local-first software keeps the primary copy of your data on your own device rather than on a remote server. As the RxDB project puts it, "the primary copy of your data lives on the client rather than a remote server."⁹ The term comes from a 2019 paper by Martin Kleppmann and colleagues; the server, if any, only syncs copies between your devices.¹

Why are apps moving away from the cloud in 2026?

Three forces converged. Record-breaking 2025 data breaches made centralized "honey-pots" of data look risky. Cloud lock-in left users exposed when services shut down or changed terms. And the engineering matured: FOSDEM 2026 gave local-first its own track,⁵ and sync libraries like Automerge cut memory use by more than 10x, making local-first apps practical to build.⁶

Is local-first the same as offline-first?

Not quite. Local-first includes working offline — the paper calls one ideal "The Network Is Optional" — but it adds ownership and sync.¹ Offline-first describes an app that still works without a connection. Local-first goes further: the primary copy of your data lives on your device, and the network is only there to sync, never to hold the original.

What happens to my data if a cloud app shuts down?

In a cloud-only app, your access can end with the service. In a SaaS model, as one 2026 write-up put it, your data can be "held hostage" if the provider goes bankrupt or changes its terms. We have seen read-later services delete saved libraries on shutdown. In local-first software, the primary copy already lives on your device, so a shutdown cannot take it. The 2019 paper frames the goal as keeping documents usable for "The Long Now."¹

What are CRDTs in local-first software?

CRDTs (conflict-free replicated data types) are the libraries that let edits made on different devices merge cleanly without a central server deciding who wins. Production examples named in RxDB's explainer of local-first are Yjs and Automerge. They are the plumbing that makes local-first collaboration possible; for a note-taker, the point is simply that your device holds the source of truth.

Does local-first mean my data never syncs?

No. Local-first does not mean isolated. The pattern keeps the source of truth on your device and syncs copies between your devices when a connection is available — sync is optional, not absent. The 2019 paper lists "Seamless Collaboration with Your Colleagues" as an ideal alongside ownership.¹ The difference from cloud-only is which copy is authoritative: yours.

Is local-first software more private?

Often, yes — by design. Centralizing everyone's data creates one large target; 2026's record breaches happened "primarily because data was stored in centralized honey-pots." The Kleppmann paper names "Security and Privacy by Default" as one of its seven ideals.¹ Keeping the primary copy on your own device removes that central honey-pot for your own notes.

After a decade of renting space on other people's servers, the most useful question about any tool is no longer how it feels to use today — it is whether your work will still open when the company behind it is gone. A note on your device, in a format you own, already has the answer.

This is the same instinct behind plain text as a durable format: the file outlasts the tool. MNMNOTE keeps your notes on your own device, offline, in open Markdown — a small bet that the architecture, not the brand, is what keeps your work yours. mnmnote.com