Backrest

Backrest is a web UI and orchestrator for Restic, helping users create, schedule, and restore file backups.

  • Backup
  • Tools & Utilities
Backrest is a web UI and orchestrator for Restic, helping users create, schedule, and restore file backups. It is a web-accessible backup solution built on top of restic, providing a WebUI that wraps the restic CLI to make it easy to create repositories, browse snapshots, and restore files. It can also run in the background, taking an opinionated approach to scheduling snapshots and orchestrating repository health operations. Features include importing existing restic repositories, cron-scheduled backups and health operations (such as prune and forget), a graphical interface for browsing and restoring files from snapshots, configurable backup notifications (Discord, Slack, Shoutrrr, Gotify), and shell command hooks that run before and after backup operations. Backrest is compatible with rclone remotes, supports cross-platform deployment (Linux, macOS, Windows, FreeBSD, Docker), and can back up to any restic-supported storage backend, including S3, Backblaze B2, Azure, Google Cloud Storage, local disk, and SFTP.

Platform availability

Available on 6 of 10 platforms

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
75last commit 116 days ago
Popular
787,782 GitHub stars
Easy to install
856 install platforms, install notes, Docker image
Light to run
No data
Security check
76no serious findings, 4 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 7 days ago

GitHub stars
7,782
Open issues
398
Last commit
2026-07-28
Latest release
v1.14.1
License
GPL-3.0
Activity
stale

Checked 22 days ago - source: GitHub (garethgeorge/backrest)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fix the Docker paths before starting In the Docker Compose file, replace /path/to/backup/data and, if you use local repositories, /path/to/local/repos with the real folders you want to protect. Keep ./backrest/config, data, cache, and rclone on persistent storage, or Backrest can forget its plans and cloud login details after changes. source
  • Use the remote access flag when needed If you install with the script and want to use the 9898 page from another device, run it with --allow-remote-access. Without that flag, it listens only on 127.0.0.1, so other machines on your network cannot connect. source
  • Prerequisites For native installs, install the restic CLI on the same host. source

Fetched 15 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What Docker paths and persistent volumes should I configure for Backrest?

Replace /path/to/backup/data and, if using local repositories, /path/to/local/repos with the real folders to protect. Keep ./backrest/config, data, cache, and rclone on persistent storage, otherwise Backrest can forget backup plans and cloud login details after changes.

How do I allow other devices to reach the Backrest UI after installing it with the script?

Run it with --allow-remote-access if you want to use the 9898 page from another device. Without that flag, it listens only on 127.0.0.1.

How can I reset Backrest login credentials?

Delete the "users" key from your saved configuration to reset the username and password.

Can the Backrest installation ID be changed after initial setup?

No, it cannot be changed via the UI after initial setup. It is used to distinguish snapshots from different Backrest instances.

What should I keep to recover a Backrest/restic repository?

Keep your repository passwords and 2FA recovery codes, since they are needed to recover the repository.

Can Backrest schedule prune and forget operations?

Yes, it can run cron scheduled backups and health operations, such as prune and forget.

Answers sourced from deepwiki.com, deepwiki.com, garethgeorge.github.io, github.com, www.reddit.com

Community

Collected 53 days ago - public community threads