Cloud · head to head
Caddy vs Velero

Velero
Backup
Open source backup and migration for Kubernetes cluster resources
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Caddy smaller ecosystem than Nginx, so third-party guides and modules are fewer; 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: Caddy covers Automatic HTTPS, Velero covers Cluster resource backup.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Caddy and Velero actually diverge.
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 Caddy
- Automatic HTTPS
- Caddyfile
- Reverse proxy
- Single binary
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.
Caddy
- Sites and services where expired certificates have caused outages beforenot Velero
- Small deployments where Nginx configuration is more effort than the problem warrantsnot Velero
- Reverse proxying internal services with TLS without a certificate workflownot Velero
Velero
- A platform team needing namespace-level restore after an accidental deletion, with no budget for a backup productnot Caddy
- Migrating workloads between Kubernetes clusters or between cloud providers using backup and restorenot Caddy
- Capturing cluster configuration before a risky upgrade so the previous state can be reinstatednot Caddy
- An organisation proving a Kubernetes recovery capability to an auditor before deciding whether to buy a commercial productnot Caddy
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Caddy
- Smaller ecosystem than Nginx, so third-party guides and modules are fewer
- Adding plugins means rebuilding the binary rather than loading a module
- Under very high throughput Nginx generally still benchmarks ahead
- Automatic certificate issuance needs outbound internet access, which complicates air-gapped deployments
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
Caddy
Free- CaddyFree
- Full functionality
- Commercial use permitted
- Community support
Velero
Free- VeleroFree
- Apache 2.0 licensed
- No cluster or capacity limits
- Community support via Kubernetes Slack and GitHub
Which should you pick?
Choose Caddy if
- You need automatic https.
- You want to start without paying.
- You work on Linux, macOS, Windows, Docker.
- You also want caddyfile.
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 Caddy or Velero better?
- Neither clearly leads. Caddy 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, Caddy or Velero?
- Caddy starts at Free and Velero at Free.
- Does Caddy or Velero run on more platforms?
- Caddy runs on Linux, macOS, Windows, Docker. Velero runs on Linux.
- Can I use Caddy for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Caddy best used for?
- Caddy is most often used for sites and services where expired certificates have caused outages before, small deployments where nginx configuration is more effort than the problem warrants, reverse proxying internal services with tls without a certificate workflow. Of those, sites and services where expired certificates have caused outages before and small deployments where nginx configuration is more effort than the problem warrants are not what Velero is typically brought in for.
- What can Caddy do that Velero cannot?
- Caddy covers Automatic HTTPS, Caddyfile, Reverse proxy, Single binary. Velero covers Cluster resource backup, Volume snapshots, File-level backup, Cross-cluster restore.
Answered from the vendors’ own pages
Caddy: Is Caddy free?
Yes, open source under the Apache 2.0 licence, free for commercial use.
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.
Caddy: What does automatic HTTPS mean?
Caddy obtains certificates from Let’s Encrypt or ZeroSSL on first request and renews them before expiry, with no cron job or configuration.
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.
Caddy: Caddy or Nginx?
Caddy is dramatically simpler to configure and removes certificate management. Nginx has the larger ecosystem and better peak throughput.
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.
Related pages
Other head to heads
- Caddy vs HAProxy
- Caddy vs Packer
- Caddy vs Pulumi
- Caddy vs Portworx
- Caddy vs Podman
- Caddy vs Rancher
- Caddy vs Porter
- Caddy vs Flux
- Caddy vs Contabo
- Caddy vs Coolify
- Caddy vs Crossplane
- Caddy vs Dokku
- Caddy vs Encore
- Caddy vs Vagrant
- Caddy vs Buildah
- Caddy vs Kustomize
- Caddy vs Skopeo
- Caddy vs containerd
- Caddy vs Portworx Backup
- Caddy vs Trilio
- Caddy vs Restic
- Caddy vs HYCU
- Caddy vs UrBackup
- Caddy vs Acronis Cyber Protect
- Caddy vs BDRShield
- Caddy vs Kopia
- Caddy vs Veeam Kasten for Kubernetes
- Caddy vs Amanda Enterprise
- Caddy vs Bacula Enterprise
- Caddy vs Borg Backup
- Caddy vs Axcient x360Recover
- Caddy vs Clonezilla
- Caddy vs Clumio
- Caddy vs Cohesity
- Velero vs HAProxy
- Velero vs Packer
- Velero vs Pulumi
- Velero vs Portworx
- Velero vs Podman
- Velero vs Rancher
- Velero vs Porter
- Velero vs Flux
- Velero vs Contabo
- Velero vs Coolify
- Velero vs Crossplane
- Velero vs Dokku
- Velero vs Encore
- Velero vs Vagrant
- Velero vs Buildah
- Velero vs Kustomize
- Velero vs Skopeo
- Velero vs containerd
- Velero vs Portworx Backup
- Velero vs Trilio
- Velero vs Restic
- Velero vs HYCU
- Velero vs UrBackup
- Velero vs Acronis Cyber Protect
- Velero vs BDRShield
- Velero vs Kopia
- Velero vs Veeam Kasten for Kubernetes
- Velero vs Amanda Enterprise
- Velero vs Bacula Enterprise
- Velero vs Borg Backup
- Velero vs Axcient x360Recover
- Velero vs Clonezilla
- Velero vs Clumio
- Velero vs Cohesity

