CloudRecover is Commvault’s recovery solution for cloud-native data across clouds. It is a fully managed, serverless service that helps protect object storage, databases, and lakehouse tables at cloud scale; helps keep copies immutable in an isolated vault; and helps identify a clean recovery point before anything is restored.

Native replication, versioning, and snapshots create copies but were not designed for fast, reliable recovery at scale, and they can let corruption propagate. CloudRecover recovers in place across billions of objects, holds copies outside the production account, and scores supported EC2 and EBS backups when ThreatDetect is enabled to help teams assess which copies appear clean. 

No. CloudRecover is serverless and agentless: no dedicated backup infrastructure to manage, with required connection resources deployed in your account, nothing to size or patch, and protection that scales as data grows.

For supported workloads, incremental-forever protection captures changes after an initial full backup, so you pay only for what you protect, at 30%+ lower backup TCO than native approaches. 

Amazon S3 Versioning lets you return an object to an earlier version, but only one object at a time. Modern applications and AI workloads need that across entire buckets of millions or billions of objects, impractical by hand. CloudRecover’s in-place rollback automates it, reverting objects to a chosen version and point in time within supported service limits. 

Each supported backup analyzed with ThreatDetect enabled receives an assessment before you restore. ThreatDetect scores each supported backup for ransomware risk from inside the backup pipeline. It builds a baseline for each asset and correlates multiple signals, so no single metric triggers a verdict. Each backup carries a risk score, a confidence level, and a downloadable report showing which restore points appear clean. 

Yes. CloudRecover is API-first, with a published Terraform provider and infrastructure-as-code modules, so teams can declare and manage protection from code. The console is an option, not a requirement.

Cloud providers are responsible for the data security and reliability of their infrastructure; customers are responsible for their data and applications, including access control. That means restoring data after an overwrite, deletion, corruption, or attack is the customer’s job, whether the cause was human error, a bad code push or ransomware. 

Three ways. Every copy is held immutable in an air-gapped vault outside your production account, so isolation helps protect backup copies if production credentials are compromised. Supported EC2 and EBS backups can be scored for ransomware risk when ThreatDetect is enabled, so you can assess which restore points appear clean. And in-place rollback helps return billions of objects to the moment before the attack, in hours rather than weeks.