Record in Mirato
Type a sentence and confirm the account and amount.
Mirato does not upload your ledger to a server. It writes confirmed transactions back to the Beancount folder you authorized, then Syncthing, a cloud drive or another file-sync tool can carry those files to your other devices.
Type a sentence and confirm the account and amount.
The transaction stays in the local file you authorized.
Syncthing or another tool syncs the whole directory.
Open the same ledger and keep reconciling and recording.
You can keep using Fava, bean-check or any other Beancount tool with the same ledger.
The animation can be reduced or disabled; the flow, code and explanations remain fully readable.
2026-10-01 * "Blue Bottle" "Latte" Expenses:Food:Coffee 32.00 CNY Assets:Bank:Checking 2026-10-01 balance Assets:Bank:Checking 4,218.50 CNY
Mirato is a local ledger app, not a hosted ledger service. It requests no network permission, has no account system and has no server that stores your ledger for you. Syncing, backups and transfer between devices are handled by the external tool you choose.
These labels describe current recommendations and research, not native Mirato integrations.
Good for syncing a local ledger directory between your phone, computer and your own devices. Files move between your devices instead of being uploaded to Mirato.
Useful if you already have a NAS or WebDAV service. Android, iOS file providers and conflict handling still need real-device testing.
Whether iCloud, Google Drive or another provider can reliably expose a ledger directory depends on the OS and the specific file provider.
Useful when you want history and reviewable changes, but mobile workflows and merge conflicts are more complicated.
A sync tool moves files; it does not understand Beancount transactions. Treat it as a file-transport layer to avoid surprises.
Sync keeps file states close across devices. A backup is an independent copy you can return to after a mistake. Sync does not replace backup.
This page lists WebDAV as a candidate only. We need real testing across Android, iOS and different services before deciding whether native integration is appropriate.
If you want rules, aliases or import drafts shared across devices, include it in the sync scope. Back it up first and remember that it can contain local state.
Tell us which devices and services you use and what problem you encountered through Mirato's feedback channel. Real use cases help set the next priority.