Is Ceph or Velero better?

Neither clearly leads. Ceph 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, Ceph or Velero?

Ceph starts at Free and Velero at Free.

Does Ceph or Velero run on more platforms?

Both run on Linux, so platform support will not decide this one for you.

Can I use Ceph for free?

Both have a free tier, so you can try either at no cost before committing.

What is Ceph best used for?

Ceph is most often used for backing a private cloud where virtual machine disks, shared filesystems and an s3 endpoint all need the same hardware, growing past the point where a proprietary array upgrade costs more than a rack of commodity servers, research and media environments with petabytes of data and staff who can operate storage, providing an s3 endpoint on premises with multi site replication under your own control. Of those, backing a private cloud where virtual machine disks, shared filesystems and an s3 endpoint all need the same hardware and growing past the point where a proprietary array upgrade costs more than a rack of commodity servers are not what Velero is typically brought in for.

What can Ceph do that Velero cannot?

Ceph covers RADOS object store, RADOS Gateway, RBD block devices, CephFS. Velero covers Cluster resource backup, Volume snapshots, File-level backup, Cross-cluster restore.

File Storage · head to head

Ceph vs Velero

Ceph

File Storage

Open source distributed storage providing object, block and file from one cluster

From: Free
Rated: -

Full review Website

Velero

Backup

Open source backup and migration for Kubernetes cluster resources

From: Free
Rated: -

Full review Website

The short version

Each has a real cost: Ceph ceph assumes an operator who understands placement groups, CRUSH rules and recovery tuning, so organisations without dedicated storage staff routinely end up with a cluster that works until the first failure and then does not.; 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: Ceph covers RADOS object store, Velero covers Cluster resource backup.
Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Ceph and Velero actually diverge.

Attributes where Ceph and Velero differ
Attribute	Ceph	Velero
Category	File Storage	Backup

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), platforms (Linux), 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 Ceph

RADOS object store
RADOS Gateway
RBD block devices
CephFS
CRUSH placement
Erasure coded pools

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.

Ceph

Backing a private cloud where virtual machine disks, shared filesystems and an S3 endpoint all need the same hardwarenot Velero
Growing past the point where a proprietary array upgrade costs more than a rack of commodity serversnot Velero
Research and media environments with petabytes of data and staff who can operate storagenot Velero
Providing an S3 endpoint on premises with multi site replication under your own controlnot Velero

Velero

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

Where each one falls short

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

Ceph

Ceph assumes an operator who understands placement groups, CRUSH rules and recovery tuning, so organisations without dedicated storage staff routinely end up with a cluster that works until the first failure and then does not.
Small clusters are inefficient: three way replication means a third of raw capacity is usable, and erasure coding needs enough failure domains to be safe, so the economics only work above a certain size.
Recovery and rebalancing generate heavy internal traffic, so a failed disk can degrade client latency across the cluster unless backfill is throttled correctly beforehand.
Upgrades must follow a strict daemon order across monitors, managers, OSDs and gateways, and a mistake in that order on a live cluster is difficult to reverse.
Because it is self hosted, every byte served to the internet is transit you pay for on your own links, so the free licence does not mean free egress and bandwidth planning becomes your problem rather than the providers.

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

Ceph

Free

CephFree
- Full functionality, no capacity limit
- Object, block and file interfaces
- Community support via mailing list and Slack

Velero

Free

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

Which should you pick?

Choose Ceph if

You need rados object store.
You want to start without paying.
You work on Linux.
You also want rados gateway.

Ceph 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 Ceph or Velero better?: Neither clearly leads. Ceph 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, Ceph or Velero?: Ceph starts at Free and Velero at Free.
Does Ceph or Velero run on more platforms?: Both run on Linux, so platform support will not decide this one for you.
Can I use Ceph for free?: Both have a free tier, so you can try either at no cost before committing.
What is Ceph best used for?: Ceph is most often used for backing a private cloud where virtual machine disks, shared filesystems and an s3 endpoint all need the same hardware, growing past the point where a proprietary array upgrade costs more than a rack of commodity servers, research and media environments with petabytes of data and staff who can operate storage, providing an s3 endpoint on premises with multi site replication under your own control. Of those, backing a private cloud where virtual machine disks, shared filesystems and an s3 endpoint all need the same hardware and growing past the point where a proprietary array upgrade costs more than a rack of commodity servers are not what Velero is typically brought in for.
What can Ceph do that Velero cannot?: Ceph covers RADOS object store, RADOS Gateway, RBD block devices, CephFS. Velero covers Cluster resource backup, Volume snapshots, File-level backup, Cross-cluster restore.

Answered from the vendors’ own pages

Ceph: How many nodes do I need to start?

Three is the practical minimum for a replicated cluster with real fault tolerance, and most production advice starts at five once you account for maintenance windows.

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.

Ceph: Is it faster than a SAN?

Not on single stream latency. It wins on aggregate throughput and on growing without a forklift upgrade, which is a different property from raw speed.

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.

Ceph: Can I buy support?

Yes. IBM sells IBM Storage Ceph and SUSE and others have offered supported builds; the upstream project itself is free.

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.

Ceph: Should I use it just for S3?

If object is all you need, a dedicated object store is simpler to run. Ceph earns its complexity when you need block and file as well.

Ceph vs Velero

Ceph

Velero

The short version

Where they differ

What each one covers

Only in Ceph

Only in Velero

What people use each for

Ceph

Velero

Where each one falls short

Ceph

Velero

Pricing, plan by plan

Ceph

Velero

Which should you pick?

Choose Ceph if

Choose Velero if

Questions people ask

Answered from the vendors’ own pages

Related pages

More on Ceph

More on Velero

Keep looking

Other head to heads