Performance complaints in accounting rarely show up as a single “error.” They show up as hesitation: the register stutters, the journal post spins, reporting tabs trade patience for coffee breaks. Often the root is architectural — not your Wi-Fi. When every scroll hits a remote API that fan-outs across microservices, you feel it in aggregated latency. When reads hit an indexed file millimeters from the UI thread's worldview (after initial load), the same interactions feel snappier.
Reads dominate real work
Bookkeepers and controllers spend more time looking than posting: search transactions, scan aging, compare categories month over month. Read-heavy workloads punish chatty network models. Local data shifts the bottleneck to device CPU and memory — predictable resources under your control.
Writes still need discipline
Fast posting is not “skip controls.” Double-entry, period locks, audit trails, and reconciliation checkpoints remain essential. Speed without structure is how silent imbalances appear. A well-designed local ledger still validates invariants — it just does not need a round-trip to a shared hosted row for every field blur.
When cloud still makes sense
Remote payroll providers, bank aggregators, and email login necessarily involve servers. The design question is what must be hosted vs what should remain local. Privbooks keeps everyday bookkeeping close while delegating integrations where appropriate. If that trade matches your risk model, compare tiers and try the free Starter path.