Softwr

Cloud · head to head

Rook vs Velero

Rook logo

Rook

Cloud

Kubernetes operator that deploys and manages Ceph storage clusters

From
Free
Rated
-
Full reviewWebsite
Velero logo

Velero

Backup

Open source backup and migration for Kubernetes cluster resources

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Rook rook automates Ceph but does not abstract it, so an incident still demands Ceph expertise, and organisations without it end up hiring consultants at exactly the wrong moment.; 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: Rook covers Ceph operator, Velero covers Cluster resource backup.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Rook and Velero actually diverge.

Attributes where Rook and Velero differ
AttributeRookVelero
PlatformsLinux, KubernetesLinux
CategoryCloudBackup

Identical on both: starting price (Free), pricing model (Open source, no licence fee), 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 Rook

  • Ceph operator
  • Block, file and object
  • Erasure coding
  • CSI driver
  • Automated upgrades
  • Multi-cluster mirroring

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.

Rook

  • An on-premises Kubernetes platform needing block, shared filesystem and S3 storage without buying three productsnot Velero
  • A team that already runs Ceph and wants its lifecycle managed declaratively inside Kubernetesnot Velero
  • A large cluster where three-way replication overhead is unaffordable and erasure coding is requirednot Velero
  • An organisation building a private cloud that cannot use managed cloud storage services for residency reasonsnot Velero

Velero

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

Where each one falls short

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

Rook

  • Rook automates Ceph but does not abstract it, so an incident still demands Ceph expertise, and organisations without it end up hiring consultants at exactly the wrong moment.
  • There is no vendor and no SLA; the realistic commercial support routes are IBM Red Hat OpenShift Data Foundation or an independent Ceph consultancy, both of which change the cost picture entirely.
  • Ceph is resource hungry, needing substantial memory and dedicated disks per OSD, so the hardware cost of a properly sized cluster is often underestimated.
  • Recovery and rebalancing after a disk or node failure generates heavy background input and output that can degrade application performance for hours, which surprises teams sizing for steady state.
  • Minimum viable clusters require several nodes with several disks each, so it is impractical at small scale and the entry hardware cost exceeds simpler alternatives.

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

Rook

Free
  • RookFree
    • Apache 2.0 licensed, no licence fee
    • Graduated CNCF project
    • Community support via GitHub and Slack only

Velero

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

Which should you pick?

Choose Rook if

  • You need ceph operator.
  • You want to start without paying.
  • You work on Linux, Kubernetes.
  • You also want block, file and object.
Rook 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 Rook or Velero better?
Neither clearly leads. Rook 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, Rook or Velero?
Rook starts at Free and Velero at Free.
Does Rook or Velero run on more platforms?
Rook runs on Linux, Kubernetes. Velero runs on Linux.
Can I use Rook for free?
Both have a free tier, so you can try either at no cost before committing.
What is Rook best used for?
Rook is most often used for an on-premises kubernetes platform needing block, shared filesystem and s3 storage without buying three products, a team that already runs ceph and wants its lifecycle managed declaratively inside kubernetes, a large cluster where three-way replication overhead is unaffordable and erasure coding is required, an organisation building a private cloud that cannot use managed cloud storage services for residency reasons. Of those, an on-premises kubernetes platform needing block, shared filesystem and s3 storage without buying three products and a team that already runs ceph and wants its lifecycle managed declaratively inside kubernetes are not what Velero is typically brought in for.
What can Rook do that Velero cannot?
Rook covers Ceph operator, Block, file and object, Erasure coding, CSI driver. Velero covers Cluster resource backup, Volume snapshots, File-level backup, Cross-cluster restore.

Answered from the vendors’ own pages

Rook: Who supports it in production?

Nobody by default. IBM sells Red Hat OpenShift Data Foundation, which is supported Rook and Ceph, and independent consultancies sell Ceph support. Decide this before deployment.

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.

Rook: Does it need Ceph knowledge?

Yes. Rook handles deployment and routine operations, but troubleshooting a degraded cluster is a Ceph skill and there is no way around it.

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.

Rook: Can it replace an object storage appliance?

Functionally yes, through the RADOS gateway, but you take on the operations that an appliance vendor would otherwise carry.

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.

Share

Related pages

More on Rook

More on Velero

Keep looking

Other head to heads