What 'local-first' actually means
Local-first is an architectural choice: your data lives and gets processed primarily on your device, not on a remote server. When you add a rent payment or a subscription in BillSight, that write happens on your phone. There's no round trip to an API, no server deciding what to do with your numbers.
This is different from most finance apps, which are server-first by default: your data is entered on your phone but stored and processed in a database you don't control, on infrastructure you can't inspect. Local-first flips that. The device is the source of truth, not a cache of it.
Why SQLite specifically
SQLite is an embedded database: it's a library, not a separate server process. There's nothing to start, nothing to crash independently of the app, no port to expose. It reads and writes to a single file on disk, and it does so with real transactional guarantees — the same ACID properties you'd expect from Postgres, just without the network hop.
It's also one of the most deployed pieces of software in the world, running inside billions of phones, browsers, and embedded systems. That track record matters for a finance tracker: we didn't want to build our own storage layer or bet your rent and utility numbers on something unproven. Because everything is local, every read and write is instant and works with zero network connectivity — open the app on a plane and it behaves exactly the same as on Wi-Fi.
The honest trade-off
Local-first by default means no automatic multi-device sync and no cloud backup managed by BillSight. If you set up your fixed costs on your phone, they stay on that phone — install the app on a second device and you start from zero there. This is a deliberate consequence of the architecture, not a bug we haven't gotten to yet.
You're not locked in, though — from Settings you can export all your expenses as a CSV file whenever you want, so they're never trapped on a single device. We think that's a fair trade: you give up managed sync, and in return your financial data never has to pass through our servers at all, because we don't have any.
Why this fits how BillSight is built
BillSight has no account system, no login, and no bank connection — not even as an option. There's no Plaid integration, no OAuth flow to your bank, nothing that could leak your financial identity to a third party. Local-first is the architectural backbone that makes those promises actually true, not just marketing copy.
The whole point of BillSight is to measure your fixed costs, not to collect them. Keeping the database on your device, under your control, is what makes that possible: we simply never see the numbers you type in. Measure, don't preach — that starts with where the data lives.