Is Kopia or Velero better?

Neither clearly leads. Kopia starts at Free and Velero at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.

Which is cheaper, Kopia or Velero?

Kopia starts at Free and Velero at Free.

Does Kopia or Velero run on more platforms?

Kopia runs on Linux, macOS, Windows, Docker. Velero runs on Linux.

Can I use Kopia for free?

Both have a free tier, so you can try either at no cost before committing.

What is Kopia best used for?

Kopia is most often used for backing up laptops and workstations to cheap object storage with a desktop interface rather than a cron job, deduplicating backups of several similar machines into one repository so common content is stored once, replacing a chunk based tool whose per object charges made a cheap bucket expensive, keeping an encrypted offsite copy where the storage provider must never be able to read the contents. Of those, backing up laptops and workstations to cheap object storage with a desktop interface rather than a cron job and deduplicating backups of several similar machines into one repository so common content is stored once are not what Velero is typically brought in for.

What can Kopia do that Velero cannot?

Kopia covers Content defined chunking, Global deduplication, Pack blobs, Client side encryption. Velero covers Cluster resource backup, Volume snapshots, File-level backup, Cross-cluster restore.

Backup · head to head

Kopia vs Velero

Kopia

Backup

Open source deduplicating backup with client side encryption and a repository on almost any storage

From: Free
Rated: -

Full review Website

Velero

Backup

Open source backup and migration for Kubernetes cluster resources

From: Free
Rated: -

Full review Website

The short version

Each has a real cost: Kopia space is only reclaimed when maintenance runs, and in a shared repository full maintenance is owned by one client, so if that machine goes away the repository grows for ever while every backup still reports success.; Velero there is no vendor support contract from the project itself, so a failed restore during an outage is resolved by your team reading source code and GitHub issues.
They diverge on capability: Kopia covers Content defined chunking, Velero covers Cluster resource backup.
Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Kopia and Velero actually diverge.

Attributes where Kopia and Velero differ
Attribute	Kopia	Velero
Platforms	Linux, macOS, Windows, Docker	Linux

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated), category (Backup).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Kopia

Content defined chunking
Global deduplication
Pack blobs
Client side encryption
Desktop and command line
Repository verification

Only in Velero

Cluster resource backup
Volume snapshots
File-level backup
Cross-cluster restore
Backup hooks
Scheduled backups
Object storage targets

What people use each for

The jobs each tool is most often brought in to do.

Kopia

Backing up laptops and workstations to cheap object storage with a desktop interface rather than a cron jobnot Velero
Deduplicating backups of several similar machines into one repository so common content is stored oncenot Velero
Replacing a chunk based tool whose per object charges made a cheap bucket expensivenot Velero
Keeping an encrypted offsite copy where the storage provider must never be able to read the contentsnot Velero

Velero

A platform team needing namespace-level restore after an accidental deletion, with no budget for a backup productnot Kopia
Migrating workloads between Kubernetes clusters or between cloud providers using backup and restorenot Kopia
Capturing cluster configuration before a risky upgrade so the previous state can be reinstatednot Kopia
An organisation proving a Kubernetes recovery capability to an auditor before deciding whether to buy a commercial productnot Kopia

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Kopia

Space is only reclaimed when maintenance runs, and in a shared repository full maintenance is owned by one client, so if that machine goes away the repository grows for ever while every backup still reports success.
The repository format has changed across versions and mixing client versions against one repository is discouraged, so a fleet must be upgraded together rather than machine by machine.
There is no central orchestration or reporting for many machines, so monitoring a fleet means building your own alerting around exit codes.
Restoring many small files is slower than the backup was, because content must be reassembled from pack blobs, and this is rarely tested until the day it matters.
Encryption is client side with no escrow, so a lost repository password means the data is unrecoverable and there is no vendor to appeal to.

Velero

