Softwr

Backup · head to head

Portworx Backup vs rustic

Portworx Backup logo

Portworx Backup

Backup

Kubernetes application backup with a free tier up to one terabyte

From
Free
Rated
-
Full reviewWebsite
rustic logo

rustic

Backup

Rust reimplementation of restic that reads and writes the same repository format

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; rustic the project is small with a short list of active maintainers, so bus factor is a genuine consideration for software whose job is to still work in five years.
  • They diverge on capability: Portworx Backup covers Application-level backup, rustic covers restic format compatibility.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Portworx Backup and rustic differ
AttributePortworx Backuprustic
Pricing modelPer node hourOpen source, no licence fee
PlatformsWeb, LinuxLinux, macOS, Windows

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 Portworx Backup

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

Only in rustic

  • restic format compatibility
  • Configuration profiles
  • Deduplicated encrypted backups
  • Cold and append only storage support
  • Multiple back ends
  • Library crates

What people use each for

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

Portworx Backup

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

rustic

  • An existing restic user who wants configuration files rather than long command lines in cronnot Portworx Backup
  • Backing up a memory constrained machine where the reference implementation is uncomfortably heavynot Portworx Backup
  • Writing to append only or cold object storage where the default tooling assumes rewritable bucketsnot Portworx Backup
  • Keeping a second implementation available so a long lived archive does not depend on one codebasenot Portworx Backup

Where each one falls short

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

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.

rustic

  • The project is small with a short list of active maintainers, so bus factor is a genuine consideration for software whose job is to still work in five years.
  • It inherits the restic repository format, so design limits in that format, including the cost of pruning large repositories, are inherited rather than fixed.
  • Command names, flags and behaviour do not map one to one onto restic, so scripts and runbooks need rewriting rather than a binary swap.
  • Far fewer people have performed a real restore from it under pressure, and backup software is one of the few categories where being second most used is itself a risk.
  • Alternating between rustic and restic against one repository works but doubles the surface for a version incompatibility to corrupt state, so most operators should pick one and stay with it.

Pricing, plan by plan

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

rustic

Free
  • rusticFree
    • Full functionality, no data limit
    • All supported storage back ends
    • Community support via GitHub

Which should you pick?

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.
Portworx Backup review

Choose rustic if

  • You need restic format compatibility.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want configuration profiles.
rustic review

Questions people ask

Is Portworx Backup or rustic better?
Neither clearly leads. Portworx Backup starts at Free and rustic at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Portworx Backup or rustic?
Portworx Backup starts at Free and rustic at Free.
Does Portworx Backup or rustic run on more platforms?
Portworx Backup runs on Web, Linux. rustic runs on Linux, macOS, Windows.
Can I use Portworx Backup for free?
Both have a free tier, so you can try either at no cost before committing.
What is Portworx Backup best used for?
Portworx Backup is most often used for a platform team running velero that needs an accountable vendor for restore failures, protecting kubernetes applications across eks, gke and on premises clusters under one policy set, restoring a namespace into a different cloud provider as a disaster recovery test, a small team that wants real kubernetes backup within the free one terabyte tier before committing budget. Of those, a platform team running velero that needs an accountable vendor for restore failures and protecting kubernetes applications across eks, gke and on premises clusters under one policy set are not what rustic is typically brought in for.
What can Portworx Backup do that rustic cannot?
Portworx Backup covers Application-level backup, Any CSI provider, Cross-cluster restore, Namespace and label selection. rustic covers restic format compatibility, Configuration profiles, Deduplicated encrypted backups, Cold and append only storage support.

Answered from the vendors’ own pages

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.

rustic: Can it read my existing restic repository?

Yes, that is the point of the project. Take a copy and verify before you rely on it, as with any change to backup tooling.

Portworx Backup: Does it only protect Portworx volumes?

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

rustic: Should I switch from restic?

Only for a specific reason such as configuration profiles, memory use or cold storage handling. Compatibility means there is no cost to trying and no cost to going back.

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.

rustic: Is it production ready?

It is used in production by a small community, but it is younger and less exercised than the implementation it is compatible with. Test restores accordingly.

rustic: Does it support the same back ends?

The common ones, including local, SFTP, S3 compatible storage and rclone. Check the current list before committing to an unusual target.

Share

Related pages

More on Portworx Backup

More on rustic

Keep looking

Other head to heads