Looking for a
Restic alternative?

Why people look for Restic alternatives

The four real reasons:

1. Performance issues - usually on large repositories or slow backends
2. Feature gaps - wanting a GUI, wanting more compression, wanting lock-free concurrent access
3. A specific integration - a backup platform that only speaks Borg or Kopia natively
4. Bad first experience - often a misconfiguration rather than a real Restic problem

Let's take each alternative seriously.

BorgBackup

Borg is the closest peer to Restic. Both are deduplicating, encrypted, snapshot-based tools with similar CLIs. The real differences:

• Compression: Borg supports zstd, lzma, and zlib at multiple levels. Restic uses zstd only. In practice, Borg gives 5-15% smaller repositories on text-heavy data.
• Backends: Borg backs up over SSH to any host with Borg installed, or to local disk. Restic natively supports S3, B2, Azure, GCS, Swift, and SFTP. For cloud object storage, Restic wins.
• Concurrency: Borg requires exclusive access to a repository during backup. Multiple machines cannot back up to the same repo simultaneously. Restic supports concurrent backups from multiple hosts.
• Maturity: Borg has been in production use longer. Both are now stable for serious workloads.

Pick Borg if: you back up to SSH-accessible Linux hosts, want maximum compression, and only one machine writes to each repository.

Pick Restic if: you use cloud storage, back up from multiple hosts to one repo, or prefer a single static binary with no server component.

We wrote a deeper comparison at Restic vs Borg.

Kopia

Kopia is the youngest of the serious contenders. It is fast, has a proper web UI, and supports more storage backends than Restic (including Rclone as a meta-backend, which opens up dozens of targets). The tradeoffs:

• Younger codebase with less battle-testing than Restic or Borg
• More complex configuration model - policies, global/repo/host layers
• Repository format is not compatible with anything else
• Authentication model has had meaningful changes between major versions

Pick Kopia if: you want a GUI for non-technical family members, need a backend that Restic does not support, or are starting a new backup project and want the newest tool.

Duplicacy

Duplicacy's claim to fame is lock-free deduplication - multiple clients can back up to a shared repository without any coordination. This is technically elegant and solves a real problem for multi-machine setups.

Caveats:

• Commercial license - free for personal use, paid for commercial
• Smaller community than Restic or Borg
• CLI ergonomics are less polished; the GUI is a separate product

Pick Duplicacy if: you have a dozen or more machines backing up to one shared target and the coordination overhead of Borg or Restic is a real pain point.

Duplicati

Duplicati is often recommended to beginners because of its nice Windows GUI. Be careful. Duplicati has a long history of corruption bugs and "restore impossible" forum threads. The project has improved but the reputation is earned.

If you specifically need a Windows-first GUI tool and cannot use anything else: evaluate Duplicati carefully, test restores frequently, and keep a second backup with a more trusted tool.

Honest recommendation: install Restic on Windows (it is one binary), or use Kopia with its GUI.

rsync

rsync is not a backup tool. It is a file sync tool. It has no encryption, no deduplication, no snapshot history. An rsync "backup" is a mirror - when ransomware encrypts your source, the next rsync job mirrors the encrypted files to your backup.

People use rsync as a backup because it is simple and ships on every Unix system. For casual "I want a copy on another disk" purposes that is fine. For actual disaster recovery, you need snapshots, and that means Restic, Borg, Kopia, Duplicacy, or a snapshot-capable filesystem like ZFS.

ZFS send / receive

If both your source and destination run ZFS, zfs send | zfs receive is the fastest and most efficient backup tool possible. Block-level, lossless, handles snapshots natively. The catch: both sides need ZFS. If you have a TrueNAS source and a ZFS-based offsite target, use this.

ServerCrate's vaults run on ZFS, but we expose them as SFTP, not raw ZFS - so Restic over SFTP is the supported path. If you have a peer who runs TrueNAS, ZFS replication is worth considering.

When to stick with Restic anyway

Before you switch, ask:

• Is it actually Restic, or your setup? Slow backends, small pack-size, and never running prune are the three most common "Restic is slow" causes. All fixable.
• Are you targeting a cloud backend? Restic's native S3/B2/GCS/Azure support is best-in-class.
• Do multiple machines share a repo? Restic handles this. Borg does not.
• Is simplicity valuable? Single Go binary, no server component, works the same on every OS. Few tools are as operationally boring as Restic, and boring is good for backups.

How ServerCrate fits

ServerCrate is a hosted offsite target optimized for Restic. Per-user SFTP vaults backed by ZFS storage in Los Angeles. Your client runs Restic, encrypts before upload, and the server physically cannot read your files. The backend technology behind your Restic repository is the part people shop for, and ServerCrate is built specifically for this use case.

If you were looking for an alternative to Restic, now you know the landscape. If you were looking for an alternative storage target for Restic, you found it.

Quick decision tree

• Need cloud object storage support → Restic
• Need maximum compression on SSH-accessible Linux → Borg
• Need a GUI for non-technical users → Kopia
• Need lock-free multi-host backup to one repo → Duplicacy
• Want a Windows-first GUI → Kopia (or Restic with a wrapper)
• Both sides run ZFS → zfs send
• Just need to sync files, not back them up → rsync