HenkSuiteTL;DRA local-first app stores your data on your own device first, and treats the internet as optional. It opens instantly, works offline, keeps your files even if the company disappears, and only syncs to the cloud when you choose to. Think Obsidian, Logseq, Anytype, or HenkSuite - not Google Docs or Notion.
Quick answer: a local-first app, in one sentence
A local-first app is software where the canonical copy of your data lives on your machine, not on a vendor's server. The cloud, when used at all, is just a sync helper - not the source of truth.
That single design choice changes almost everything else: speed, privacy, offline behaviour, longevity, and how much you actually own.
The simple definition of local-first
Where your data actually lives
In a normal cloud app, your data lives on a server in some data center. Your laptop is just a window into that server. Close your browser tab, lose your internet, or watch the company shut down - and your data is gone or frozen.
In a local-first app, the opposite is true. Your data is a real file (or a local database) on your disk. The app reads and writes that file directly. The cloud, if it exists at all, is only there to copy that file to your other devices.
The network is optional, not required
This is the cleanest mental test for whether something is local-first: turn off your Wi-Fi and try to use it. A local-first app doesn't notice. A cloud app shows a spinner, an error, or a polite "you're offline" banner.
A useful gut-checkIf the app stops working when your internet does, it isn't local-first. It's a cloud app with a thin offline shim.
Local-first vs cloud apps: the real difference
How cloud apps work today
Most popular productivity tools - Google Docs, Notion, Asana, Trello, Airtable - are cloud-native. The architecture looks like this:
- Source of truth: a database in the vendor's data center.
- Your device: a thin client (browser tab or wrapper) that asks the server for everything.
- Every keystroke: a small network round trip.
- Your data: technically yours, practically rented.
How local-first apps flip the model
Local-first inverts that stack:
- Source of truth: a file or local database on your machine.
- Your device: the actual app, doing the actual work.
- Every keystroke: writes to local storage in microseconds.
- Your data: yours - inspectable, backupable, portable.
The cloud doesn't disappear. It just stops being the bottleneck. Sync, sharing, and collaboration are layered on top of the local copy, not in front of it.
The seven Ink & Switch properties
The phrase “local-first” was coined by the research lab Ink & Switch in their landmark 2019 essay. They proposed seven properties that distinguish local-first software from cloud-only software. Most modern local-first apps aim to satisfy as many of them as possible.
The full checklist
- 1. No spinners: work proceeds at the speed of your hardware, not the network.
- 2. Your work is not trapped on one device: sync to other devices when you want.
- 3. The network is optional: the app works fully offline.
- 4. Seamless collaboration with others: sharing is possible without a central authority.
- 5. The long now: your data outlives the company.
- 6. Security and privacy by default: end-to-end encryption is the norm, not a paid add-on.
- 7. You retain ultimate ownership and control: nobody can take your work away.
Few apps hit all seven perfectly. The point of the list is direction, not a passing grade. An app that scores 5/7 is dramatically more durable than one that scores 0/7.
Examples of local-first apps in 2026
HenkSuite: an all-in-one local-first suite
HenkSuite is a good example because it covers the kind of features people usually associate with cloud-only tools - projects, tasks, notes, calendar, mail, spreadsheets, time tracking, habits, goals, finance - while keeping every byte in a local SQLite database on your machine.
It's built on Tauri 2, so the desktop app sits around 50MB of RAM, opens instantly, and reads and writes to the database in well under a millisecond. The license is one-time, the app is offline by default, and the database file is just a regular file you can copy, back up, or move.
Obsidian, Anytype, Logseq and friends
Other well-known local-first apps include:
- Obsidian: Markdown notes on disk with a strong plugin ecosystem.
- Logseq: outliner-first notes app, also Markdown-based.
- Anytype: end-to-end encrypted, peer-to-peer Notion-style workspace.
- AppFlowy: open-source, local-first take on the Notion model.
- Linear (offline mode): not fully local-first, but a serious step in that direction.
Pros and cons of going local-first
Local-first isn't magic. It comes with real tradeoffs. Here's an honest split.
- ✓Instant performance - sub-millisecond reads and writes from local storage
- ✓Works fully offline, on planes, in basements, or behind shaky Wi-Fi
- ✓Your data is a real file you own, back up, and inspect
- ✓Privacy by default - no third party reading your notes or training on them
- ✓App keeps working even if the company disappears
- ✓Often a one-time license instead of an endless subscription
- ✕Real-time multiplayer editing is harder than in pure cloud apps
- ✕Sync setup can be slightly more involved (iCloud, Dropbox, or vendor sync)
- ✕You are responsible for your own backups
- ✕Mobile parity is sometimes behind desktop
- ✕Less "magic" AI features that depend on a server fleet
FAQ: local-first apps
Do local-first apps need the internet at all?
No. By definition, a local-first app works fully offline. It might use the internet for sync, license checks, or optional features, but the core experience does not depend on it.
How do they sync between devices?
Most local-first apps offer a few options: a vendor-hosted sync service (often end-to-end encrypted), a third-party file sync tool like iCloud Drive or Dropbox, or peer-to-peer sync. The key is that sync is a layer on top of your local data, not a replacement for it.
Who should use a local-first app?
Anyone who values speed, privacy, offline use, or long-term ownership of their work. That tends to mean writers, researchers, developers, indie hackers, freelancers, and anyone tired of paying monthly subscriptions for tools that go down whenever their ISP does.
The bottom line
A local-first app is software that puts your device first and the cloud second. That single architectural choice unlocks speed, privacy, offline work, and real ownership of your data - the things cloud apps quietly traded away over the last decade.
If you want to feel the difference yourself, install HenkSuite and watch how a productivity app behaves when there's no server in the way.
About the author
Emilia is the founder of HenkSuite. She builds productivity tools because the internet has 47 of them and none of them feel fast, private, or finished.