Local-first billing software, explained

The two architectures, plainly

In a cloud-first product, the authoritative copy of your data sits on a server the vendor runs. Your device holds a cache of it. When you make a bill, the app is really asking that server to record one.

In a local-first product, the authoritative copy sits on your own device. Making a bill is a local operation that completes whether or not anything else in the world is reachable. Any copy elsewhere is a backup, not the original.

Everything else people argue about downstream of this — offline behaviour, who can read your data, what happens when you stop paying — follows from that one difference about where the real copy lives.

When cloud-first is genuinely the better choice

This deserves saying properly rather than being waved away, because for some businesses cloud-first is the right answer and local-first would be a mistake.

If several locations need to see the same live figures at the same moment, cloud-first does that natively and local-first has to work at it. If you need to check today's sales from another city on a different device, that is what a server-side copy is for. If a dozen staff across branches need individual logins with different permissions, that is a cloud-shaped problem.

And if losing your phone would mean losing your business records, a vendor-held copy is a real safety net.

What local-first gives you instead

Billing does not depend on a signal. That matters more in practice than it sounds on a feature list: a basement shop, a highway counter, a small town at eight in the evening.

Your data is not leverage. If the authoritative copy is on the vendor's server, the terms under which you access your own records are the vendor's to change — at renewal, after an acquisition, or when the pricing page quietly updates.

And there is no breach of a central database to be caught in, because there is no central database holding your customers and your sales.

The honest costs of local-first

Backups become your responsibility rather than something that happens invisibly. A local-first app can make this easy, but it cannot make it automatic in the way a server can, because the data has to be sent somewhere you own.

Multi-device access is harder. Reading today's figures from a different phone in a different city is exactly the case cloud-first is built for.

And losing the device matters more. A restore is only as good as the last backup, which is why the backup setup is the one step in a local-first product worth doing on day one rather than eventually.

“Works offline” is not the same claim

A great many cloud-first products advertise an offline mode. That usually means a holding pen: your work is stored locally and synced when the connection returns.

It mostly works. The difference shows up when a sync fails, because two copies now disagree and something has to decide which one wins. Local-first does not have that class of problem, because there was never a second copy competing to be authoritative.

The practical test is the same either way: put the app in flight mode and try to complete a real sale.

Where Data Swaraj comes in

Data Swaraj is the name Vanij uses for the principle: your business data belongs to you, lives with you, and stays reachable regardless of what happens to us commercially.

Concretely that means the records live on your device, backups go to storage you own rather than to us, and exporting your own data is free on every plan, including the free one. That last point is the one that decides whether the principle is real: data you cannot get out is not data you own.

How to tell which one a product actually is

Marketing copy is not reliable here, because “secure” and “your data is safe with us” are said by everyone. Three questions settle it.

Can you create a bill with the device in flight mode? Where is the authoritative copy of your customer list right now? And on the day you stop paying, can you still open the app and export everything?

Those answers are checkable, and they tell you more than any feature comparison will.