Sync across devices
Pellet can sync between your devices. There is no Pellet server — you run the relay, or you don’t sync at all.
That’s an unusual answer, so it’s worth being plain about the trade: nobody else holds your notes, and nobody can read them. In exchange, someone has to run a small server, and that someone is you.
What it actually is
Section titled “What it actually is”The relay is a single file with no dependencies. It can run on:
- A computer you already leave on — Pellet can host it for you on desktop
- A Raspberry Pi or home server
- A cheap VPS, if you want it reachable from anywhere
Everything it stores is encrypted with keys that only your devices have. Your devices exchange those keys directly with each other when you pair them, and remember them — so the relay is never asked to vouch for anybody.
The practical upshot: a relay can refuse to hand your data over. It can’t read it, change it, or slip anything in.
Setting it up
Section titled “Setting it up”- Run the relay. Settings → Sync relay on desktop, or host it yourself with Docker.
- Set a secret. This stops strangers creating vaults on your relay. Do it before you expose the port, not after.
- Point your first device at it — Settings → Device sync.
- Pair the second device. It shows a code; confirm it on both. That’s the moment trust is established.
When two devices disagree
Section titled “When two devices disagree”Say you edit the same note on a laptop and a phone while both are offline. Both versions are kept. The one that loses becomes a clearly-named conflict copy right next to the original, so you can look at them side by side.
Sync never deletes something because it couldn’t work out what you meant.
If you lose a device
Section titled “If you lose a device”Revoke it from Settings. The vault key rotates, the relay’s copy is purged, and the missing device is holding something that no longer opens anything.
If you’d rather not
Section titled “If you’d rather not”You don’t have to sync at all. A vault in a cloud-drive folder works, with the usual caveat that two devices editing the same file at once can produce that service’s own conflict files rather than Pellet’s tidier ones.