Backup · head to head
Proxmox Backup Server vs Velero

Proxmox Backup Server
Backup
Deduplicating backup server for virtual machines, containers and Linux hosts, with verification built in
- From
- Free
- Rated
- -

Velero
Backup
Open source backup and migration for Kubernetes cluster resources
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Proxmox Backup Server there is no Windows client, so physical Windows machines must be backed up by something else and the estate ends up with two backup products.; 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: Proxmox Backup Server covers Deduplicated chunk 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 Proxmox Backup Server and Velero actually diverge.
| Attribute | Proxmox Backup Server | Velero |
|---|
Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), platforms (Linux), user rating (Not yet rated), category (Backup).
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 Proxmox Backup Server
- Deduplicated chunk store
- Incremental guest backups
- Client side encryption
- Verification jobs
- Remote sync
- Live restore and file level restore
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.
Proxmox Backup Server
- Backing up a Proxmox VE cluster with incremental block level backups of running guestsnot Velero
- Replacing a backup product whose licence is priced per socket or per terabyte on a virtualisation estatenot Velero
- Proving backup integrity on a schedule rather than discovering corruption during a restorenot Velero
- Keeping an encrypted second copy on a remote server or on tape without a third party servicenot Velero
Velero
- A platform team needing namespace-level restore after an accidental deletion, with no budget for a backup productnot Proxmox Backup Server
- Migrating workloads between Kubernetes clusters or between cloud providers using backup and restorenot Proxmox Backup Server
- Capturing cluster configuration before a risky upgrade so the previous state can be reinstatednot Proxmox Backup Server
- An organisation proving a Kubernetes recovery capability to an auditor before deciding whether to buy a commercial productnot Proxmox Backup Server
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Proxmox Backup Server
- There is no Windows client, so physical Windows machines must be backed up by something else and the estate ends up with two backup products.
- The datastore is millions of small chunk files, so it needs storage with real input and output capability and performs poorly on a single spinning disk or an SMB or NFS share.
- Deduplication is per datastore, so splitting workloads across datastores for retention or tenancy reasons multiplies the storage those workloads consume.
- Garbage collection depends on file access time semantics on the underlying filesystem, so a datastore mounted with the wrong options can fail to reclaim space or, worse, behave unpredictably.
- Subscriptions are priced per CPU socket per year, so a backup server consolidated onto fewer larger dual socket machines pays twice per host for the supported repository.
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
Proxmox Backup Server
Free- No subscriptionFree
- Full functionality with no capacity limit
- Community package repository
- Community forum support
- Subscription$undefined/year
- Priced per CPU socket per year
- Access to the enterprise package repository
- Vendor support tickets
Velero
Free- VeleroFree
- Apache 2.0 licensed
- No cluster or capacity limits
- Community support via Kubernetes Slack and GitHub
Which should you pick?
Choose Proxmox Backup Server if
- You need deduplicated chunk store.
- You want to start without paying.
- You work on Linux.
- You also want incremental guest backups.
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 Proxmox Backup Server or Velero better?
- Neither clearly leads. Proxmox Backup Server 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, Proxmox Backup Server or Velero?
- Proxmox Backup Server starts at Free and Velero at Free.
- Does Proxmox Backup Server or Velero run on more platforms?
- Both run on Linux, so platform support will not decide this one for you.
- Can I use Proxmox Backup Server for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Proxmox Backup Server best used for?
- Proxmox Backup Server is most often used for backing up a proxmox ve cluster with incremental block level backups of running guests, replacing a backup product whose licence is priced per socket or per terabyte on a virtualisation estate, proving backup integrity on a schedule rather than discovering corruption during a restore, keeping an encrypted second copy on a remote server or on tape without a third party service. Of those, backing up a proxmox ve cluster with incremental block level backups of running guests and replacing a backup product whose licence is priced per socket or per terabyte on a virtualisation estate are not what Velero is typically brought in for.
- What can Proxmox Backup Server do that Velero cannot?
- Proxmox Backup Server covers Deduplicated chunk store, Incremental guest backups, Client side encryption, Verification jobs. Velero covers Cluster resource backup, Volume snapshots, File-level backup, Cross-cluster restore.
Answered from the vendors’ own pages
Proxmox Backup Server: Can it back up machines that are not on Proxmox?
Linux hosts yes, through the client, at file level. Other hypervisors and physical Windows machines are outside its scope.
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.
Proxmox Backup Server: Is a subscription required?
No. Without one you use the community repository and forum support. The subscription buys the tested enterprise repository and vendor tickets.
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.
Proxmox Backup Server: How do I know a backup will restore?
Run verification jobs. They re-read the stored chunks and mark snapshots verified or failed, which is stronger evidence than a successful backup log.
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.
Proxmox Backup Server: What storage should the datastore be on?
Local disks, ideally with ZFS and enough input and output capacity for many small files. Network shares are supported but routinely disappointing.
Related pages
More on Proxmox Backup Server
Other head to heads
- Proxmox Backup Server vs Bacula
- Proxmox Backup Server vs Kopia
- Proxmox Backup Server vs rustic
- Proxmox Backup Server vs UrBackup
- Proxmox Backup Server vs Borg Backup
- Proxmox Backup Server vs Duplicacy
- Proxmox Backup Server vs BDRShield
- Proxmox Backup Server vs HPE StoreOnce
- Proxmox Backup Server vs HYCU
- Proxmox Backup Server vs Acronis Cyber Protect
- Proxmox Backup Server vs Portworx Backup
- Proxmox Backup Server vs Apple Time Machine
- Proxmox Backup Server vs Arcserve UDP
- Proxmox Backup Server vs AvePoint Cloud Backup
- Proxmox Backup Server vs Axcient x360Recover
- Proxmox Backup Server vs Bacula Enterprise
- Proxmox Backup Server vs Trilio
- Proxmox Backup Server vs Restic
- Proxmox Backup Server vs Veeam Kasten for Kubernetes
- Proxmox Backup Server vs Amanda Enterprise
- Proxmox Backup Server vs Clonezilla
- Proxmox Backup Server vs Clumio
- Proxmox Backup Server vs Cohesity
- Velero vs Bacula
- Velero vs Kopia
- Velero vs rustic
- Velero vs UrBackup
- Velero vs Borg Backup
- Velero vs Duplicacy
- Velero vs BDRShield
- Velero vs HPE StoreOnce
- Velero vs HYCU
- Velero vs Acronis Cyber Protect
- Velero vs Portworx Backup
- Velero vs Apple Time Machine
- Velero vs Arcserve UDP
- Velero vs AvePoint Cloud Backup
- Velero vs Axcient x360Recover
- Velero vs Bacula Enterprise
- Velero vs Trilio
- Velero vs Restic
- Velero vs Veeam Kasten for Kubernetes
- Velero vs Amanda Enterprise
- Velero vs Clonezilla
- Velero vs Clumio
- Velero vs Cohesity
