Sync runs on a server you own — a home machine, a small VPS, whatever you trust. Your phone encrypts every entry before it leaves, so the server only ever stores sealed blobs it cannot open. Setup takes four steps.
Anything that runs Node 20 or newer and can be reached by your devices: a spare Mac mini, a Raspberry Pi on your home network, or a small rented server. It needs very little — the whole vault is a single file.
Get the source from GitHub and start it. The README has the full options — port, data folder, and running it as a background service.
In Nisshi, open More → Data Backup → Sync, enter your server's address and the enrollment code it gives you. After that first time, your journal syncs on its own. Apple Watch follows your phone.
One server can hold several journals. Share a single join code with family or a small team; each person's vault is keyed by a random account id and sealed with their own password.
Even if someone took the server — or the SQLite file on it — they'd hold ciphertext and random ids. No titles, no dates in the clear, no key.
How the encryption works →No. Nisshi is fully functional offline. Encrypted backups to a file cover most people with one phone.
The most recent change wins. Anything worth a second look shows up under Review sync conflicts.
Copy its single SQLite file. It's already encrypted, so the copy is as safe as the original.
No. There is no Nisshi cloud, the server makes no outbound requests, and the source is public so you can check.