# velero-io/velero

Backup and migrate Kubernetes applications and their persistent volumes

Repository: https://github.com/velero-io/velero
Canonical: https://ross.abutalabs.com/products/velero
Homepage: https://velero.io
Language: Go
License: Apache-2.0
License Family: permissive
Topics: kubernetes, disaster-recovery, backup, velero, hacktoberfest
Last push: 2026-08-26T17:16:55+00:00

## Health v2 (maintenance only)
Score: 92/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 78, longevity 100
- inputs: {"age_days": 3318, "days_push": 7, "days_rel": 68, "gap_med": 51, "n_releases_24m": 12}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 10254, forks 1602 (observed 2026-08-28T04:10:41.346926+00:00)

## What it is
Velero is an open-source tool (formerly Heptio Ark) that backs up and restores Kubernetes cluster resources and persistent volumes, supporting disaster recovery, data migration between clusters, and scheduled data protection. It consists of a server that runs in the cluster and a local command-line client, and works with public cloud platforms or on-premises.

## Use cases
- back up kubernetes cluster resources and persistent volumes
- restore a kubernetes cluster after data loss or outage
- migrate kubernetes workloads to another cluster
- set up scheduled backups with retention policies
- replicate a production cluster to dev and test environments
- perform disaster recovery for kubernetes applications

## When to choose
- you need kubernetes-native backup and restore of cluster resources and PVs
- you want disaster recovery with reduced time to recovery for cluster outages
- you need to migrate or replicate workloads across clusters or cloud providers
- you want scheduled backups, hooks, and volume snapshot support

## When to avoid
- you only need to back up data outside of Kubernetes (plain databases, VMs, bare files)
- you need full disk/image-level backups of the underlying nodes
- you run workloads outside Kubernetes entirely

## Facets
- artifact type: cli-tool
- maturity: stable
- function: backup, deployment, cli, self-hosted
- domain: cloud-computing, self-hosted
- platform: go, cli, cloud, self-hosted
- tags: kubernetes, disaster-recovery, persistent-volumes, cluster-migration, cncf, snapshot, restore, devops, containers, docker

## Member repositories
- velero-io/velero (main) score 92

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:41.346926+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:19:23.666140+00:00, confidence not recorded.
  - readme: https://github.com/velero-io/velero (fetched 2026-08-28T04:10:41.346926+00:00, sha f467efd60db9)
  - homepage: https://velero.io (fetched 2026-08-29T08:18:51.427161+00:00, sha 124c8805f40c)
  - site_page: https://velero.io/docs/v1.18 (fetched 2026-08-29T08:18:51.436805+00:00, sha 963c14c255fa)
  - site_page: https://velero.io/docs/main/start-contributing (fetched 2026-08-29T08:18:51.438891+00:00, sha 6f97be95e144)
  - site_page: https://velero.io/docs (fetched 2026-08-29T08:18:51.440753+00:00, sha 963c14c255fa)
- Data as of 2026-08-30T08:39:29.467469+00:00.
