Softwr

Backup · head to head

Kopia vs Portworx Backup

Kopia logo

Kopia

Backup

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

From
Free
Rated
-
Portworx Backup logo

Portworx Backup

Backup

Kubernetes application backup with a free tier up to one terabyte

From
Free
Rated
-

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.; Portworx Backup the paid tier carries a 1,000 node hour monthly minimum, so a cluster that only needs occasional protection still pays a floor.
  • They diverge on capability: Kopia covers Content defined chunking, Portworx Backup covers Application-level backup.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Kopia and Portworx Backup actually diverge.

Attributes where Kopia and Portworx Backup differ
AttributeKopiaPortworx Backup
Pricing modelOpen source, no licence feePer node hour
PlatformsLinux, macOS, Windows, DockerWeb, Linux

Identical on both: starting price (Free), 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 Portworx Backup

  • Application-level backup
  • Any CSI provider
  • Cross-cluster restore
  • Namespace and label selection
  • Scheduled policies
  • Role-based access
  • Free tier

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 Portworx Backup
  • Deduplicating backups of several similar machines into one repository so common content is stored oncenot Portworx Backup
  • Replacing a chunk based tool whose per object charges made a cheap bucket expensivenot Portworx Backup
  • Keeping an encrypted offsite copy where the storage provider must never be able to read the contentsnot Portworx Backup

Portworx Backup

  • A platform team running Velero that needs an accountable vendor for restore failuresnot Kopia
  • Protecting Kubernetes applications across EKS, GKE and on premises clusters under one policy setnot Kopia
  • Restoring a namespace into a different cloud provider as a disaster recovery testnot Kopia
  • A small team that wants real Kubernetes backup within the free one terabyte tier before committing budgetnot 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.

Portworx Backup

  • The paid tier carries a 1,000 node hour monthly minimum, so a cluster that only needs occasional protection still pays a floor.
  • It is licensed separately from Portworx Enterprise, so organisations that assumed storage and backup came together find a second subscription in the quote.
  • The free tier caps at one terabyte of protected data, which is quickly exceeded by any database of consequence and forces a jump straight to the minimum commitment.
  • Backup targets are object stores you provide, so restore egress charges from your cloud provider are outside the vendor price and appear during a recovery rather than in procurement.
  • Application-consistent backup of databases still depends on correct pre and post hooks, so the product does not remove the requirement to understand and rehearse your own restore ordering.

Pricing, plan by plan

Kopia

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

Portworx Backup

Free
  • FreeFree
    • Up to one terabyte of protected data
    • No feature restrictions
    • Fully managed service
  • Portworx Backup$0.2/node hour
    • Minimum 1,000 node hours per month
    • Unlimited protected capacity
    • Any Container Storage Interface provider

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.

Choose Portworx Backup if

  • You need application-level backup.
  • You want to start without paying.
  • You work on Web, Linux.
  • You also want any csi provider.

Questions people ask

Is Kopia or Portworx Backup better?
Neither clearly leads. Kopia starts at Free and Portworx Backup at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Kopia or Portworx Backup?
Kopia starts at Free and Portworx Backup at Free.
Does Kopia or Portworx Backup run on more platforms?
Kopia runs on Linux, macOS, Windows, Docker. Portworx Backup runs on Web, 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 Portworx Backup is typically brought in for.
What can Kopia do that Portworx Backup cannot?
Kopia covers Content defined chunking, Global deduplication, Pack blobs, Client side encryption. Portworx Backup covers Application-level backup, Any CSI provider, Cross-cluster restore, Namespace and label selection.

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.

Portworx Backup: Is the free tier real?

Yes, up to one terabyte of protected data with no feature restrictions as a managed service. It is a usable production tier for small footprints, not a trial.

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.

Portworx Backup: Does it only protect Portworx volumes?

No. It works across Container Storage Interface providers, including cloud provider storage and other vendors' drivers.

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.

Portworx Backup: Is it included with Portworx Enterprise?

No. It is a separate licence at 0.20 USD per node hour with its own minimum.

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.

Share

Related pages

Other head to heads