Softwr

Cloud · head to head

Portworx vs Veeam Kasten for Kubernetes

Portworx logo

Portworx

Cloud

Kubernetes-native storage and data services, priced by the node hour

From
$0.33/node hour
Rated
-
Veeam Kasten for Kubernetes logo

Veeam Kasten for Kubernetes

Backup

Kubernetes-native backup, disaster recovery and application mobility

From
Free
Rated
-

The short version

  • Only Veeam Kasten for Kubernetes has a free tier, so it costs nothing to try first.
  • Each has a real cost: Portworx bare metal nodes are charged at 1.11 USD per node hour against 0.33 for virtual nodes, so a bare metal cluster costs more than three times a virtualised one for identical capability.; Veeam Kasten for Kubernetes licensing is per worker node, so clusters designed with many small nodes for scheduling flexibility pay considerably more than the same capacity in fewer large nodes.
  • They diverge on capability: Portworx covers Container-native volumes, Veeam Kasten for Kubernetes covers Application-aware capture.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Portworx and Veeam Kasten for Kubernetes actually diverge.

Attributes where Portworx and Veeam Kasten for Kubernetes differ
AttributePortworxVeeam Kasten for Kubernetes
Starting price$0.33/node hourFree
Pricing modelPer node hourPer worker node
Free tierNoYes
PlatformsLinuxKubernetes, Linux
CategoryCloudBackup

Identical on both: 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 Portworx

  • Container-native volumes
  • Failure domain placement
  • Volume encryption
  • Database automation
  • Disaster recovery
  • Autopilot capacity management
  • Hardware independence

Only in Veeam Kasten for Kubernetes

  • Application-aware capture
  • Policy engine
  • Immutable targets
  • Restore transformation
  • Database hooks
  • Ransomware detection

What people use each for

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

Portworx

  • Running a production PostgreSQL or Cassandra cluster on Kubernetes and needing the data to survive node lossnot Veeam Kasten for Kubernetes
  • A platform team offering self-service databases to developers on an internal Kubernetes platformnot Veeam Kasten for Kubernetes
  • Failing over stateful applications between clusters in different regions as a disaster recovery positionnot Veeam Kasten for Kubernetes
  • An OpenShift estate where the built-in storage option does not meet the availability requirement for stateful setsnot Veeam Kasten for Kubernetes

Veeam Kasten for Kubernetes

  • A platform team that must prove to auditors it can restore a production namespace, not just its disksnot Portworx
  • Migrating a stateful application from on-premises OpenShift to a managed cloud Kubernetes servicenot Portworx
  • Protecting Kubernetes workloads to an immutable object store so ransomware cannot delete the backupsnot Portworx
  • A team using operators and custom resources that volume-snapshot tools silently fail to capturenot Portworx

Where each one falls short

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

Portworx

  • Bare metal nodes are charged at 1.11 USD per node hour against 0.33 for virtual nodes, so a bare metal cluster costs more than three times a virtualised one for identical capability.
  • A 1,000 node hour monthly minimum applies, which means small or intermittent clusters pay for capacity they do not consume.
  • Replicating volumes across nodes consumes real capacity and network bandwidth, so the underlying infrastructure cost rises alongside the licence in a way the node hour rate does not show.
  • Pure Storage ownership means roadmap priorities are set by an array vendor, and buyers should confirm that hardware independence remains contractual rather than assumed.
  • Operating it well requires Kubernetes storage expertise, and teams that adopted Kubernetes to simplify operations often find they have added a distributed storage system to run.

Veeam Kasten for Kubernetes

  • Licensing is per worker node, so clusters designed with many small nodes for scheduling flexibility pay considerably more than the same capacity in fewer large nodes.
  • The free Starter edition is scale limited and community supported, so it works for evaluation and small clusters but there is no gentle upgrade path when production grows past the limit.
  • Backup performance depends on the underlying CSI driver snapshot capability, so on storage without proper CSI snapshot support it falls back to slower generic copying.
  • Restores into a different cluster need matching custom resource definitions and operator versions present beforehand, so cross-cluster mobility is less automatic than the marketing suggests.
  • Kasten protects Kubernetes only, so organisations with mixed virtual machine and container estates run it alongside a separate backup product and manage two retention policies and two sets of evidence.

