Nisshi 日誌
Nisshi Sync · self-hosted

Every device in step.
Nobody in the middle.

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.

Runtime
Node 20+
Storage
One SQLite file
Outbound calls
None
Price
Free & open source
Setup — four steps
  1. 01

    Pick a machine you trust.

    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.

    Home computer Raspberry Pi NAS Small VPS
  2. 02

    Install the server.

    Get the source from GitHub and start it. The README has the full options — port, data folder, and running it as a background service.

    Terminalon your server
    $ git clone https://github.com/encorbatao/nisshi-sync-server
    $ cd nisshi-sync-server
    $ [INSTALL & START COMMAND — from the README]
  3. 03

    Connect your iPhone.

    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.

    ✓Encrypted on the phone before upload
    ✓Disconnect any time — your data stays on-device
    ‹ Data Backup
    Sync
    SERVER
    https://[your-server]
    ENROLLMENT CODE
    Connect
    Entries are encrypted on this iPhone before they're sent. The server never receives your key.
  4. 04

    Invite the household — or don't.

    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.

    Sync now
    Push and pull immediately.
    Verify sync
    An integrity check, end to end.
    Review conflicts
    Last write wins; you can check.
    Disconnect
    Forget the server, keep your data.
What your server actually stores

The same entry,
on each side of the wire.

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 →
On your iPhone
·Pick up prescription
○Dentist — Dr. Smith, 08:30
sealed on device ↓
On your server
account 7f3a·c91e·04bd·…
blob q8Zt0mVx3Kc+R2pLwN9eH1yUf6sJbA…
blob Lr4Wc7nQ0dTzE5kYvX2mPa8hGsB…
Good to know

Before you start.

Do I need sync at all?

No. Nisshi is fully functional offline. Encrypted backups to a file cover most people with one phone.

What if two devices edit the same entry?

The most recent change wins. Anything worth a second look shows up under Review sync conflicts.

How do I back up the server?

Copy its single SQLite file. It's already encrypted, so the copy is as safe as the original.

Can you see my data?

No. There is no Nisshi cloud, the server makes no outbound requests, and the source is public so you can check.

Ready? The source and README are on GitHub.
Stuck somewhere? Write to info@nisshi.app.
View sync server