Velero

Overview

Velero is an open-source Kubernetes backup and recovery tool for cluster operators. It is best suited to teams that need control over backup scope, storage integrations and cross-cluster moves. Its flexibility is a strength, but it depends on a functioning Kubernetes environment and storage setup.

Key features

Backups can cover an entire cluster or target selected namespaces and label-matched resources. That supports both broad disaster recovery and narrower protection, while leaving teams responsible for deciding what needs coverage.

Recurring schedules and pre- and post-backup hooks support repeatable backups and custom operations. Velero can restore after data loss and move resources between clusters, including replicating production clusters into development and test environments. Persistent-volume backups are supported, including CSI-backed volumes through Kubernetes CSI Snapshot APIs, provided the cluster and CSI driver meet the prerequisites.

The system pairs a server running on the Kubernetes cluster with a locally run command-line client. Maintainer-supported plugins cover AWS, Google Cloud, Microsoft Azure and VMware vSphere; community plugins extend the choices. The plugin architecture also permits custom storage integrations and backup or restore functions without modifying the core binary. It works with cloud or on-premises environments using object storage and, optionally, supported block-storage systems.

Installation requires access to a Kubernetes cluster, kubectl, compatible object storage and at least one plugin. File-system backup is not installed by default, so teams that need it must account for that setup. Although Windows workloads can be backed up, the Velero server still requires at least one Linux node. Some object-storage immutability settings can also interfere with backups because Velero needs to update backup metadata.

Velero documents support for self-signed storage-provider certificates and alternate identity mechanisms that avoid a credentials file. The project is a CNCF Sandbox project, with community support through GitHub issues and the Kubernetes Slack #velero-users channel.

Pricing

Velero is open source and free. Its free plan, Velero, costs nothing and supports cloud or on-premises use, but requires Kubernetes and storage-provider plugins. It includes persistent-volume backup, both application-consistency options, scheduled backups, custom retention and cross-cluster restore. Immutable backups are not supported.

There are no paid tiers to weigh against that free plan. The trade-off is operational: teams provide the cluster, compatible storage and plugin configuration, and rely on community rather than a paid support plan.

Platforms

Velero supports API, Linux, macOS, self-hosted and Windows environments. The CLI documentation lists macOS and Windows releases as well as downloadable client platforms. The server runs on Kubernetes, and Windows workload backups require a Linux node in the cluster.

Who it's for

Velero fits teams already operating Kubernetes that need scheduled cluster or resource backups, disaster recovery, persistent-volume protection, migration or replication to development and testing clusters. Its plugin model is useful when teams need provider flexibility or custom backup and restore behavior. It is a poor fit for organizations without Kubernetes expertise, or those that need immutable backups or a managed deployment and dedicated support.

Pros and cons

• Flexible backup scope: Teams can protect an entire cluster or focus on namespaces and label-selected resources.
• Useful recovery and migration workflows: Scheduled backups, restore, cross-cluster moves and production-to-test replication cover several Kubernetes operations in one tool.
• Extensible storage: Maintainer-supported and community plugins support cloud and on-premises options without changing the core binary.
• Setup is infrastructure-dependent: A Kubernetes cluster, kubectl, object storage and at least one plugin are prerequisites; file-system backup needs separate installation.
• Immutability can be a constraint: Some object-storage immutability settings may prevent backups from working as expected.
• Community support: Help is available through project channels, but the support model is community-based.

Alternatives

For a managed Kubernetes service rather than a cluster backup tool, consider Google Kubernetes Engine; its free tier uses monthly billing credits for zonal and Autopilot clusters.

KubeSphere Backup may suit teams that want a hosted repository with a defined free allowance: its free plan covers two protected applications, three days of retention and 10 GB.

For general-purpose managed-data backup across Linux, macOS and Windows, Plakar offers a free plan with up to 500 GB of managed data and a control plane deployed on infrastructure you own.

For Mac-only backup, Veeam Agent for Mac has a free edition, though it is limited to one backup job and does not back up directly to object storage.

Afi Kubernetes Backup is another Kubernetes backup option, with free licenses available by request for environments protecting fewer than 10 nodes.

For virtual-environment backup, Storware Backup & Recovery offers a free license, but technical support is not included.

Rancher Backup and Restore Operator is another free option.

For Kubernetes backup with a free tier capped at five nodes, consider Veeam Kasten for Kubernetes.

Explore more options in Kubernetes Backup Software and Container Backup Software.

Verdict

Choose Velero if your team runs Kubernetes and wants a free, extensible way to schedule backups, restore persistent volumes and move resources between clusters. Its plugin flexibility and broad recovery workflows are compelling; look elsewhere if you need immutable backups, managed operations or dedicated support.