,~~~~~,
(~~~~~~~)
`~~~~~`
,~~~~~,
(~~~~~~~) zipp-nest v···
`~~~~~`
● running (launchd · port 8765)
● listening 192.168.1.42:8765
↑ minecraft-srv 2026-03-11 14:23 snapshot.tar.gz (12.4 MB)
↑ postgres 2026-03-11 13:51 snapshot.tar.gz ( 4.1 MB)
↑ photos 2026-03-10 22:14 snapshot.tar.gz ( 2.3 GB)
↑↓ navigate · enter select · q quit
backup over internet
Run remote backups on your own server with end-to-end encryption. No open ports, no third-party storage — your data stays yours.
)()(
( ●● )
\──/
/||\
,~~~~~,
(~~~~~~~)
`~~~~~`
what you get
available now
zipp-nest listens for incoming backups from zipp. Each job gets its own folder on the server. Snapshots are stored with timestamps — exactly what zipp sent, nothing changed.
After each upload, old snapshots are pruned automatically to match the max snapshots limit you set in zipp. The server stays clean without any manual cleanup.
Every received backup is logged with timestamp, job name and size. Browse the history from the TUI without leaving the terminal.
Press Start server in the TUI — it registers as launchd (macOS) or systemd (Linux) and keeps running after you close the app. No manual daemon setup.
setup
One curl command. Binary drops into /usr/local/bin, scheduler registers itself.
Same one-liner on the server. Open the TUI, press Start server — it registers as a system service and keeps running.
zipp-nest shows a short code under Connection info. Open zipp → Nest → paste it. Both machines are now linked.
Press n on any job to switch to [nest] or [nest+local]. Next scheduled run sends the backup to your server.
installation
Same one-liner. Works on Linux (systemd) and macOS (launchd).
$ curl -sL https://install-nest.zipp.rest | bash
✓ zipp-nest v··· installed
run: zipp-nest
changelog