Plays4. PlaysWhat you can do nowTo doDoneDismissedDeadlinesSince you lookedChecking Plays…Plays could not be checked. This does not mean there is nothing to do.Plays are held while the actionability and safety checks are measured.Personal Plays are held until the measured rollout checks pass.Deadline reminders are held until the measured rollout checks pass.Sign in to see Plays for your saved tools.Personal Plays and Deadlines are included with Practitioner, Researcher and Business.Sign inSee plansRetrySave a tool in Your stack to see Plays for it.We have not checked every saved tool yet. There is no all-clear to report.No new action was found in the checked release sources. Checked as ofNo published Plays for this tool in the last 90 days. This is not an all-clear for the version you run.No Plays in this view.No dated Plays for your saved tools.Why it mattersDo thisBefore you startEstimated effortEffort has not been measured.Read the sourceSource evidenceAct before it breaksNot for meRemind me next weekHidden from To do until next week.That change was not saved. Try again.Keep my Play answers in my accountOptional: save Done, Not for me and reminders privately in your account. Your tools are matched in this browser. No answers are sent until you opt in.Erase my Play answersYour Play answers and private calendar link have been erased.Create a private calendar linkReplace calendar linkRevoke calendar linkAnyone with this link can read generic deadline events. It contains no tool names, versions or answers. Revoke it any time.Private calendar feedWithin 30 daysWithin 7 daysPast the published dateMore than 30 days awayAct byNo earlier visit saved for this tool.breakingtotal Plays since your last reviewReview this toolMark this tool reviewedReview dates stay in this browser. Opening this list does not mark a tool reviewed.Category moves this monthThere is not enough documented history to call a category move this month.Category history is unavailable. No monthly comparison can be made.Category moves are held until the measured rollout checks pass.The documented monthly history shows no category move.What we got wrongThere are too few reviewed Plays to report a correction rate.Play corrections have not been measured for this month.Plays reviewedcorrectedPublished in the last 90 days. Breaking changes come first.Saved tools are matched in this browser; your versions are not sent.Your Plays{count} PlaysWhat you can do with the tools you runRelease sources for {checked} of {total} saved tools checked; no new plays match this edition.Add your toolsRead the details on the webIn {count} daysWe corrected {wrong} of {count} reviewed Plays.
Summary
Velero is an open-source command-line backup and recovery tool for Kubernetes resources and persistent volumes, aimed at platform engineers managing cluster continuity. It runs a server in the cluster alongside a locally run CLI, and works with public-cloud or on-premises storage. Beyond disaster recovery, it can migrate resources between clusters and replicate production into development or test environments; recent capabilities include wildcard namespace filters, concurrent backups, volume-group snapshots, and Windows workload support. Launched in 2017, it remains an active project.
Velero is an open-source tool that backs up, restores, and migrates Kubernetes cluster resources and persistent volumes.
Which Kubernetes resources and persistent volumes can I recover after cluster loss?
creates backups of cluster resources and volume data, then restores them so workloads and their stored data can be recovered; the result depends on what was included in the backup and what the storage setup can restore
How can I move workloads from one Kubernetes cluster to another?
backs up resources and persistent volumes from the source cluster and restores them into another cluster, providing a migration path rather than changing the source in place
How can I reproduce production in a development or test cluster?
captures production cluster resources and persistent volumes in a backup and restores that backup into the destination environment; the copy reflects what the backup includes
Which namespaces should be included in or excluded from a backup or restore?
applies include and exclude filters, including wildcard namespace patterns, so matching namespaces are selected in bulk rather than listed individually
Can I preserve data that spans several related volumes at one point in time?
uses volume-group snapshots for correlated volumes, providing a point-in-time snapshot across the group when the cluster’s snapshot capabilities support it
What happened during a backup or restore when I need to investigate a failure?
exposes operation status, storage-location availability, resource events, and diagnostics from data-mover activity, giving evidence about the operation; those records do not by themselves prove that every application-level transaction was consistent
Built from Velero's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
+Plugin system for extensible backup and restore logicNot checked yet · Date unknownAdd, remove, and manage third-party or user-defined plugins at runtime to extend object/block store backends and apply custom per-item backup or restore actions without recompiling the core binary.37 releases · 2 other sources · first seen Nov 2017▸
Also counts toward: Command-line interface, Plugin API support, Plugin system
+Restic-based volume backup and restoreNot checked yet · Date unknownBack up and restore nearly any Kubernetes volume type, including those without native snapshot support, using an integrated restic backend stored in the same object storage location as other Ark data.37 releases · 2 other sources · first seen Jul 2018▸
Also counts toward: Command-line interface, Disaster recovery
+Persistent volume snapshotsNot checked yet · Date unknownAutomatically snapshot and restore persistent volumes as part of backup and restore operations, with the option to opt out.30 releases · 2 other sources · first seen Sep 2017▸
Also counts toward: Command-line interface, Disaster recovery
+Velero install commandNot checked yet · Date unknownProvide a `velero install` CLI command to deploy Velero into a cluster, replacing static YAML installation files and supporting options such as pod annotations and credential configuration.22 releases · 5 other sources · first seen May 2019▸
Also counts toward: Command-line interface
+Human-readable describe output for backups, restores, and schedulesNot checked yet · Date unknownDisplay a formatted, human-friendly summary of a backup, restore, or schedule object including its phase, warnings, errors, and included/excluded resources.22 releases · 4 other sources · first seen Nov 2017▸
Also counts toward: Command-line interface
+CSI volume snapshot backup and restoreNot checked yet · Date unknownBack up and restore persistent volumes using the Kubernetes CSI VolumeSnapshot API, with dedicated download targets for CSI snapshot and snapshot-content metadata files and associated metrics.19 releases · first seen Jun 2022▸
Also counts toward: Disaster recovery, JSON data export
+Namespace-scoped restore filteringNot checked yet · Date unknownInclude or exclude specific namespaces when performing a restore using dedicated flags.11 releases · 5 other sources · first seen Sep 2017▸
Also counts toward: Command-line interface
+Prometheus metricsNot checked yet · Date unknownExpose Prometheus metrics covering total backup attempts (success and failure counts), total backup size in bytes, and backup durations.16 releases · first seen Jul 2018▸
+Backup and volume snapshot location configurationNot checked yet · Date unknownConfigure backup storage and volume snapshot destinations as distinct BackupStorageLocation and VolumeSnapshotLocation custom resources, replacing the single Config CRD, with support for bucket-level prefixes so multiple clusters can share one bucket.12 releases · 3 other sources · first seen Nov 2018▸
+Namespace-scoped backupNot checked yet · Date unknownBack up one or more specific namespaces, automatically including their persistent volumes while controlling whether unrelated cluster-scoped resources are included.9 releases · 4 other sources · first seen Oct 2017▸
Also counts toward: Command-line interface
+Backup and restore deletionNot checked yet · Date unknownDelete backups, restores, and schedules along with their associated data, with support for bulk deletion via label selectors or an --all flag.9 releases · 4 other sources · first seen Feb 2018▸
Also counts toward: Command-line interface
+Cluster-scoped resource control during backup and restoreNot checked yet · Date unknownExplicitly include or exclude cluster-scoped resources (such as nodes, CRDs, and ClusterRoles) during backup and restore operations.10 releases · 2 other sources · first seen Oct 2017▸
Also counts toward: Command-line interface
+Resource-type restore filteringNot checked yet · Date unknownSelectively include or exclude specific Kubernetes resource types when performing a restore.9 releases · 2 other sources · first seen Sep 2017▸
Also counts toward: Command-line interface
+Cloud provider configuration validationNot checked yet · Date unknownValidates cloud provider configurations at startup and makes the persistent volume provider setting optional.9 releases · first seen Sep 2017▸
+Repository maintenance configurationNot checked yet · Date unknownConfigure repository maintenance jobs via a ConfigMap, including settings for CPU/memory requests, limits, cache limits, and node selection.6 releases · 1 other source · first seen Nov 2024▸
+Tool rename and migration supportNot checked yet · Date unknownRename the tool from Heptio Ark to Velero, updating all imports, environment variables, and the binary name, with a migration command to convert pre-v0.11 Ark backup metadata in object storage to the current Velero format before upgrading to v1.0.5 releases · 2 other sources · first seen Feb 2019▸
Also counts toward: Command-line interface
+CRD v1beta1 backup compatibilityNot checked yet · Date unknownBack up schema-less CRDs through the v1beta1 API even when retrieved via the v1 endpoint, ensuring compatibility with clusters that enforce structural schemas on v1 CRDs.7 releases · first seen Mar 2020▸
+Backup sync controllerNot checked yet · Date unknownPeriodically synchronise backup metadata from object storage into the cluster, running once per minute with reduced cloud provider API calls.5 releases · 1 other source · first seen Nov 2018▸
Also counts toward: Scheduled jobs
+Schedule pause and resumeNot checked yet · Date unknownPause a backup schedule to prevent it from triggering during maintenance or at creation time, and unpause it later to resume automated backups.3 releases · 3 other sources · first seen Nov 2022▸
Also counts toward: Command-line interface
+Backup TTL managementNot checked yet · Date unknownControl how long backups are retained, with a configurable time-to-live that defaults to 30 days.5 releases · first seen Nov 2017▸
Also counts toward: Command-line interface
+Flexible server namespace deploymentNot checked yet · Date unknownRun the Ark server in any chosen namespace rather than a fixed, hard-coded one.5 releases · first seen Feb 2018▸
+Restore priority orderingNot checked yet · Date unknownControl the order in which Kubernetes resources are restored by specifying both high-priority resources restored first and low-priority resources restored last.4 releases · first seen Nov 2022▸
+Pre- and post-backup pod exec hooksNot checked yet · Date unknownExecute custom scripts inside containers during a pod backup, enabling actions such as flushing disk buffers or issuing database commands before data is captured.4 releases · first seen Oct 2017▸
previously: Pre-backup pod exec hooks
+Resource Modifier rules for restoreNot checked yet · Date unknownDefine JSON patch operations (add, replace, remove) in a ConfigMap to rewrite Kubernetes resource fields — such as storage class names or image references — during restore, without writing a custom RestoreItemAction plugin.3 releases · 1 other source · first seen Sep 2023▸
+Upload progress monitoring for backupsNot checked yet · Date unknownTrack and surface active upload state and partial-failure conditions during backup through dedicated BackupPhaseUploading and BackupPhaseUploadingPartialFailure phases.4 releases · first seen Sep 2021▸
+Native CLI binariesNot checked yet · Date unknownDistribute Ark as pre-built native binaries for macOS, Linux (amd64, arm64, arm), and Windows as release artifacts, replacing the previous container-based workflow.4 releases · first seen Oct 2017▸
Also counts toward: Command-line interface
+Volume selection policy filteringNot checked yet · Date unknownFilter which persistent volumes are included in backups based on PVC labels using a dedicated volume policy configuration.2 releases · 1 other source · first seen Apr 2025▸
+Azure multi-region and cross-subscription backup supportNot checked yet · Date unknownBack up and restore resources across Azure subscriptions and in Azure China and German cloud regions.3 releases · first seen Nov 2019▸
+Restore hooksNot checked yet · Date unknownExecute actions during pod restore by injecting init containers into pod specs or running commands in pod containers after restore completes.3 releases · first seen May 2020▸
+Service account secret restorationNot checked yet · Date unknownWhen restoring service accounts that already exist in the target cluster, copy their secrets and image pull secrets into the cluster.3 releases · first seen Jul 2018▸
+Server runtime profilingNot checked yet · Date unknownExpose pprof endpoints on the Velero server to capture runtime profiling data.2 releases · 1 other source · first seen Jan 2019▸
Also counts toward: Command-line interface
+Server status and version reportingNot checked yet · Date unknownExpose server version information via a `ServerStatusRequest` CRD and surface it in `velero version` output.3 releases · first seen Feb 2019▸
Also counts toward: Command-line interface
+Feature flag systemNot checked yet · Date unknownPass a --features argument to any Velero command to selectively enable pre-release or opt-in features at runtime.3 releases · first seen Nov 2019▸
Also counts toward: Command-line interface
+Structured JSON server loggingNot checked yet · Date unknownEnable JSON-formatted log output on the Velero server for structured logging and easier ingestion by log aggregation systems, with a configurable log level passed through to plugins.3 releases · first seen May 2019▸
Also counts toward: Command-line interface
+TLS verification bypass for S3-compatible storageNot checked yet · Date unknownAllow Velero to connect to S3-compatible object storage endpoints using self-signed certificates by disabling TLS verification via a server config option and a client-side flag.3 releases · first seen Nov 2019▸
Also counts toward: Command-line interface
+Encrypted backup storageNot checked yet · Date unknownStore backups in S3 using server-side encryption with AWS KMS keys.3 releases · first seen Sep 2017▸
previously: Encrypted backup storage via S3 SSE-KMS
+Top-level CLI subcommand aliasesNot checked yet · Date unknownUse `ark create` and `ark get` as shorthand top-level aliases for common subcommands.2 releases · 1 other source · first seen Oct 2017▸
Also counts toward: Command-line interface
+Schedule skipping supportNot checked yet · Date unknownSkip the first scheduled run immediately after creating a schedule to control when the next execution window begins.1 release · 1 other source · first seen Jan 2024▸
+Backup PVC configurationNot checked yet · Date unknownConfigure backup PVCs via a ConfigMap to control read-only mounting, storage class selection, and SELinux overrides for data mover pods.2 releases · first seen Nov 2024▸
+Node-agent configuration managementNot checked yet · Date unknownMake the node-agent configuration ConfigMap name configurable via server parameters instead of using a fixed name.2 releases · first seen Nov 2024▸
+Multi-architecture container imagesNot checked yet · Date unknownPublish multi-arch container images covering linux/amd64, linux/arm64, linux/arm, and linux/ppc64le via Docker manifest lists, requiring no user changes beyond updating the version tag.2 releases · first seen Mar 2020▸
+Kubernetes API pagination for large clustersNot checked yet · Date unknownChunk Kubernetes API LIST calls into smaller pages via a configurable server flag to prevent API server timeouts on large clusters.1 release · 1 other source · first seen Sep 2021▸
Also counts toward: Command-line interface
+Ordered resource backupNot checked yet · Date unknownBack up Kubernetes resources in a user-defined order via the --ordered-resources option, enabling dependency sequencing during restore.1 release · 1 other source · first seen Sep 2020▸
Also counts toward: Command-line interface, Disaster recovery
+Kubeconfig context targetingNot checked yet · Date unknownUse a global --kubecontext flag to direct Ark CLI commands at a non-default Kubernetes context.2 releases · first seen Apr 2018▸
Also counts toward: Command-line interface
+AWS Signature support and multi-profile credentialsNot checked yet · Date unknownSupport AWS Signature v1 for signed URLs and allow selecting a named AWS credentials profile per BackupStorageLocation.2 releases · first seen Jan 2019▸
+Volume tag propagationNot checked yet · Date unknownCopy tags from cloud volumes to their snapshots during backup and from snapshots back to new volumes during restore, across AWS, Azure, and GCP.1 release · 1 other source · first seen Apr 2018▸
+Backup validation with node-agent checkNot checked yet · Date unknownFail backup validation if the built-in data mover is requested but no node-agent pods are running.1 release · first seen Sep 2026▸
+Encrypted CSI volume data mover supportNot checked yet · Date unknownCopy namespace-scoped secrets and configmaps during backup/restore to enable the data mover for encrypted CSI volumes.1 release · first seen Sep 2026▸
+Backup Item Action skip supportNot checked yet · Date unknownSupport a SkipFromBackupAnnotation on objects returned by Backup Item Actions to exclude them from backup.1 release · first seen May 2026▸
Also counts toward: Plugin API support
+Custom volume policy actionsNot checked yet · Date unknownSupport a 'custom' action type in volume policies to allow user-defined logic for PVC inclusion.1 release · first seen May 2026▸
+Data mover resource limitsNot checked yet · Date unknownConfigure ephemeral storage requests and limits for data mover and maintenance job pods.1 release · first seen May 2026▸
+Backup concurrency controlNot checked yet · Date unknownEnable concurrent processing of multiple backups to improve throughput in multi-tenant environments.1 release · first seen Mar 2026▸
+Backup storage CA certificate managementNot checked yet · Date unknownSupport Secret-based CA certificates for BackupStorageLocation to manage TLS trust.1 release · first seen Mar 2026▸
+FS backup privileged mode supportNot checked yet · Date unknownAllow running file-system backup pods in privileged mode to handle volume types requiring elevated privileges.1 release · first seen Mar 2026▸
+Windows cluster supportNot checked yet · Date unknownRun Velero components including node-agent, data mover, and maintenance jobs on Windows nodes to back up and restore Windows workloads.1 release · first seen Apr 2025▸
Also counts toward: Disaster recovery
+Pod Security Admission namespace labellingNot checked yet · Date unknownLabels the Velero-installed namespace so that Kubernetes Pod Security Admission (PSA) policies are satisfied during installation.1 release · first seen Mar 2023▸
+IPv6 dual-stack environment supportNot checked yet · Date unknownVelero functionality is verified to work on IPv6 dual-stack Kubernetes environments.1 release · first seen Feb 2022▸
+Distroless container base imagesNot checked yet · Date unknownPackage Velero using distroless base images that contain no shell, reducing the attack surface at the cost of interactive exec access to containers.1 release · first seen Sep 2021▸
+Shell completionNot checked yet · Date unknownGenerate shell completion scripts for Velero CLI commands, with support for fish shell in addition to previously supported shells.1 release · first seen Apr 2021▸
+S3-compatible storage compatibilityNot checked yet · Date unknownImprove compatibility with S3-compatible object storage systems such as StorageGrid by removing assumptions about response encoding.1 release · first seen Sep 2020▸
+Azure credentials file supportNot checked yet · Date unknownConfigure Azure provider credentials by pointing to a `.env` file via the `$AZURE_CREDENTIALS_FILE` environment variable rather than embedding them directly.1 release · first seen May 2019▸
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for Velero, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Velero puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
See whether Velero's docs change before or after its release notes, release by release.
Documentation timing is included with Practitioner, Researcher and Business. When the docs come first, you can read about a change before it's announced.
We check each docs page on a fixed schedule, so every gap is a range rather than one number.
A release we can't place on either side is shown as "Can't tell".
Nothing first seen in this window. That doesn't mean Velero shipped nothing, only that we found no record of it.
Changes per month New Updated Retired
2026-11
1
How we count
Read from 5 of 50 release notes and docs updates we hold for Velero. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Velero's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
Show
Coverage in all entries
50 entries
No entries match these filters.
November 20267
September 20261
August 20261
May 20261
March 20261
November 20251
September 20251
July 20251
April 20251
November 20241
June 20241
January 20241
December 20231
October 20231
September 20231
April 20231
March 20231
November 20222
September 20221
June 20221
March 20221
February 20221
September 20211
August 20211
April 20211
October 20201
September 20201
May 20201
April 20201
March 20201
November 20191
August 20191
May 20192
February 20191
January 20191
November 20181
July 20181
April 20181
February 20181
November 20171
October 20171
September 20171
Project health
Issue, contributor and maintainer activity in velero-io/velero, 2023-12 – 2026-11,
as of 2026-11-03. Twelve-month figures first; the trend lines run
the whole window.
Contributorsnot measureddistinct committers, last 12 months
Maintainersnot measuredcore set, last 12 months
Bus factornot measuredcommitters behind half the commits
Community-filed69%of issues opened, last 12 months
Median time to close14 daysfirst maintainer reply 3.9 days
Open backlog655of 4,885 issues ever filed
Issues opened / month23 · 26communitymaintainers
Open backlog655
Contributors / monthnot measured
Commits / monthnot measured
Starsnot measured
Issue themes, last 12 months
bugs 4%
features 6%
docs 1%
other 89%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
How Velero helps against real attacks
Velero documents controls for 1 defense technology seen in attacks this year.
Copy this, send it to your AI assistant, then come back with its reply.
Nothing is sent from here. You paste the reply in the next step.
1 Copy
2 Paste
3 Confirm
Paste the reply
One tool per line is best. Versions are optional, and any format works. Names we don’t track are sent to us, without versions, so we can consider adding them.