Virtualization Platform RFP Template (Free): Requirements
Paste-ready virtualization platform requirements (hypervisor, clustering and HA, storage, networking, VM migration, automation, security), vendor questions and a weighted scoring rubric.
Paste-ready Kubernetes backup requirements (application-consistent backup, CSI snapshots, cross-cluster restore, immutability, RBAC, GitOps), sharp vendor questions and a weighted scoring rubric.

See the structure before you download. The Word file has every section listed below, ready to fill in.
The sections in the document, in order.
Use this Kubernetes backup RFP template when you need to protect stateful applications running on Kubernetes, including their resources, configuration and persistent volumes, across every cluster and cloud you run.
It's written for the platform engineering, backup, security and procurement team running the evaluation, and it covers the whole process: when to issue an RFI first, the requirements to send, the questions that separate vendors, how to prove restores in a proof of concept, and how to score the answers.
Download the editable Microsoft Word version below. Every requirement, vendor question and scoring weight on this page is in the document, ready to tailor and send.
A Kubernetes backup evaluation involves platform engineering, storage, security and the teams that own stateful applications. The proof of concept matters more than the written answers, because a restore either works on your clusters or it doesn't. The example schedule in this template runs about 10 weeks from kickoff to contract award; allow longer if you need to prove restores across several clouds or regions.
Each line is written to paste straight into your RFP. Must-have means a vendor that cannot meet it is out; Nice-to-have earns extra points. Change the priorities to fit your situation, and delete what doesn't apply.
| ID | Requirement | Priority |
|---|---|---|
| F1 | Backup of each application's namespace-scoped resources (deployments, stateful sets, services, config maps, secrets, service accounts, persistent volume claims and custom resources) together with its persistent volume data, as one restorable unit. | Must-have |
| F2 | Capture of the cluster-scoped resources an application depends on, such as custom resource definitions, storage classes and cluster roles, so the application can be restored into a new, empty cluster. | Must-have |
| F3 | Backup scope defined by cluster, namespace, label selector or application grouping, with automatic protection of new namespaces and workloads that match a policy. | Must-have |
| F4 | Application-consistent backups using pre- and post-snapshot hooks or reusable templates that quiesce, flush or dump databases and other stateful services. List the databases that have prebuilt templates. | Must-have |
| F5 | Persistent volume protection through the Kubernetes CSI snapshot API, with snapshot data exported to a separate backup target rather than kept only as snapshots on the primary storage. | Must-have |
| F6 | A file-system-level backup method for volumes whose CSI driver does not support snapshots. State the performance and privilege trade-offs. | Must-have |
| F7 | Crash-consistent snapshots of all of an application's volumes at the same moment, using Kubernetes volume group snapshots where the CSI driver supports them. | Nice-to-have |
| F8 | Backup schedules and retention per policy (hourly, daily, weekly, monthly and yearly), with several backup targets per policy and separate retention for each target. | Must-have |
| F9 | Restore of a whole namespace, a single application, individual Kubernetes resources or a single persistent volume, to the original namespace or a new one. | Must-have |
| F10 | File-level restore from a persistent volume backup without restoring the whole volume. | Nice-to-have |
| F11 | Restore to a different cluster, region, cloud or Kubernetes distribution, with built-in transformations during restore (for example, changing the namespace, storage class, image registry, labels or ingress hostnames). | Must-have |
| F12 | Migration of applications between clusters, distributions and clouds (for example, for Kubernetes upgrades or cloud moves) using the same backup and restore workflow. | Must-have |
| F13 | Disaster recovery plans that restore a defined set of applications to a standby cluster in a set order, with pre- and post-restore steps, and that can be run on demand as a test or as a failover. | Must-have |
| F14 | Scheduled restores into a standby or isolated test cluster, for warm-standby disaster recovery and automated recovery testing, with a pass or fail report for each run. | Nice-to-have |
| F15 | Self-service backup and restore for application teams within their own namespaces, inside limits set by platform administrators. | Must-have |
| F16 | Protection of virtual machines that run on Kubernetes through a Kubernetes-native virtualization layer, if they are in scope. | Nice-to-have |
| ID | Requirement | Priority |
|---|---|---|
| T1 | Kubernetes-native deployment by Helm chart or operator, with configuration held as Kubernetes custom resources. List each in-cluster component and its CPU, memory and storage requirements. | Must-have |
| T2 | In-cluster components that run with the minimum permissions they need. Identify any component that needs privileged or host-level access, and explain why. | Must-have |
| T3 | Support for [list Kubernetes distributions and managed Kubernetes services in use], and for the current Kubernetes minor release plus at least two prior minor releases. State how soon new upstream releases are supported. | Must-have |
| T4 | One console and API to manage backup policies, jobs and restores across all our clusters (on-premises, cloud and edge). State whether the management plane is self-hosted, vendor-hosted, or available as both. | Must-have |
| T5 | Support for [number] clusters, [number] namespaces, [number] persistent volumes and [capacity] of protected data, with parallel backup and restore and documented throughput limits. | Must-have |
| T6 | Incremental backups after the first full copy, with deduplication and compression of exported data. State whether incremental backups use changed block tracking from the storage system or CSI driver. | Must-have |
| T7 | Recovery of the backup platform itself: if the cluster hosting the backup software is lost, we can install it in a new cluster and reconnect to existing backups and their catalog. | Must-have |
| T8 | Installation and operation in air-gapped environments, using our private container registry. | Nice-to-have |
| ID | Requirement | Priority |
|---|---|---|
| I1 | Single sign-on to the console and API via OIDC or SAML 2.0 with our identity provider, mapping identity-provider groups to roles. | Must-have |
| I2 | Validated snapshot and restore support for [list CSI drivers and storage platforms in use], with a published support matrix. | Must-have |
| I3 | Backup targets including S3-compatible object storage, public cloud object storage and NFS [list the targets you use]. | Must-have |
| I4 | Backup policies, schedules and restore definitions expressed as Kubernetes custom resources or declarative files that we can keep in Git and apply through our GitOps and CI/CD tooling. | Must-have |
| I5 | A documented REST API and command-line interface covering every function available in the console. | Must-have |
| I6 | Metrics in a Prometheus-compatible format, and alerts for failed, missed or late jobs and unprotected workloads by email, webhook and our ticketing (ITSM) and incident tools. | Must-have |
| I7 | Streaming of job, audit and security event logs to our SIEM in a documented format. | Must-have |
| I8 | Infrastructure-as-code support (for example, a Terraform provider) for platform configuration and cluster onboarding. | Nice-to-have |
| ID | Requirement | Priority |
|---|---|---|
| S1 | Role-based access aligned with Kubernetes namespaces and RBAC, so users can only see, back up and restore what they are authorized for. Include a read-only role for auditors. | Must-have |
| S2 | Immutable backup copies using object lock (WORM) on supported targets. Explain how the platform's retention settings interact with the storage-level lock. | Must-have |
| S3 | At least one isolated copy of each backup, held in a separate account or logically air-gapped target with separate credentials, so compromised cluster or Kubernetes administrator credentials cannot delete it. | Must-have |
| S4 | Multi-factor or multi-person approval for destructive actions such as deleting backups, shortening retention or disabling policies. | Nice-to-have |
| S5 | Encryption of backup data in transit (TLS 1.2 or higher) and at rest, with customer-managed keys held in our key management system (via KMIP or a cloud key management service). Kubernetes Secrets captured in backups must stay encrypted. | Must-have |
| S6 | An audit log of every backup, restore, policy and administrative action with user attribution, exportable and retained for [period]. | Must-have |
| S7 | Detection of anomalies in backup data or activity, such as unusual change rates, mass deletion or newly encrypted content, with affected restore points flagged so we can find the last clean copy. | Nice-to-have |
| S8 | For any vendor-hosted components: a current SOC 2 Type II report and ISO/IEC 27001 certification, a data processing agreement, a list of sub-processors, a choice of region for stored metadata, and a contractual time limit for notifying us of security incidents. | Must-have |
| S9 | Use of FIPS 140-validated cryptographic modules. Make this Must-have if you are a public-sector or regulated buyer that requires it. | Nice-to-have |
| ID | Requirement | Priority |
|---|---|---|
| M1 | An implementation plan covering an inventory of clusters, namespaces, storage classes and stateful applications; protection tiers with RPO, RTO and retention; and a phased rollout from non-production to production clusters. | Must-have |
| M2 | A migration approach from our current backup tooling that keeps existing backups restorable until their retention expires. | Must-have |
| M3 | Identification of who delivers the implementation (vendor, partner or both) and the Kubernetes experience of the named team. | Must-have |
| M4 | A tested restore of [named critical applications] into a different cluster before production sign-off, with recovery times recorded. | Must-have |
| M5 | A published supported-version policy and upgrade path for the software and its in-cluster components, with backups taken by earlier releases remaining restorable. | Must-have |
| M6 | 24×7 support for critical issues, with response-time targets by severity. For vendor-hosted components, an availability SLA with service credits and a public status page. | Must-have |
| M7 | Training and documentation for platform administrators and application teams, including recovery runbook templates. | Nice-to-have |
| ID | Requirement | Priority |
|---|---|---|
| C1 | Pricing broken down by component, metric (for example, per node, per cluster, per application or per terabyte protected) and term, showing list price, discount and net price. | Must-have |
| C2 | An explanation of how usage is counted for clusters that autoscale, short-lived clusters, non-production clusters and standby disaster recovery clusters. | Must-have |
| C3 | Any costs beyond the license that the proposed design creates, such as a separately priced management plane, vendor-hosted storage, or data transfer between regions or clouds. | Must-have |
| C4 | A cap on price increases at renewal. State the cap. | Must-have |
| C5 | A proof of concept at no charge, with the vendor's engineering support. | Nice-to-have |
| C6 | Exit terms that keep our backups restorable after the contract ends (for example, read-only access for the remaining retention period, or a documented backup format), plus transition assistance. | Must-have |
These questions are designed to separate vendors, not to collect brochure answers. Ask for evidence: a demo, a document or a reference.
Score each criterion from 1 to 5, multiply by its weight, and add the results. The weights below are a starting point; agree on your own before any proposals arrive so the scoring can't be bent around a favorite.
| Criterion | Weight | What a strong response shows |
|---|---|---|
| Backup and restore coverage | 25% | Every Must-have met in a generally available release, with application-consistent backup and restore into a new, empty cluster demonstrated on your own stateful applications. |
| Recovery, disaster recovery and mobility | 15% | Restores across clusters, storage classes and clouds without manual fixes, ordered disaster recovery plans, and recovery times measured in the proof of concept. |
| Ransomware resilience and security | 15% | Immutable, isolated copies that cluster-admin credentials can't delete, customer-managed encryption keys, and access scoped to Kubernetes namespaces and RBAC. |
| Platform coverage and scale | 15% | Support for every distribution, Kubernetes version and CSI driver you run, a small and well-documented in-cluster footprint, and evidence at your scale. |
| Automation and integration | 10% | Policies as code that fit your GitOps workflow, a complete API and CLI, and metrics, alerts and logs flowing into your monitoring, SIEM and ticketing tools. |
| Implementation and support | 10% | A credible phased plan, an experienced named team, a clear supported-version policy, and support targets that match your recovery objectives. |
| Commercials and total cost | 10% | A licensing metric that stays predictable as clusters autoscale, a renewal cap, and exit terms that keep backups restorable, over a three-year view. |
| Total | 100% |
Scoring scale
Your environment (clusters, distributions, storage platforms, CSI drivers and stateful applications) and protection tiers with RPO, RTO and retention targets; requirements for application-consistent backup, CSI snapshots, restore granularity, cross-cluster restore and migration, immutability, encryption, RBAC and policy-as-code, each marked Must-have or Nice-to-have; questions that make vendors demonstrate restores; support and pricing terms; and the rubric you'll score with. This template includes all of them.
Yes, for anything stateful. Git holds the desired state of your manifests, but not the data in persistent volumes, secrets you keep out of Git, or resources that operators and controllers create at runtime. Rebuilding from Git also doesn't give you a point-in-time copy to roll back to after data corruption or ransomware. The two work together: keep your backup policies in Git as well, and use backups to recover data and whole applications.
Not on its own. A CSI snapshot usually stays with the storage system or cloud account that holds the original volume, so it can be lost or compromised along with them. It's a fast way to capture a consistent point in time; a backup platform should then copy that data to a separate, preferably immutable target, together with the Kubernetes resources needed to restore the application.
Either can work. Some general-purpose backup platforms include Kubernetes protection, and some products are built only for Kubernetes. Send this RFP to both kinds and score them against the same requirements, paying particular attention to application consistency, restore into a new cluster, support for your distributions and CSI drivers, and how policies fit your GitOps workflow.
The example schedule in this template runs about 10 weeks from kickoff to contract award, including three weeks for vendor responses and about three weeks for a proof of concept. Allow more time if a short RFI comes first, or if you need to prove restores across several clouds or regions.
Acronis
Arcserve
AvePoint
Axcient
Backblaze
Bacula Systems
Barracuda Networks
Cohesity
Commvault
CrashPlan
Datto
Dell Technologies
Druva
Hornetsecurity
HYCU
IBM
Keepit
MSP360
N-able
N2WNNAKIVO
OpenText
Rubrik
Unitrends
Veeam
Listed A to Z from vendors' own descriptions. Listings are free, unranked and not an endorsement. See all Backup vendors →
Paste-ready virtualization platform requirements (hypervisor, clustering and HA, storage, networking, VM migration, automation, security), vendor questions and a weighted scoring rubric.
A free, vendor-neutral RFP for hiring an agency or development partner to build custom software, with user stories, delivery questions, code ownership…
Paste-ready Microsoft 365 backup requirements (Exchange Online, OneDrive, SharePoint, Teams, Entra ID, restore, immutability, legal hold), sharp vendor questions and a scoring…
Please provide your feedback below.
"*" indicates required fields