Kopia vs restic

Editor take

Choose Kopia for a desktop app on each machine and for policies that follow each host in one repository. Choose restic for a repository that Backrest and Zerobyte can open.

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.

Kopia

Where Kopia is stronger

  • A desktop app on each machineKopiaUI runs on Windows, macOS and Linux and connects straight to the repository; restic is a command line, with browsable front ends such as Backrest and Zerobyte.1
  • Policies per machine, one repositorySchedule, retention and compression are set for each username@hostname in the same repository; restic applies retention from flags on each forget run and leaves scheduling to cron or systemd.2
  • Optional Reed-Solomon error correctionChosen when you create a repository, it guards snapshots against bitflips; the docs call it experimental. restic's repository format has no parity data.3

restic

Where restic is stronger

  • Repositories other tools openBackrest wraps restic and imports existing restic repositories, so a repository made now still opens without Backrest.4

Kopia vs restic: 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
LicenceApache-2.0BSD-2-Clause
Concurrent backupsLock-freeLock-free
Storage supportLocal, SFTP, S3, B2, WebDAVLocal, SFTP, S3, B2, REST, rclone
NotificationsEmail, Webhooks, Pushover–
DeduplicationYes (per repository)Yes (per repository)
Web UIYes–
WindowsYes–
macOSYes–
LinuxYes–
DockerYesYes
Linux packageYesYes
WindowsYesYes
macOSYesYes
Tech stackGoGo
Docker Containers1 (app only)1 (app only)
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Kopia docs and restic docs.

Updated