Recovering across AWS, Azure and Google Cloud: what each tool covers

Why is a cloud logo not enough?

A vendor's home page may list every major cloud because its product can see them. Recovery support is a narrower claim: the tool can capture the resources in that cloud and bring them back. When you run more than one cloud, check recovery coverage per cloud, not the logo row.

What does each tool document?

• Firefly: its Backup and DR coverage table lists 190 AWS resource types across 48 services and 86 Azure resource types across 14 services. Its product page lists Google Cloud, OCI and Kubernetes for inventory and codification, but Google Cloud is not in the backup coverage table.
• Arpio: documents AWS and Azure. Arpio announced its Azure capabilities on 4 March 2026; Google Cloud is not currently supported, and its June 2026 Series A announcement says the funding will expand support to it.
• Commvault Cloud Rewind: names AWS, Azure and Google Cloud and is listed on all three marketplaces. Its docs say cross-account recovery is currently AWS only.
• ControlMonkey: names AWS, Azure and Google Cloud for daily configuration snapshots, plus more than 30 SaaS providers.
• Cohesity, not scored: the Cloud Rebuild page states select AWS workloads in Terraform-provisioned environments. Azure and Google Cloud recovery were not covered in our sources.
• StackGuardian, not scored: covers AWS, Azure and Google Cloud for discovery, codification and drift detection, with no recovery product.
• Scalr, not scored: stores Terraform state in Google Cloud, Azure or AWS buckets, with no recovery product.
• Gambit Security: named clouds are not published on its site.

How should a multi-cloud team decide?

Start from where your critical applications run, not from the full estate. If they are all on AWS, every recovery tool here documents the cloud you need. If some run on Azure, the shortlist narrows to Firefly, Arpio, Commvault Cloud Rewind and ControlMonkey. If Google Cloud recovery matters, Commvault Cloud Rewind and ControlMonkey are the tools here that document it; ask the others for dates.

Pricing can depend on it too: Arpio publishes separate single-cloud and multi-cloud prices for each tier.

What about other platforms?

Some tools extend beyond the three large clouds. Firefly lists OCI and Kubernetes on its product page, announced VMware vSphere support on 31 August 2026 and Databricks workspace support on 16 September 2026. Arpio announced recovery for Amazon Bedrock on 25 August 2026. These are vendor announcements; check what each covers for recovery, not only for inventory, before relying on it. A short written answer from the vendor, naming the resource types covered, is worth more than a logo on a home page.

What should you take from this lesson?

Make a table of your critical applications by cloud, then ask each vendor to confirm recovery support, in writing, for the resource types those applications use. The recovery time estimator flags tools that do not document a cloud you select.