There is no vendor support contract from the project itself, so a failed restore during an outage is resolved by your team reading source code and GitHub issues.
Application consistency depends on backup hooks you write and maintain, and a database backed up without a correct hook restores to a state that may not be usable.
Restore ordering across dependent resources such as custom resource definitions and operators needs manual attention, and complex applications frequently need a documented runbook rather than a single restore command.
Corporate engineering investment became uncertain after Broadcom acquired VMware, which is a real consideration for anyone building a long retention policy on the project.
Object storage egress charges apply on restore and are billed by your cloud provider, so a full cluster recovery from another region carries a cost discovered during the incident rather than during planning.

Pricing, plan by plan

Kopia

Free

KopiaFree
- Full functionality, no data limit
- Desktop application included
- Any supported storage back end

Velero

Free

VeleroFree
- Apache 2.0 licensed
- No cluster or capacity limits
- Community support via Kubernetes Slack and GitHub

Which should you pick?

Choose Kopia if

You need content defined chunking.
You want to start without paying.
You work on Linux, macOS, Windows, Docker.
You also want global deduplication.

Kopia review

Choose Velero if

You need cluster resource backup.
You want to start without paying.
You work on Linux.
You also want volume snapshots.

Velero review

Questions people ask

Is Kopia or Velero better?: Neither clearly leads. Kopia starts at Free and Velero at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Kopia or Velero?: Kopia starts at Free and Velero at Free.
Does Kopia or Velero run on more platforms?: Kopia runs on Linux, macOS, Windows, Docker. Velero runs on Linux.
Can I use Kopia for free?: Both have a free tier, so you can try either at no cost before committing.
What is Kopia best used for?: Kopia is most often used for backing up laptops and workstations to cheap object storage with a desktop interface rather than a cron job, deduplicating backups of several similar machines into one repository so common content is stored once, replacing a chunk based tool whose per object charges made a cheap bucket expensive, keeping an encrypted offsite copy where the storage provider must never be able to read the contents. Of those, backing up laptops and workstations to cheap object storage with a desktop interface rather than a cron job and deduplicating backups of several similar machines into one repository so common content is stored once are not what Velero is typically brought in for.
What can Kopia do that Velero cannot?: Kopia covers Content defined chunking, Global deduplication, Pack blobs, Client side encryption. Velero covers Cluster resource backup, Volume snapshots, File-level backup, Cross-cluster restore.

Answered from the vendors’ own pages

Kopia: Is a partly corrupt repository still restorable?

Partly. Deduplication means one damaged pack blob affects every snapshot referencing its contents, but unaffected files still restore. Run verification regularly rather than assuming.

Velero: Can we buy support for Velero?

Not from the project. Several commercial Kubernetes backup products package or extend it and sell support, which is the practical route to an accountable vendor.

Kopia: How does it compare with restic?

Similar guarantees, with packing that behaves better on per operation billing, a desktop interface, and compression enabled by default.

Velero: Does it back up persistent volume data?

Yes, through cloud or Container Storage Interface snapshots, or through file-level upload where snapshots are not available.

Kopia: Do I need to run maintenance manually?

It is scheduled automatically by default, but you must ensure the client that owns full maintenance keeps running, otherwise deleted snapshots never free space.

Velero: What does it cost?

Nothing to licence. You pay for object storage capacity and for egress on restore, both billed by your cloud provider.

Kopia: Can several machines share one repository?

Yes, and that is where deduplication pays off, but they should run compatible versions and only one owns full maintenance.

Kopia vs Velero

Kopia

Velero

The short version

Where they differ

What each one covers

Only in Kopia

Only in Velero

What people use each for

Kopia

Velero

Where each one falls short

Kopia

Velero

Pricing, plan by plan

Kopia

Velero

Which should you pick?

Choose Kopia if

Choose Velero if

Questions people ask

Answered from the vendors’ own pages

Related pages

More on Kopia

More on Velero

Keep looking

Other head to heads