Borg vs Duplicati
Editor take
Choose Borg for an append-only key over SSH and for archives you can mount. Choose Duplicati for a web UI that schedules and for SMB, FTP and cloud-drive destinations.
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.
Borg
Where Borg is stronger
- Append-only key over SSHAn SSH key can run borg serve --append-only, so a compromised client cannot delete old archives; Duplicati guards cloud volumes with bucket object locking.1
- Mount an archive as a folderborg mount exposes any archive through FUSE for browsing and copying files; Duplicati restores through its own UI or the command line.2
- No local database to keepThe repository holds everything, so a new machine needs the passphrase; Duplicati rebuilds a per-job database when one is missing, which can take a while.3
Duplicati
Where Duplicati is stronger
- Web UI with schedulesJobs carry a schedule, retention and a restore browser; Borg has no scheduler or interface, so cron and borg create do the work.4
- SMB, FTP and cloud drivesSMB, FTP, SFTP, S3, B2, Dropbox, OneDrive and Google Drive are destinations of their own; Borg 1.4 writes to a disk or an SSH host.5
- Full-disk imagesReads a whole disk with its partition table and restores it to a blank drive; Borg archives files and folders only.6
Borg vs Duplicati: 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 | ||
|---|---|---|
| Price | Free | Free + Paid |
| Licence | BSD-3-Clause | MIT |
| Concurrent backups | Sequential / locked | – |
| Storage support | Local, SSH | Local, SFTP, S3, B2, WebDAV |
| Notifications | – | Email, Webhooks, Telegram |
| Deduplication | Yes (per repository) | Yes (per repository) |
| Web UI | – | Yes |
| Windows | – | Yes |
| macOS | – | Yes |
| Linux | – | Yes |
| Docker | Yes | Yes |
| Linux package | Yes | Yes |
| Windows | – | Yes |
| macOS | Yes | Yes |
| Tech stack | Python | .NET |
| Docker Containers | 1 (app only) | 1 (app only) |
| Database | none | SQLite |
| Architecture | x86 + ARM | x86 + ARM |
Common questions
Does Borg need its own server?
No. A local directory works, and a remote repository only needs SSH and borg serve on the host. Borg 1.4 has no S3 or cloud backend of its own (the 2.0 beta adds S3, B2 and rclone), so a bucket has to be mounted as a filesystem before Borg can write to it.
Can Duplicati browse an archive without restoring it?
It lists the files in a version and restores the ones you pick, from its web UI or the command line. Borg mounts any archive with borg mount, so you browse it like a directory.
Which one tells me a backup failed?
Both, by different routes. Borg exits non-zero, so cron or a wrapper script has to send the alert. Duplicati sends an email, HTTP, Telegram or XMPP report after each run for free, and the Console adds missed-backup alerts on a paid plan.
Do both compress their backups?
Yes. Borg picks a codec on each borg create: lz4 by default, or zstd, zlib or lzma. Duplicati compresses each volume as it uploads it, with a compression module (zip, or tar with gzip or zstd) and a level set per job.
Sources: Borg docs and Duplicati docs.