Most apps today are “cloud-first”: your data lives on the provider’s servers, and the app is just a window into it. Local-first flips that order — your data belongs to your device first. For sensitive data like personal finance, that difference is worth paying attention to.

What does local-first mean?

A local-first app has three core traits:

Stored on device first: every record is written straight to your device’s storage.
Works offline: no connection needed to use it fully.
Syncing is optional: only when you sign in is your data backed up for use across devices.

How is it different from cloud-first?

With a cloud-first app, losing your connection often means losing access, and your data always sits on a third party’s servers. With local-first, you keep control: the app works on its own, and you decide when — and whether — your data goes to the cloud.

Why it matters for your finances

More private: income, spending and assets are deeply personal. Keeping them on your device reduces exposure compared to pushing everything to the cloud by default.
Always available: logging an expense with weak signal? No problem.
Fast: local reads and writes are near-instant, with no waiting on the network.
You own your data: export, back up or delete it any time.

Is there a trade-off?

Local-first doesn’t mean “never use the cloud”. To sync between your phone and tablet, you still need a middle point. The difference is that you choose to turn syncing on, rather than it being the default — and even then, the data belongs to your own account.

eevas is built local-first

eevas stores every transaction, asset and budget right on your device and works fully offline. Only when you want to sync and back up/restore across devices do you need to sign in. Receipt photos are only sent temporarily for AI to read — never stored for syncing.

In short: your money, your data — it should stay on your device. That is the philosophy eevas is built on.