Backrest vs Zerobyte

Editor take

Choose Backrest for shell hooks around a plan and for a 1.x release line. Choose Zerobyte for NFS and SMB shares it mounts itself and for alerts to ntfy, Telegram or Pushover.

Editor

Where they differ

Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.

Backrest

Where Backrest is stronger

  • Shell hooks around a planRuns a command before and after a snapshot, for a database dump or a service pause; Zerobyte fires HTTP webhooks at those points instead.1
  • Past 1.0 at 1.14.1Backrest ships 1.x releases; Zerobyte is at 0.x, and its own docs warn that versions can bring major changes.2

Zerobyte

Where Zerobyte is stronger

  • Mounts NFS and SMB itselfAdds NFS, SMB, WebDAV and SFTP shares as volumes inside its container; Backrest has no NFS or SMB backend of its own.3
  • Alerts routed per scheduleNine destinations, including ntfy, Telegram and Pushover, chosen per schedule and per event; Backrest sends to five services.4

Backrest vs Zerobyte: specs side by side

Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.

Spec
PriceFreeFree
LicenceGPL-3.0AGPL-3.0
Concurrent backupsSequential / locked–
Storage supportLocal, SFTP, S3, B2, rcloneLocal, S3, B2, SFTP
NotificationsDiscord, Slack, Gotify, Shoutrrr, HealthchecksDiscord, Slack, Gotify, ntfy, Email, Webhooks
DeduplicationYes (per repository)Yes (per repository)
Web UIYesYes
DockerYesYes
Linux packageYes–
WindowsYes–
macOSYes–
Tech stackGoBun
Docker Containers1 (app only)1 (app only)
DatabaseSQLiteSQLite
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Backrest site and Zerobyte docs.

Updated