Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host Backrest
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 UI and scheduler built on restic: create or import restic repositories, define backup plans with cron schedules and retention policies, browse snapshots and restore files from the browser, and run prune and check operations on a schedule. It supports every restic storage backend (S3, B2, Azure, GCS, SFTP, local and rclone remotes), command hooks around backups and notifications to Discord, Slack, Shoutrrr, Gotify and Healthchecks.
Pick Backrest when you already trust restic but want a browser instead of cron lines and shell scripts. It is a web UI and scheduler wrapped around the restic CLI: you create a new repository or import an existing one, define backup plans with a cron or interval schedule and a count- or time-based retention policy, browse snapshots and restore files from the UI, and schedule prune and check operations. It works with every restic backend (S3, B2, Azure, GCS, SFTP, local paths and rclone remotes), runs command hooks before and after backups and can notify Discord, Slack, Shoutrrr, Gotify and Healthchecks. It is GPL-3.0 Go. Our snippet is the README's Compose example with the Docker Hub image pinned to a release tag and the upstream volume layout, including the rclone configuration folder, kept under `./backrest`. We did not find an upstream RAM minimum, so our 128 MB floor is an estimate. The catalog's restic is the bare command-line tool this wraps, and Kopia and Duplicati ship their own interfaces and repository formats instead.
What you need
Any VPS with at least 128 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Backrest's README and getting-started guide flag these before you rely on it:
non-negotiableFirst-time setup asks you to create a username and password; the guide says authentication can be disabled for local installs or behind an authenticating reverse proxy, and that to reset credentials you delete the users key from config.json (ours is ./backrest/config/config.json) and restart. The container listens on 0.0.0.0:9898 over plain HTTP, so put a TLS reverse proxy in front before exposing it.
non-negotiableThe guide warns to keep a copy of your repository credentials and encryption keys somewhere safe, because losing the repository password means you cannot restore. It suggests storing the whole Backrest configuration in a password manager or encrypted storage; the config and the data directory both sit under ./backrest, so back that up too.
non-negotiableBackrest can only back up what the container can see. The README's Compose example mounts the source data at /userdata and local repositories at /repos; our snippet creates empty ./backrest/userdata and ./backrest/repos folders as placeholders, so replace them with the real paths you want to protect. A repository on the same disk is not an off-site backup.
non-negotiableThe README's example uses ghcr.io/garethgeorge/backrest:latest; the image is also on Docker Hub with a tag per release, and we pin v1.14.1 (released 2026-07-12). The default image includes rclone and common Unix utilities, and a -scratch variant (v1.14.1-scratch) is the minimal build.
Backrest used 9 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 128 MB.
Is the Backrest install snippet verified?
The Backrest install snippet is marked verified on Ubuntu 26.04 (Nov 2026).