Borg vs Kopia
Editor take
Choose Borg for an append-only key over SSH and for a 1.x release line that began in 2016. Choose Kopia for a desktop app on each machine and for S3, B2 and Azure targets.
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 SSHA restricted SSH key runs borg serve --append-only, so a compromised machine cannot delete old archives on a disk or SSH host; Kopia needs cloud object locks to match.1
- A 1.x series since 2016Borg ships 1.4.5 as its stable release and 2.0 is still beta; Kopia is at 0.23.1, before its first 1.0.2
Kopia
Where Kopia is stronger
- A desktop app on each machineKopiaUI runs on Windows, macOS and Linux and connects straight to the repository; Borg installs as the borg command line, with borg serve on the host that keeps the repository.3
- S3, B2 and Azure targetsAmazon S3, Backblaze B2, Azure Blob, Google Cloud, WebDAV and SFTP are built in; Borg 1.4 writes to a disk or an SSH host, and the 2.0 beta adds S3 and B2.4
- Several machines, one repositoryMultiple machines back up to the same repository and share its deduplicated data; Borg locks the repository while it creates an archive, so a second backup can fail.5
Borg vs Kopia: 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 |
| Licence | BSD-3-Clause | Apache-2.0 |
| Concurrent backups | Sequential / locked | Lock-free |
| Storage support | Local, SSH | Local, SFTP, S3, B2, WebDAV |
| Notifications | – | Email, Webhooks, Pushover |
| 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 | Go |
| Docker Containers | 1 (app only) | 1 (app only) |
| Architecture | x86 + ARM | x86 + ARM |
Common questions
Which one writes to S3?
Kopia, natively: Amazon S3, Backblaze B2, Azure Blob and Google Cloud Storage are built in. Borg 1.4 has no S3 backend of its own (the 2.0 beta adds one), so a cloud copy means a disk mounted as a filesystem or a second host reached over SSH.
Can two machines back up at the same time?
With Kopia, yes: several machines back up to one repository and share its deduplicated data. Borg takes an exclusive lock while it creates an archive, so a simultaneous backup to the same repository can fail.
Can Kopia open a Borg repository?
No. Each keeps its own repository format and its own keys, so a restore needs the tool that wrote the backup. Moving across means restoring from one and writing a fresh backup with the other.
Do both compress?
Yes. Borg picks a codec on each borg create, with lz4 as the default and zstd, zlib or lzma as alternatives, and Kopia compresses per policy with pgzip, s2 or zstd. Both dedupe first, so a chunk already in the repository is not stored twice.
Sources: Borg docs and Kopia docs.