"What 'Local-First' Means for Your Business Data"

#The definition

Local-first means the software stores your data on your machine, not on the vendor's server. Your timesheet is a file at a path you can point to. ~/Documents/owntime/timesheet.db. The app reads and writes that file directly. There is no cloud copy, no sync service, no background upload.

The app still works if the internet goes down. It still works if the vendor's servers go down. It still works if the vendor goes down. The only thing that can stop it is your own machine failing, and even then, the file is yours to back up.

That is the whole definition. Everything else is a consequence.

#What local-first guarantees

**You can read your own data without the app

.** The file is [SQLite](/help/your-data), one of the most widely supported database formats in existence. You can open it in any SQLite browser, query it with a script, or hand it to your accountant as a CSV export. You do not need the vendor's permission and you do not need an export function that may or may not include everything.

You can leave without losing anything. When you stop using the tool, the data does not stay behind on a server you can no longer reach. It is already on your disk. There is no "request your data" process. You already have it.

The vendor cannot hold your data hostage. There is no server holding a copy, so there is no copy to lock you out of during a billing dispute. The leverage that makes subscription repricing painful, your history is trapped and leaving is expensive, structurally does not exist when the file is already yours.

The app works offline. No wifi, no cell signal, no VPN. The timer ticks, the entries save, the invoice generates. The only thing you cannot do offline is download updates, and updates are signed and optional.

#What local-first does not guarantee

I want to be precise about this, because the term gets used to imply things it does not mean.

Local-first does not mean the software is good. It does not mean the features are complete. It does not mean the developer will keep shipping. It only means where the data lives. You can have a local-first app that is buggy, abandoned, or missing the feature you need. The data location is one axis. The quality is another.

Local-first does not mean you are backed up. If your disk fails and you have not copied the file somewhere, the data is gone. The vendor losing your data is impossible. You losing your data is still your responsibility. This is the trade, and it is the correct place for it, but it is a trade.

Local-first does not mean collaborative. If two people need to edit the same file at the same time, a local file is the wrong model. That is what servers are for. If your workflow needs live multi-user editing, local-first is a constraint you will feel.

#Why it matters for a time tracker

For most software, local-first is a preference. For a time tracker, it is structural.

A time tracker holds your billing memory. Every client, every project, every hour you billed, going back years. That history is the thing that makes leaving expensive, and the thing a vendor can leverage when they reprice you. If the history lives on the vendor's server, the vendor holds the leverage. If it lives on your disk, you do.

This is the specific case where local-first is not a nice-to-have. It is the difference between "I can leave whenever I want" and "I can leave whenever I am willing to rebuild three years of billing history." One of those is a real choice. The other is a hostage situation with a monthly invoice.

#The test

If a tool claims to be local-first, ask one question: can I find the file?

Open your file browser. Navigate to where the data lives. If you can point to a path and see the file, the claim is probably true. If you cannot find a file, or the data only exists inside the app with no visible path on your disk, the claim is marketing.

For owntime, the path is ~/Documents/owntime/timesheet.db. It is there. You can see it. You can copy it. That is the whole claim, verified.

Try owntime free for 14 days · See where your data lives · Read the privacy commitment

---