Bnkr vs Velero
Bnkr
bnkr.isVelero
velero.ioSide by side
| Figure | Bnkr | Velero |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Container Backup Software | 7.8 (#10) | 8.0 (#9) |
| Spec score · Kubernetes Backup Software | 7.8 (#13) | 8.0 (#11) |
| Deployment | The README says Bnkr can run as a Kubernetes deployment with a service account that has sufficient access to the data being backed up. | Velero can run with a cloud provider or on premises and consists of a server running in the cluster and a locally run command-line client. |
| Purpose | Bnkr is a Kubernetes backup and migration application. | Velero backs up and restores Kubernetes cluster resources and persistent volumes, supports disaster recovery, and migrates resources between clusters. |
Plans
In their own words
Bnkr
Bnkr is a free, open-source Kubernetes backup and migration application focused on valuable data inside a cluster rather than the whole cluster. It backs up files in Pods, Deployments, and StatefulSets, plus MySQL, MariaDB, PostgreSQL, and MongoDB databases. Schedules can run hourly, daily, weekly, monthly, yearly, or through a cron formula, and manual backup and restore are available. Email notifications report successful or failed backups and migrations to multiple recipients. Bnkr describes bidirectional migration of files and supported databases between Kubernetes, servers, and S3. The project runs as a single-binary web server and can be deployed in Kubernetes with a service account able to access backup data. Its README recommends the official image because some dependencies are external tools. Bnkr is available on the web or for self-hosting, uses the MIT license, and lists more than 20 themes. The free plan is listed at free, with no usage limit stated.
Velero
Velero is an open-source tool for backing up and restoring Kubernetes resources and persistent volumes, recovering from data loss, and moving resources between clusters. Backups can cover an entire cluster or selected resources chosen by namespace or label. Recurring schedules and pre- and post-backup hooks support repeatable operations. Velero can restore after data loss and migrate resources, including replication from production to development or test clusters. Its server runs on Kubernetes, while a command-line client runs locally. Storage integrations include maintainer-supported plugins for AWS, Google Cloud, Microsoft Azure, and VMware vSphere, plus community-maintained options. The plugin architecture also permits custom storage integrations and backup or restore behavior. Velero can be used in cloud or on-premises environments with object storage and, optionally, supported block storage. Installation requires access to a Kubernetes cluster, kubectl, a compatible object storage provider, and at least one plugin. File system backup is not installed by default. The project provides community support through GitHub and Kubernetes Slack.