"One File. Here Is Everything It Replaces."

Your timesheet is one file. timesheet.db. It sits in your Documents folder. It is about as dramatic as a tax document, and it replaces more than you think.

#A cloud sync service

Most time trackers store your data on their servers and sync it to your devices. That sync is a service. It has an uptime page and an outage channel and a status tweet when it breaks.

owntime does not sync. It does not need to. The file is on your Mac. If you want it on two Macs, you put the file in iCloud Drive or Dropbox or a Syncthing folder, and the sync is handled by a tool you already pay for and already trust. The time tracker does not need its own sync because the file is already syncable.

This means there is no owntime sync status page. There is no "sync failed, your data is conflicted." There is a file, and there is whatever you use to move files between machines, and those are the only two things that can go wrong.

#An account system

To use a cloud tracker, you create an account. Email, password, maybe two-factor, maybe SSO if your company is large enough. The account is the gate between you and your data. If the account is locked, the data is locked.

owntime has no account. You download the app, you open it, you start tracking. There is no sign-up wall, no email verification, no password to forget. The license key is a string you paste in. It verifies offline. There is no account to lock you out because there is no account.

I get asked whether this is secure. The honest answer is that security is not the point. The point is that there is no gate. Your data is not behind an authentication wall. It is behind your machine's login, which is your problem to manage, and that is the correct place for it.

#A backup vendor

Cloud trackers back up your data on their servers. You trust their backup policy, their retention window, their disaster recovery plan. You do not see the backups. You see a settings toggle that says "data protection" and you hope it means what you think.

owntime backs up locally, automatically, about twenty rolling copies, every six hours, to a folder next to the file. You can see them. You can open them. You can delete them. And if you want an off-machine copy, you can mirror the file to your own Cloudflare R2 or S3 bucket on every save, with your keys, to your bucket.

The backup is not a feature you trust. It is a behavior you can verify, because the files are on your disk and you can count them.

#A data hostage

This is the one that matters, and the one that is hardest to see until it is too late.

When your timesheet lives on a vendor's server, the vendor holds leverage. Not because they are malicious. Because the structure makes leverage inevitable. Your history is there. Leaving is expensive. If the price changes, you pay, because the cost of leaving is higher than the cost of staying.

When your timesheet is one file on your disk, the leverage does not exist. You can copy the file, open it in another tool, hand it to your accountant, delete it. The vendor cannot hold it because the vendor never held it. The worst case of a price change is you stop updating the tool and keep using the file you already have.

#The honest trade

One file is not free of responsibility. If you do not back up the file, and your disk fails, the data is gone, and that is on you. If you lose the file, there is no cloud copy to recover. If you want the data on two machines, you set up the sync yourself.

I am telling you this because "one file" sounds like a limitation until you realize what it replaces. It replaces a sync service

you do not control, an account that can lock you out, a backup policy you cannot inspect, and a leverage structure that works against you. In exchange, it asks you to manage a file. For most consultants and small agencies, that is a trade worth making.

#The bottom line

One file. No sync service. No account. No backup vendor you cannot see. No data hostage. Just a SQLite file in your Documents folder, doing the work of four cloud services, and asking you to back it up.

That is what local-first means in practice. Not a philosophy. A file.

Try owntime free for 14 days · See where your data lives · Read how the import works

---