Overview

Velero combines a server installed in a Kubernetes cluster with a command-line client run locally. It can operate in cloud or on-premises environments, using object storage and optionally supported block-storage systems. That makes it relevant to teams with varied infrastructure, but not a standalone backup service for organizations without Kubernetes operations capacity.

The project is open source and identifies as a Cloud Native Computing Foundation Sandbox project. Community support is available through GitHub issues and the Kubernetes Slack #velero-users channel; teams needing another support arrangement should weigh that model before adopting it.

Key features

Backups can cover a whole cluster or target selected namespaces and label-matched resources. This supports broad disaster-recovery copies as well as narrower policies, though operators must decide which resources belong in each backup.

Recurring schedules and pre- and post-backup hooks help make backup workflows repeatable and accommodate custom operations. Velero can restore after data loss and move resources between clusters, including replicating production clusters to development and test environments. These capabilities make it useful beyond recovery alone, but successful recovery still depends on configuring the required storage and cluster components.

Persistent-volume backup is supported, including CSI-backed volumes through Kubernetes CSI Snapshot APIs. CSI use depends on cluster and driver prerequisites. Maintainer-supported provider plugins cover AWS, Google Cloud, Microsoft Azure, and VMware vSphere, with community-maintained plugins also available. The plugin architecture allows additional storage integrations and custom backup or restore behavior without modifying the core binary.

Security options include use with storage providers secured by self-signed certificates and alternate identity mechanisms that do not require a credentials file. One important caveat: some object-storage immutability settings can interfere with backups because Velero needs to update backup metadata. Teams requiring immutable storage should verify compatibility before relying on that configuration.

Pricing

Velero is free and open source. Its Velero plan is free and supports cloud or on-premises use, but requires Kubernetes and storage-provider plugins. There are no paid tiers or seat and quota limits stated for the plan; the practical costs are the infrastructure and operational effort required to run it.

The free plan includes persistent-volume backup, application consistency, cross-cluster restore, scheduled backups, and custom retention options. Immutable backups are not supported, which matters for teams whose retention policy depends on object immutability.

Platforms

Velero is listed for API, Linux, macOS, self-hosted, and Windows environments. The server runs on Kubernetes, while the client runs locally; CLI releases are available for macOS and Windows as well as other platforms. Windows workload backups still require at least one Linux node for the Velero server. Basic installation also requires access to a Kubernetes cluster, kubectl, and a compatible object-storage provider. File-system backup is not installed by default.

Who it's for

Velero suits teams operating Kubernetes clusters that need backup, restore, disaster recovery, cluster migration, or replication into development and testing. It is especially appropriate where operators want to select resources by namespace or labels and integrate storage through plugins. It is a weaker fit for teams seeking a turnkey managed backup product, guaranteed immutable backups, or a workflow without Kubernetes and storage prerequisites.

Pros and cons

Pros: Whole-cluster and selective backups let teams match protection scope to workload needs.
Pros: Scheduled backups, hooks, restore, and cross-cluster migration cover routine protection and recovery workflows.
Pros: Provider and community plugins extend storage choices across cloud and on-premises environments.
Cons: Installation requires a Kubernetes cluster, kubectl, compatible object storage, and at least one plugin.
Cons: CSI volume protection depends on cluster and driver prerequisites, and file-system backup is not installed by default.
Cons: Some object-storage immutability configurations may conflict with metadata updates, and immutable backups are not a supported plan capability.
Cons: Support is community-based through project channels rather than a stated commercial support plan.

Alternatives

Kubernetes Backup Software and Container Backup Software are broader directories for comparing products in those categories.

Choose Google Kubernetes Engine when the priority is a paid Kubernetes platform with a free tier and monthly credits for eligible clusters, rather than Velero's open-source backup tooling. KubeSphere Backup is worth considering for hosted repository limits and application-based tiers, including a free plan capped at 2 protected applications, 3 days of retention, and 10 GB.

Storware Backup & Recovery offers a free license without technical support and a separate 60-day trial, making it an option for readers comparing trial-based backup products. Afi Kubernetes Backup is another option for Kubernetes backup, with free licenses available by request for environments protecting fewer than 10 nodes and a paid plan at 140.00 USD per month.

Bacula Enterprise may suit readers seeking an annually billed enterprise subscription priced by secured endpoint count and support response time. HYCU R-Cloud is a paid alternative with a free trial and a broader platform list. Plakar is a freemium option for Linux, macOS, and Windows, with its free plan covering up to 500 GB of managed data and a self-deployed control plane. Veeam Agent for Mac is the more targeted choice for macOS backup; its free edition is limited to one backup job and does not back up directly to object storage.

Verdict

Choose Velero if your team already runs Kubernetes and needs a free, extensible way to schedule backups, restore volumes and resources, or move workloads between clusters. Its strongest reason to choose is the combination of selective scope, plugin-based storage, and migration support. Look elsewhere if immutable backups or turnkey commercial support are essential, or if your team cannot meet the Kubernetes and storage setup requirements.

	Azure Backup for AKS	Velero
Free plan		Yes
Paid from		Free
Platforms	Web	api, Linux, macOS, self-hosted, Windows
Free plan	No
Application consistency	both	both
Persistent volume backup	Yes	Yes
Cross-cluster restore	Yes	Yes
Backup frequency	scheduled	scheduled
Retention options	custom	custom
Immutable backups	Yes	No

Azure Backup for AKS vs Velero

Azure Backup for AKS

Velero