Founders and bookkeepers rarely ask vendors the uncomfortable question: where is the system of record? If the answer is “our servers, always,” you may still have a great product—but you should understand the trade. You are renting continuity. Renting can be fine when the vendor is stable, pricing is predictable, and exports are complete. It is painful when pricing changes, accounts are disrupted, or exports omit the relational detail your CPA needs to re-audit a year.
Three levels of “export” (only one is a ledger)
- Report exports (PDF/CSV): useful for sharing, not sufficient to reconstruct the full posting history and subledgers.
- Transaction dumps: better, but still require careful schema mapping—especially for inventory layers, tax basis, and partially paid invoices.
- Database ownership: a portable relational file (for example SQLite) that contains the same truth the app uses—not a prettified subset.
This distinction matters at the worst time: diligence, dispute, or forced migration. If your only artifact is reports, you will spend weeks rebuilding truth. If your artifact is the database, you at least have a queryable spine. See browser SQLite portability for what that looks like in practice.
Pricing shocks are a continuity risk
Accounting software is sticky by design: your team trained on it, your bank feeds point at it, your CPA expects a rhythm. Vendors know that. The mitigation is not cynicism—it is contracting with your eyes open: know your export path, keep periodic offline archives, and avoid workflows that only exist inside one proprietary automation bubble.
Privacy: what must be remote vs what can stay local
Some functions inherently involve third parties: email login, bank aggregation, payment processing. The design question is what remains local after those integrations. A local-first ledger keeps everyday GL reads/writes on device after load, which reduces the “always streaming my books” posture some teams want to avoid. For fleet and field operations, that can be load-bearing; read local-first ledgers for fleets and logistics.
A buyer checklist that survives stress
- Can I obtain a full database backup on demand without a support ticket?
- Do bank rules and registers survive export/import round trips for my workflow?
- What happens if I downgrade or cancel paid features—do I lose read access to history?
- Can my CPA reproduce the trial balance from exports without proprietary tooling?
How Privbooks frames the trade
Privbooks is explicit: your primary company file is local in the browser, with exports and optional cloud snapshots for teams that want off-device continuity—without making the vendor-hosted GL the only copy by default. If that matches your risk model, try the product and validate backups on a cadence that fits your operation.