BCDROpen source · Apache-2.0

Velero

Community project

An open-source, Kubernetes-native backup and restore tool that captures cluster and namespace state — and, paired with restic or Kopia, the volume data behind it — on a schedule, and can restore or migrate selected resources into another cluster for disaster recovery. Immutability depends on the object-storage backend (for example S3 Object Lock). Donated by Broadcom to the CNCF Sandbox in 2026.

Visit website Compare with…

Verified July 11, 2026Source: 1

Product type: Community project
Deployment: CLIHybrid
Organization size: Mid-marketEnterprise
Pricing tier: Free

Capability checklist

BCDR

How Velero measures up against the full Backup & Cyber Recovery taxonomy.

Immutable backups — not supported: Stores backup copies that can't be altered, encrypted, or deleted for a set retention period, so a clean recovery point survives even if attackers reach the backup system itself.
Air-gapped vaulting — not supported: Keeps an isolated recovery copy in a separate, network-segmented or offline vault that ransomware spreading through the production network can't reach.
Ransomware anomaly detection — not supported: Scans backups for signs of mass encryption or unusual change rates, flagging a ransomware attack and helping pinpoint the last clean recovery point.
DR orchestration & recovery testing — supported: Automates failover to standby infrastructure and regularly tests that a recovery actually works, instead of assuming the backups will restore when they're needed.
Broad workload coverage — not supported: Backs up many kinds of workloads — VMs, SaaS apps, Kubernetes, cloud services, and endpoints — from one platform rather than a separate tool per system.
Granular restore — supported: Recovers at the level actually needed — a single file, mailbox, VM, or database — and can bring workloads back quickly instead of only restoring everything at once.