PROVIDER Β· Modern snapshot backup tool
Kopia
Kopia is an open-source (Apache 2.0) snapshot backup tool from around 2020 using content-addressed dedup and end-to-end encryption, with both GUI and CLI across S3, B2, and SFTP backends for self-hosted server backup.
4pts
Pros
Cons
Product Information
Detailed Notes
Overview
Kopia is an open-source backup tool (Apache 2.0) that appeared around 2020, written in Go by a US-based author. It belongs to the content-addressed snapshot family like restic, with encryption, deduplication, and independent snapshots, adding a graphical interface and richer policy configuration that lowers the CLI barrier.
In Backup & Migration work it suits teams that want more than a CLI but not a commercial product, offering a desktop GUI, server-side CLI with policy files, backends including S3, B2, and SFTP, and hourly snapshot schedules with retention rules.
Know the limits. Its ecosystem and documentation trail restic and the community is smaller, policy configuration has many knobs that require understanding how snapshots relate to retention, and long-running performance plus index size on very large repositories still need your own validation.
Core Strengths
- Open source (Apache 2.0) with both GUI and CLI, lowering the entry barrier
- Content-addressed snapshots with dedup and end-to-end encryption keep multi-version archives small
- S3, B2, SFTP, and WebDAV backends push backups to offsite object storage
- Hourly policies with flexible retention plus snapshot integrity verification
Product Ecosystem
Snapshots and retention
Snapshots cover files and directories with retention controlling version count. Retention must outlast incident discovery time, since keeping seven days only when problems surface is already too late.
Encryption and backends
The repository passphrase must be stored offline or data is unrecoverable, and the backend should be a bucket with object lock to stop ransomware clearing history. Run a real restore drill after setup.
Drawbacks
- Smaller community and thinner documentation than restic, with fewer references for edge cases
- Many policy options where misunderstanding snapshot versus retention leaves gaps
- Index and performance behaviour on very large repositories needs validation
- No commercial support or SLA, so critical systems need a companion solution
Use Cases
- Self-hosted backup needing a GUI (β β β β β) - GUI plus CLI serves both usability and automation
- Scheduled server snapshots (β β β β β) - S3 backend plus retention builds offsite backup
- Teams needing deep customisation (β β β β ) - Flexible policies cover complex retention needs
- Critical systems needing vendor support (β β ) - No commercial SLA, so pair it with a commercial product
Pricing
| Plan | Price | Scope |
|---|---|---|
| Licence | $0 | Open source (Apache 2.0), no licence fee |
| Scheduling and UI | Built in | Policies configured via GUI or CLI |
| Storage cost | Per backend | Billed separately by the storage provider |
The software is free and cost sits in storage and operations. Beyond licence fees, include restore-drill labour when comparing with commercial products, since any untested backup has unknown reliability.
FAQ
-
Kopia or restic? Kopia for a GUI and finer policy control, restic for a mature ecosystem, scripting, and the most references. Both support object storage with encrypted dedup, and switching means rebuilding repositories.
-
What if the passphrase is lost? It is unrecoverable. Store the passphrase offline in a different location from the backups, ideally in both a password manager and a physical copy.
-
Can backups be made undeletable? Object lock or immutable storage on the storage side is required, since client-side policy cannot stop deletion after credential leakage, and that step is what protects backups from ransomware.