Self-Hosted · OpenShift 4.12 – 4.17

OpenShift Virtualization backup that covers VMs and containers in one platform

CloudCasa delivers backup, restore, migration, and disaster recovery for OpenShift clusters — including KubeVirt VM workloads. Self-hosted deployment, immutable recovery points, and centralized management across environments.

Full-stack backup for KubeVirt VMs, PVCs, and Kubernetes resources via CSI snapshots
Immutable, lockable recovery points designed to survive ransomware events
Guided restore and migration across clusters with storage class and namespace remapping
Single pane of glass for multi-cluster backup operations, on-prem and cloud

Red Hat Certified Compatible with OCP 4.12–4.17 · Velero/OADP replacement

Request Self-Hosted Trial Access

Start your 60-day trial for up to 5 worker nodes. Tell us about your environment. We'll follow up within one business day.

First name

Last name

Work email

Company

OpenShift clusters

Virtual machines

We respond within 1 business day. Your data stays yours.

The Challenge

OpenShift resilience ≠ backup

OpenShift keeps workloads running. It does not create independent recovery points, enforce retention policies, or enable clean cross-cluster restore when a cluster is compromised, misconfigured, or lost. That gap is where CloudCasa operates.

Challenge

CloudCasa Solution

VM and container sprawlVMs and containers spread across clusters with no unified protection strategy or consistent retention policy.

One platform, full stackProtects OpenShift Virtualization (KubeVirt) VMs and Kubernetes workloads together, with shared policies and a single catalog.

Ransomware exposureStandard backups can be targeted and deleted or encrypted alongside production data.

Immutable, lockable recovery pointsBackup data is written to immutable storage. Retention locks prevent deletion — including by authenticated users.

Restore without a playbookRestores in incident conditions become improvised, error-prone, and slow.

Structured, repeatable workflowsGuided restore flows with storage class mapping, namespace renaming, and progress monitoring. Testable before you need them.

No cross-cluster visibilityEach cluster has its own backup state. No unified view of coverage, gaps, or job status.

Centralized operationsSingle dashboard for backup status, policy coverage, and recovery operations across all clusters and environments.

Replacing Velero or OADP?

CloudCasa provides a managed alternative to Velero and OADP for teams who need centralized cataloging, retention policies, immutable storage, and a consistent UI — without maintaining their own Velero configuration per cluster.

See it in a trial

The Workflow

How it works

CloudCasa uses CSI snapshot integration and KubeVirt-native APIs to protect both Kubernetes resources and VM workloads consistently, without separate toolchains.

Deploy in your environment

Install CloudCasa via Helm charts. Self-hosted deployment runs within your cluster — no data leaves your environment. Compatible with air-gapped and restricted networks.

OCP 4.12 – 4.17

Define backup policies

Set policies for namespaces, resource types, PVCs, and KubeVirt VM workloads. Assign retention schedules and choose your backup destination — S3-compatible, ODF/Ceph, or any on-prem object store.

CSI + KubeVirt APIs

Restore, migrate, or recover

Use guided workflows to restore to the same or a different cluster. Includes storage class mapping, namespace transformation, and selective resource restore. Test restores without affecting production.

Cross-cluster · Multi-cloud

Platform Capabilities

Built for OpenShift Virtualization at scale

Everything in one platform, managed from one control plane.

🖥

VM Backup & Restore

Full protection for KubeVirt VMs using native APIs. Covers VM definitions, volumes, and associated PVCs — on-prem or in the cloud.

🔒

Immutable Recovery Points

Backup data written to lockable storage with configurable retention. Resistant to deletion by ransomware and unauthorized users.

🔐

Encryption in Transit and at Rest

Data is encrypted throughout the backup lifecycle — during transfer and in storage — with no dependency on SaaS key management.

📊

Single Pane of Glass

Unified management for backup, recovery, and migration across all OpenShift clusters, with centralized job status and policy coverage views.

🔁

Guided Restore Workflows

Structured restore paths with storage class and namespace mapping. Consistent enough to test regularly, reliable enough for incident response.

📸

CSI Snapshot Integration

Leverages CSI snapshot APIs for consistent, crash-safe PVC backup across supported storage backends — no agents required inside workloads.

Deployment Model

Why self-hosted for OpenShift Virtualization?

Some environments cannot send backup data or metadata through a SaaS control plane. Self-hosted CloudCasa is designed for those requirements without sacrificing operational capability.

Data sovereignty

Backup data and catalog metadata remain in your infrastructure. Aligned with internal policies and regional data residency requirements.

Air-gap compatible

Fully operational in environments with no outbound internet access. Images can be mirrored to an internal registry. No call-home dependencies during backup or restore.

Multi-tenant RBAC

Namespace-scoped access control lets different teams manage their own backup policies without cross-cluster visibility. Plugs into OpenShift's existing RBAC model.

FAQ

Common questions

Straight answers to the questions OpenShift teams ask before evaluating backup tooling.

Which OpenShift versions are supported?

CloudCasa supports OpenShift Container Platform 4.12 through 4.17, including OpenShift Virtualization on those versions. Support for new OCP releases is qualified through the Red Hat certification process. Confirm the exact version match during your trial setup call if you are running an older or pre-release version.

How long does initial deployment and first backup take?

Most teams complete onboarding within 10 minutes with SaaS, and about 1 to 2 hours with the self-hosted deployment. The first full backup run time depends on PVC and VM volume sizes. Incremental backups using CSI snapshots are significantly faster after the first run.

Where does backup data go? What storage backends are supported?

CloudCasa supports S3-compatible object storage, including AWS S3, MinIO, NetApp StorageGRID, and similar backends. It also works with ODF/Ceph for on-prem deployments. You configure the destination during setup — nothing is sent to CloudCasa-managed infrastructure in the self-hosted model.

Can I migrate OpenShift workloads between on-prem and cloud clusters?

Yes. CloudCasa supports restore and migration between clusters regardless of whether they are on-prem or cloud-hosted. Restore operations include storage class mapping and namespace renaming, so you can adapt workloads to the target environment without manual intervention.

How does multi-tenancy work?

CloudCasa uses namespace-scoped RBAC to isolate backup and restore permissions between teams. A DevOps team managing namespace A cannot see or modify backup policies for namespace B. This maps directly to OpenShift's existing RBAC model — no separate identity system required.

Does it work fully air-gapped with no internet access?

Yes. The self-hosted deployment has no runtime dependency on outbound internet connectivity. Container images can be mirrored to an internal registry. Backup and restore operations run entirely within your network. License validation behavior in fully air-gapped environments is confirmed during the trial setup call.

Why not rely on built-in OpenShift resilience?

OpenShift's built-in resilience — node failover, etcd replication, cluster health management — is designed to keep services running. It does not create independent, immutable recovery points, enforce retention schedules, or support clean cross-cluster restore after deletion, corruption, or a compromise event. Those are different problems that require independent backup tooling.