Server or desktop
One product, two answers to where the database lives. The ledger, the rules and the screens are the same; what differs is who else can be in the workspace and what the machine is allowed to talk to.
| Aspect | Hosted, or on your server | Desktop |
|---|---|---|
| Price | On the hosted service, the Free plan or Personal and Pro (see Plans and prices); during the beta, founders have Pro free until 31 March 2027. A server you run yourself is yours to pay for: the reference Google Cloud deployment, sized for its beta, costs about $58 a month; a small one with no warm instances costs about $14 with its database running and about $6 with it stopped. | Free, with nothing to pay to run it: it runs on your own computer, and its AI runs on a key of your own. |
| Sign-in | Firebase Auth: email and password, or Google. | A token the application mints per launch. No account anywhere. |
| Database | A PostgreSQL you run, with separate logins for the application and the audit reader. | PGlite, embedded in the application, in a data directory on your disk. |
| Documents | Object storage buckets you own, one per kind of document. | Directories beside the data, one per kind of document. |
| Members | Invite family, an accountant, a property manager, with access per book. | One owner, who may keep several workspaces. |
| Intake | Telegram and email, received by a public endpoint and processed by a private worker. | Files you upload, and what the application fetches when you allow its host. |
| Bank connections | Mercury, SimpleFIN, Wise, Enable Banking, Teller, Plaid and Interactive Brokers, synced with Sync now. Automatic sync is not running on the hosted service yet. | Mercury, SimpleFIN, Wise, Enable Banking and Interactive Brokers, synced while the app is open, once you allow each service's host. |
| Network | Whatever your server can reach: banks, the ECB, your AI provider. | Nothing, until you allow a host by name in the allowlist file. Bank, rates, AI and the update check each need their host allowed. |
| Backups | Your database's own, plus a workspace archive the operator can export, stamped with the release it came from. | A copy of the data directory daily and before every update, the newest three kept beside it and restored from Settings; and a workspace export of your own, to a file you choose. |
| Updates | You deploy each release yourself, upgrading the database to it first; the API refuses to start against a database at a different release. | Today's builds are made from source, unsigned, and do not update themselves; a newer build backs up your data before it migrates the database. The update check stays off until you allow its host. |
Getting either
Both are early. The reference server deployment is invite-only and joined by invitation from a workspace owner; the desktop edition is built from source today, since the signed release pipeline needs certificates that are not yet in place.
A workspace moves with its history intact and every old login detached, into an empty installation at the same release. The desktop app exports one from Settings and restores one before its first workspace; on a server the operator exports with the archive command, and that file restores into a desktop app or an empty server installation. Members of a server workspace cannot yet export it from the app.