Softwr

File Storage · head to head

Cloudian vs Velero

Cloudian logo

Cloudian

File Storage

S3-compatible on-premises object storage with object lock immutability

From
On request
Free plan
No
Velero logo

Velero

Backup

Open source backup and migration for Kubernetes cluster resources

From
Free
Free plan
Yes

The short version

  • Velero is free; Cloudian prices on request.
  • Only Cloudian lists S3 API compatibility; only Velero lists cluster resource backup.
  • Prices and features on this page were last checked on 1 September 2026.

Where they differ

Only the attributes on which Cloudian and Velero actually diverge.

Attributes where Cloudian and Velero differ
AttributeCloudianVelero
Starting priceOn requestFree
Pricing modelQuoteOpen source, no licence fee
Free tierNoYes
CategoryFile StorageBackup

Identical on both: platforms (Linux).

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 Cloudian

  • S3 API compatibility
  • Object Lock
  • Erasure coding
  • Multi-tenancy
  • Hybrid tiering
  • HyperStore appliances

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.

Cloudian

  • A backup team needing an immutable target so a compromised administrator account cannot delete the backupsnot Velero
  • An organisation restoring hundreds of terabytes regularly where public cloud egress charges make cloud storage untenablenot Velero
  • A university or government body with data residency rules preventing use of public cloud object storagenot Velero
  • A media archive holding petabytes of finished content where per-terabyte capital cost beats per-gigabyte monthly cloud feesnot Velero

Velero

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

Where each one falls short

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

Cloudian

  • You operate the hardware, so capacity planning, firmware, node failures and a refresh cycle every five years return as costs that a public cloud bill hides
  • Per-terabyte licensing plus servers means high upfront cost, and the crossover point against public cloud only arrives at meaningful scale, typically hundreds of terabytes and up
  • S3 compatibility is high but not identical to Amazon, so occasional applications depending on newer or less common S3 features need testing rather than assumption
  • Small deployments need a minimum node count for erasure coding to be meaningful, which sets a practical floor on entry cost regardless of how little data you have
  • Performance is object storage performance, so it is not a substitute for block or high-throughput file storage and buyers occasionally deploy it for the wrong workload

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

Cloudian

On request
  • Cloudian HyperStoreOn request
    • Licensed per usable terabyte, subscription or perpetual
    • Software-only on your hardware or as Cloudian appliances
    • No egress or API request charges

Velero

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

Which should you pick?

Choose Cloudian if

  • You need s3 api compatibility.
  • You work on Linux.
  • You also want object lock.

Choose Velero if

  • You need cluster resource backup.
  • You want to start without paying.
  • You work on Linux.
  • You also want volume snapshots.

Questions people ask

Is Cloudian or Velero better?
Neither clearly leads. Cloudian starts at On request and Velero at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cloudian or Velero?
Velero has a free tier; the other does not. Paid plans start at On request for Cloudian and Free for Velero.
Does Cloudian or Velero run on more platforms?
Both run on Linux, so platform support will not decide this one for you.
Can I use Velero for free?
Yes. Velero has a free tier, so you can try it without paying. Cloudian starts at On request.
What is Cloudian best used for?
Cloudian is most often used for a backup team needing an immutable target so a compromised administrator account cannot delete the backups, an organisation restoring hundreds of terabytes regularly where public cloud egress charges make cloud storage untenable, a university or government body with data residency rules preventing use of public cloud object storage, a media archive holding petabytes of finished content where per-terabyte capital cost beats per-gigabyte monthly cloud fees. Of those, a backup team needing an immutable target so a compromised administrator account cannot delete the backups and an organisation restoring hundreds of terabytes regularly where public cloud egress charges make cloud storage untenable are not what Velero is typically brought in for.
What can Cloudian do that Velero cannot?
Cloudian covers S3 API compatibility, Object Lock, Erasure coding, Multi-tenancy. Velero covers Cluster resource backup, Volume snapshots, File-level backup, Cross-cluster restore.

Answered from the vendors’ own pages

Cloudian: Does object lock really stop ransomware deleting backups?

Within the retention period, yes, provided the lock is set in compliance mode. That is precisely why it is the common answer to backup-targeting ransomware.

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.

Cloudian: Are there egress charges?

No. That is the central cost argument against public cloud object storage, and it only becomes visible when you have to restore at volume.

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.

Cloudian: Can we use our own servers?

Yes, HyperStore is software-defined and runs on qualified commodity hardware, or you can buy Cloudian appliances if you would rather not certify your own.

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

Other head to heads