Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host Zerobyte
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A web interface for scheduling and monitoring encrypted backups, built on restic. Define volumes to back up (local directories, or NFS, SMB, WebDAV and SFTP shares it mounts itself), create repositories on local disk, S3-compatible storage, Google Cloud Storage, Azure Blob or any of rclone's 40+ remotes, then attach schedules with cron-style timing, retention policies and pre/post webhooks. It restores from the browser and sends notifications through Shoutrrr-supported services. It is a 0.x project and its README warns that major changes can land between versions.
Pick Zerobyte when you want a modern web interface over restic with volumes, repositories and schedules as separate objects, and the ability to mount NFS, SMB, WebDAV or SFTP shares and back them up without scripting. It is AGPL-3.0 TypeScript running on Bun; repositories can be local disk, S3-compatible storage, Google Cloud Storage, Azure Blob or any rclone remote, with encryption, compression, retention policies, backup webhooks and notifications. Our snippet adapts the README's "simplified setup (no remote mounts)" compose file, pinned to `ghcr.io/nicotsx/zerobyte:v0.44.0` (released 2026-10-31), with `APP_SECRET` generated into `.env`; the README's default file also adds `SYS_ADMIN` and `/dev/fuse` for remote shares. We did not find an upstream RAM minimum, so our 512 MB floor is an estimate. Backrest is the closest catalog neighbour, a restic web UI built around plans and cron; Zerobyte adds remote-share mounting and organisations, and is much newer. restic, Kopia and borgmatic have no web interface and Duplicati uses its own format.
What you need
Any VPS with at least 512 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# Zerobyte — web UI for restic — adapted from the README's "simplified setup (no remote mounts)" compose file — pinned to v0.44.0mkdir -p zerobyte-data backup-sourceecho 'hello from SelfHost Atlas' > backup-source/hello.txtprintf 'APP_SECRET=%s\nBASE_URL=http://localhost:4096\n' "$(openssl rand -hex 32)" > .envcat > docker-compose.yml <<'EOF'services: zerobyte: image: ghcr.io/nicotsx/zerobyte:v0.44.0 container_name: zerobyte restart: unless-stopped ports: - "4096:4096" environment: - TZ=UTC - BASE_URL=${BASE_URL} - APP_SECRET=${APP_SECRET} volumes: - ./zerobyte-data:/var/lib/zerobyte - ./backup-source:/mydataEOFdocker compose up -dtimeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:4096/api/healthcheck; do sleep 3; done'# → http://SERVER_IP:4096 — first load asks you to create the admin account. Browsing from another machine? Set BASE_URL in .env to exactly that address (e.g. http://SERVER_IP:4096) and run docker compose up -d again, or login will fail. Back up .env: APP_SECRET encrypts the stored credentials
Zerobyte's README and installation docs flag these before you rely on it:
non-negotiableThe README states Zerobyte is still a 0.x project and subject to major changes from version to version. Pin an exact tag as we do (the README's example uses a moving minor tag) and read release notes before upgrading.
non-negotiableLogin depends on BASE_URL. The docs say to set it to the exact address you browse (http://192.168.1.50:4096 for IP access, or an https:// domain, which turns on secure cookies). Our snippet defaults to http://localhost:4096 in .env so it can start unattended; change it and run docker compose up -d again before using it from another machine.
non-negotiableThe README strongly discourages exposing Zerobyte to the internet; if you do, bind 127.0.0.1:4096:4096 and put an authenticated tunnel in front. Authenticated organisation members are trusted operators for repositories, volumes, schedules and restores, as there is no fine-grained role system.
non-negotiableAPP_SECRET encrypts sensitive data in the database, so keep .env and the ./zerobyte-data directory (/var/lib/zerobyte, which the README says must not be a network share) in your own backups, and use the recovery keys guide for repository keys. Back up the sample ./backup-source mounted at /mydata by adding it as a Directory volume.
Zerobyte used 93 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 512 MB.
Is the Zerobyte install snippet verified?
The Zerobyte install snippet is marked verified on Ubuntu 26.04 (Nov 2026).