Pricing, plan by plan

Portworx

$0.33/node hour
  • Portworx Enterprise on virtual machine nodes$0.33/node hour
    • Minimum 1,000 node hours per month
    • Replicated persistent volumes
    • Encryption and disaster recovery
  • Portworx Enterprise on bare metal nodes$1.11/node hour
    • Minimum 1,000 node hours per month
    • Same capabilities on bare metal clusters
    • Higher rate reflects node density

Veeam Kasten for Kubernetes

Free
  • StarterFree
    • Functionally the same as Enterprise
    • Limited on scale and support
    • Intended for evaluation and small non-production clusters
  • Enterprise$undefined/year
    • Licensed per worker node, quoted annually
    • Available through AWS, Azure and Google Cloud marketplaces
    • Vendor support with SLAs

Which should you pick?

Choose Portworx if

  • You need container-native volumes.
  • You work on Linux.
  • You also want failure domain placement.

Choose Veeam Kasten for Kubernetes if

  • You need application-aware capture.
  • You want to start without paying.
  • You work on Kubernetes, Linux.
  • You also want policy engine.

Questions people ask

Is Portworx or Veeam Kasten for Kubernetes better?
Neither clearly leads. Portworx starts at $0.33/node hour and Veeam Kasten for Kubernetes at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Portworx or Veeam Kasten for Kubernetes?
Veeam Kasten for Kubernetes has a free tier; the other does not. Paid plans start at $0.33/node hour for Portworx and Free for Veeam Kasten for Kubernetes.
Does Portworx or Veeam Kasten for Kubernetes run on more platforms?
Portworx runs on Linux. Veeam Kasten for Kubernetes runs on Kubernetes, Linux.
Can I use Veeam Kasten for Kubernetes for free?
Yes. Veeam Kasten for Kubernetes has a free tier, so you can try it without paying. Portworx starts at $0.33/node hour.
What is Portworx best used for?
Portworx is most often used for running a production postgresql or cassandra cluster on kubernetes and needing the data to survive node loss, a platform team offering self-service databases to developers on an internal kubernetes platform, failing over stateful applications between clusters in different regions as a disaster recovery position, an openshift estate where the built-in storage option does not meet the availability requirement for stateful sets. Of those, running a production postgresql or cassandra cluster on kubernetes and needing the data to survive node loss and a platform team offering self-service databases to developers on an internal kubernetes platform are not what Veeam Kasten for Kubernetes is typically brought in for.
What can Portworx do that Veeam Kasten for Kubernetes cannot?
Portworx covers Container-native volumes, Failure domain placement, Volume encryption, Database automation. Veeam Kasten for Kubernetes covers Application-aware capture, Policy engine, Immutable targets, Restore transformation.

Answered from the vendors’ own pages

Portworx: Is Portworx tied to Pure Storage hardware?

No. It runs on any Kubernetes distribution over any underlying storage, though Pure has owned it since 2020 and sets the roadmap.

Veeam Kasten for Kubernetes: Is Kasten K10 still a product?

It is now sold as Veeam Kasten for Kubernetes. The kasten.io domain redirects to Veeam and the documentation still lives at docs.kasten.io.

Portworx: What does a real cluster cost?

At 0.33 USD per virtual node hour, twenty nodes running continuously is roughly 4,800 USD a month. Bare metal at 1.11 USD per node hour is around 16,000 USD for the same node count.

Veeam Kasten for Kubernetes: Is there a free edition?

Yes, the Starter edition is free and functionally complete but limited on scale and support, aimed at evaluation and small non-production clusters.

Portworx: Is backup included?

No. Portworx Backup is a separately priced product covering Kubernetes application backup.

Veeam Kasten for Kubernetes: How is Enterprise licensed?

Per worker node. Count your nodes, not your capacity, before comparing quotes, because node sizing directly changes the price.

Share

Related pages

Other head to heads