Kopia vs Backrest
they're not actually competing for the same job

The honest framing nobody else gives you

Search "Kopia vs Backrest" and most articles compare them feature-for-feature like they're equivalents. They're not. Here's the real picture:

• Kopia is a backup engine.Its own format, its own dedup, its own encryption, its own UI built in. Self-contained tool. Direct competitor to Restic and Borg.
• Backrest is a UI.Web dashboard that calls the Restic binary. The backups are Restic format. Backrest just adds scheduling, monitoring, and a clickable interface on top.

So "Kopia vs Backrest" is really "Kopia vs Restic" — with Backrest just being the UI you'd use to drive Restic. The right comparison shape:

Side-by-side comparison

When to choose Kopia

• You want one tool, not a stack.Kopia is the engine and the UI in one binary. Less moving parts than Restic + Backrest.
• You're starting fresh.No existing Restic repos, no existing tooling. Kopia's UX is more polished out of the box.
• You're self-hosting against generic object storage.S3, B2, MinIO. Kopia talks directly. No middleware.
• You don't need a hosted provider.Kopia hosting options are thin — most managed backup providers are Restic-first.

When to choose Backrest (Restic)

• You already have Restic repos.Backrest reads them. Don't migrate just for a UI.
• You want hosted backend options.Restic has the largest ecosystem of managed providers. Hosted Kopia barely exists.
• You want a UI but don't want to commit to one tool's format.Restic's data is portable. If you ditch Backrest later, repos still work with the CLI.
• You're running multi-host backups to one repo.Restic handles multi-host repos cleanly. Backrest gives you one dashboard for all hosts.

The third option: hosted Restic, skip the UI question

If your goal is "I want backups working with minimal fuss," running Backrest still leaves you with a service to maintain. The Backrest container needs uptime, updates, a domain, TLS, auth. That's another thing to babysit alongside the actual backup target.

ServerCrate runs the Restic backend for you. You point Restic CLI (or any Restic-compatible client, Backrest included) at our SFTP endpoint and we handle ZFS, snapshots, integrity, redundancy, monitoring. Same Restic format you'd use anyway. Zero-knowledge by design — repo passwords never leave your machine in plaintext.

You can still run Backrest in front of it if you want a dashboard. But you're not also responsible for the storage layer.

FAQ

Is Backrest a fork of Restic?

No. Backrest is a separate project that wraps the official Restic binary. It calls Restic for actual backup operations and adds a web UI, scheduler, and config layer on top.

Can I switch between Kopia and Restic later?

Not directly. The repository formats are incompatible. You'd need to restore from one tool and re-backup with the other. This is a real lock-in cost — pick carefully if you're starting fresh.

Does ServerCrate support Kopia?

Not natively. ServerCrate is built for Restic over SFTP. Kopia supports SFTP backends so it would technically work, but our tooling, monitoring, and docs are Restic-first. If you're committed to Kopia, you're better off with generic object storage.

Is Backrest production-ready?

Backrest is actively developed and used in homelab and small business contexts. For mission-critical enterprise backups, the conservative play is still raw Restic CLI with systemd timers — fewer moving parts, better audit trail. Backrest is fine for most non-enterprise use.