What “local-first” actually means for your data

“Local-first” gets used as a buzzword, so here’s the plain version, because it’s the single idea most of Sedonis is built on.

The usual way: cloud-first

Most apps are cloud-first. Your data lives on their servers, and your device is basically a window onto it. Open the app and you’re really looking at their copy. That’s why so many tools stop working the moment your connection drops, and why a breach on their end is a breach of your data.

It’s convenient. It also means the most important copy of your information isn’t yours.

The other way: local-first

Local-first flips the default. Your data lives on your device first. The app works there: online or off, fast, with no spinner waiting on a server. Syncing still happens, so your phone and laptop stay in step, but sync is a background convenience, not the thing holding your data hostage.

Two things fall out of that:

• It’s faster and it works offline, because you’re not round-tripping to a server for every action.
• You can encrypt before you sync. Since the real copy is already on your device, sensitive data can be sealed there and only leave as ciphertext. That’s how a Sedonis Vault stays readable to you and no one else, not even us. (More on how that works in what end-to-end encryption means.)

Why it matters for a business

For a business, the data is the sensitive part: your revenue, your clients, your margins. Local-first means the working copy is yours, on your machine. Turn on Vault and that information never sits in plain text on a server: it leaves your device only in a form you hold the key to. In Standard, the default, the synced copy is readable by us, like most software.

That’s the foundation under everything we build. If you want to see it in practice, start with Notch or Turnover: one app is free, no card.