Softwr

Cloud · head to head

Flux vs Portworx Backup

Flux logo

Flux

Cloud

GitOps continuous delivery for Kubernetes

From
Free
Rated
-
Full reviewWebsite
Portworx Backup logo

Portworx Backup

Backup

Kubernetes application backup with a free tier up to one terabyte

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Flux no user interface of its own: observing what Flux is doing means CLI or a third-party dashboard; 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: Flux covers Git as source of truth, 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 Flux and Portworx Backup actually diverge.

Attributes where Flux and Portworx Backup differ
AttributeFluxPortworx Backup
Pricing modelOpen source, no licence feePer node hour
PlatformsKubernetes, LinuxWeb, Linux
CategoryCloudBackup

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

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 Flux

  • Git as source of truth
  • Pull-based delivery
  • Helm and Kustomize support
  • Automated image updates

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.

Flux

  • Removing cluster credentials from CI systemsnot Portworx Backup
  • Keeping many clusters consistent with a single declared statenot Portworx Backup
  • Automatically correcting configuration drift rather than discovering it laternot Portworx Backup

Portworx Backup

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

Where each one falls short

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

Flux

  • No user interface of its own: observing what Flux is doing means CLI or a third-party dashboard
  • Debugging a stuck reconciliation is harder than reading a pipeline log, because failure is asynchronous
  • Everything must be in Git, which is awkward for secrets and needs a sealed-secrets or external-secrets approach
  • GitOps is a workflow change, not just a tool, and teams used to imperative deploys find the adjustment real

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

Flux

Free
  • FluxFree
    • Full functionality
    • No usage limits
    • Community support

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 Flux if

  • You need git as source of truth.
  • You want to start without paying.
  • You work on Kubernetes, Linux.
  • You also want pull-based delivery.
Flux review

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

Questions people ask

Is Flux or Portworx Backup better?
Neither clearly leads. Flux 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, Flux or Portworx Backup?
Flux starts at Free and Portworx Backup at Free.
Does Flux or Portworx Backup run on more platforms?
Flux runs on Kubernetes, Linux. Portworx Backup runs on Web, Linux.
Can I use Flux for free?
Both have a free tier, so you can try either at no cost before committing.
What is Flux best used for?
Flux is most often used for removing cluster credentials from ci systems, keeping many clusters consistent with a single declared state, automatically correcting configuration drift rather than discovering it later. Of those, removing cluster credentials from ci systems and keeping many clusters consistent with a single declared state are not what Portworx Backup is typically brought in for.
What can Flux do that Portworx Backup cannot?
Flux covers Git as source of truth, Pull-based delivery, Helm and Kustomize support, Automated image updates. Portworx Backup covers Application-level backup, Any CSI provider, Cross-cluster restore, Namespace and label selection.

Answered from the vendors’ own pages

Flux: Is Flux free?

Yes, open source and CNCF-graduated.

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.

Flux: Flux or Argo CD?

Both implement GitOps. Argo CD ships a strong web UI and is often preferred for visibility; Flux is more modular and composes as controllers, which suits platform teams.

Portworx Backup: Does it only protect Portworx volumes?

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

Flux: Why is pull-based safer?

Because the cluster reaches out to Git rather than CI reaching into the cluster. No external system needs write credentials to production.

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.

Share

Related pages

More on Flux

More on Portworx Backup

Keep looking

Other head to heads