The Cloud Gave Us Convenience — At a Cost

Over the past decade, nearly every piece of software we use has migrated to the cloud. Our notes, documents, calendars, and even our creative work now live on servers we don't own or control. The trade-off felt obvious: seamless sync, access from anywhere, automatic backups. Who could argue with that?

But the cracks are starting to show. Services get acquired, shut down, or simply change their pricing overnight. Remember when Evernote was the gold standard for note-taking? Or when Google killed Reader and took an entire ecosystem with it? Cloud-first software makes you a tenant, not an owner.

What Is Local-First Software?

Local-first software is an approach where the primary copy of your data lives on your device — not on a remote server. Collaboration and sync are still possible, but they're treated as optional layers on top of local ownership, not the foundation.

The concept was articulated clearly in a 2019 paper by Ink & Switch, which outlined seven ideals for local-first apps:

  • Fast: No waiting for network round-trips — operations happen instantly.
  • Multi-device: Your data syncs across your own devices.
  • Works offline: Full functionality without an internet connection.
  • Collaboration: Real-time or async collaboration remains possible.
  • Long-lived: You can open files decades later, without vendor lock-in.
  • Privacy: Your data isn't being mined by a third party.
  • User control: You own and can export everything.

Real Tools Embracing the Local-First Philosophy

This isn't just theoretical. A growing ecosystem of tools is putting these principles into practice:

  • Obsidian — Notes stored as plain Markdown files on your drive.
  • Logseq — Open-source knowledge graph that works entirely with local files.
  • Anytype — A local-first alternative to Notion with end-to-end encryption.
  • Beeper / self-hosted alternatives — Taking control of your own messaging history.

The Technical Challenge: CRDTs

The hardest problem in local-first software is conflict resolution. When two devices edit the same document offline and then sync, whose version wins? The answer lies in a data structure called a Conflict-Free Replicated Data Type (CRDT). CRDTs mathematically guarantee that two copies of data, edited independently, can always be merged without conflicts.

Libraries like Automerge and Yjs are making it much easier for developers to build CRDT-powered apps, which means we're likely to see a wave of local-first tools in the coming years.

Should You Make the Switch?

Going fully local-first has trade-offs. Setup is sometimes more involved. Sharing with others can require extra steps. But for data you care about — your writing, your knowledge base, your creative work — the resilience and ownership you gain are well worth it.

Start small: move your notes to a plain-text or Markdown-based system. Back up to your own storage. The goal isn't to reject collaboration or convenience — it's to make sure you are always in the driver's seat.