"How a Desktop App Works With No Servers At All"

You open most apps

and somewhere in the background, they talk to a server. They sync your data. They check your license. They send analytics. You do not see it. It just happens.

owntime does not do that. There is no server. The app runs on your Mac, reads and writes a local file, and never phones home. I want to explain what that actually looks like in practice, because "no server" sounds like a limitation until you realize what it replaces.

#What happens when you open the app

You open owntime. It reads a file from your disk. ~/Documents/owntime/timesheet.db. That file is your entire timesheet, your clients, your projects, your entries, your invoices. The app loads it into memory and shows it to you.

There is no login. There is no sync spinner. There is no "loading from the cloud." The file is already there, on your machine, and the app opens it. If your internet is down, the app opens exactly the same way, because the internet was never part of the opening.

#What happens when you track time

You start the timer. The entry is written to the local file. When you stop, the entry is saved. The save goes to your disk, not to a server. If you are offline, on an airplane, in a basement with no signal, the entry still saves, because there is nowhere else for it to go.

There is no sync conflict. There is no "this entry was modified on another device, which version do you want?" There is one file, on one machine, and the app is the only thing writing to it. The problems that come from syncing data between devices do not exist because there is no syncing.

#What happens when you invoice

You build an invoice from tracked entries. The entries are in the local file. The invoice is built locally. The PDF is generated locally. You send it yourself, from your own email, to your own client. The app does not send it for you, because there is no server to send it from.

This is the part that surprises people. The app builds the invoice. You send it. There is no "the app emailed your client" because the app has no email server and no permission to send mail on your behalf. The invoice is a file on your desk. What you do with it is your business.

#What happens when you quit

You close the app. Nothing is uploaded. Nothing is synced. The file is on your disk, in the state you left it. If you never open the app again, the file is still there. If the app disappears from the internet tomorrow, the file is still there. You can open it in any SQLite browser, export it to CSV, hand it to your accountant. The app was a reader for the file. The file does not need the app.

#What you gain

Speed. No network call means no waiting. The app opens fast because it is reading a local file, not downloading your data from a server.

Offline. No internet required. The app works the same online and offline because the only thing a network connection adds is downloading updates.

Privacy. No server means no server to breach, no telemetry to collect, no data to hand over in a legal request. Your timesheet is not in anyone's cloud. It is on your disk.

No account. No email, no password, no two-factor, no account that can be locked or hacked or used to market to you. The app does not know who you are.

#What you lose

Sync. If you want your timesheet on two machines, you set up the sync yourself. iCloud Drive, Dropbox, Syncthing. The app does not do it for you. This is the real trade, and for some people it is a dealbreaker.

Collaboration. If two people need to edit the same timesheet 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, this is not the tool.

Off-machine backup. If your disk fails and you have not copied the file somewhere, the data is gone. The vendor cannot recover it because the vendor never had it. You are responsible for the backup.

#The honest summary

A desktop app with no servers is fast, offline, private, and account-free. It does not sync, does not collaborate, and does not back itself up. Those are not bugs. They are the same architectural choice seen from different angles.

If your work is primarily on one machine, if you bill from tracked time, and if you want to own your data, the gains outweigh the losses. If your work is across multiple machines and people, the losses are real and you should use a tool built for that.

Try owntime free for 14 days · See where your data lives · Read the honest comparison with Toggl

---