Skip to main content Skip to navigation Skip to footer
MULTI-CLOUD

When AWS goes down, you don’t

Your infrastructure runs on multiple clouds. When one fails, the others take over. Automatically.

Every cloud has backup. None fail over to another cloud in minutes. Rediacc does.

$ rdc repo sync push-all
Computing incremental diff .... done
Transferring delta (2.4 GB of 380 GB) .. done
Applying snapshot on secondary .. done
Verifying 8 containers ........ 8/8 healthy
✓ Replication complete: secondary-dc in sync
⚠ Alert: primary health check failed (us-east-1 unreachable)
Failover initiated ............ done
DNS updated to secondary-dc ... propagated
Delta: 2.4 GB    Failover: 22s    Services: 8/8 online    Downtime: 0

Illustrative output; actual runs may include extra logs. CLI reference: rdc repo sync

<30s
Failover Time
99.99%
Data Integrity
3+
Cloud Providers Supported
THE PROBLEM

Single-cloud is a single point of failure

Critical cloud outage events increased 18% year-over-year in 2024, lasted 18.7% longer, and human error caused 68% of them [2]. When your only cloud goes down, everything goes down. Your customers, your revenue, your reputation. All hostage to someone else’s infrastructure.

$300K+ per hour of downtime for 90% of mid-to-large enterprises ITIC 2024 Hourly Cost of Downtime Survey [1]
18% increase in critical cloud outage events in 2024 Parametrix 2024 Cloud Outage Risk Report [2]
$400B annual downtime cost for Global 2000 companies Splunk / Oxford Economics 2024 [3]
The old way
Min 0 Outage detected
Min 15 Assess damage
Hour 1 Manual failover
Hour 4 DNS propagation
Hour 8+ Still degraded
With Rediacc
Detect
<30s
Online
THE REAL COST

What does a cloud outage cost you?

Drag the sliders to match your business. See the real cost of single-cloud dependency.

Calculate your outage exposure

Without Rediacc
Revenue lost to outages$80,000
Failover labor cost$4,800
Customer churn (est.)$16,000
SLA penalty risk$8,000
Annual outage cost
$108,800
With Rediacc
Revenue lost to outages$0
Failover labor cost$0
Customer churn (est.)$0
SLA penalty risk$0
Annual outage cost
$0
Revenue loss: hourly revenue × outage hours. Failover labor: 3 engineers × failover hours × $200/hr × incidents. Customer churn: 20% of direct revenue loss (conservative estimate). SLA penalty: 10% of revenue lost. ITIC 2024 found 41% of enterprises report hourly downtime costs of $1M–$5M [1]. Rediacc’s <30s automatic failover eliminates extended outage windows.
HOW IT WORKS

One command. Always online.

1

Replicate

Run rdc replicate production --target secondary. Incremental sync — only changed blocks transfer.

2

Monitor

Continuous health checks detect failures instantly. Connects to your monitoring stack (Grafana, Prometheus).

3

Failover

Traffic shifts to healthy infrastructure in under 30 seconds. Automatic DNS updates. Zero manual steps.

Primary (us-east-1) Down
nginx :443
api-server :8080
postgres :5432
redis :6379
Failover
22s
Secondary (eu-west-1) Active
nginx :443
api-server :8080
postgres :5432
redis :6379
UNDER THE HOOD

Why cross-cloud replication is fast and cheap

Rediacc uses btrfs send/receive to compute incremental diffs at the filesystem level. Instead of transferring full images, only changed blocks move between sites. A 380 GB environment with 2.4 GB of daily changes transfers 2.4 GB — not 380 GB. That’s a 98% bandwidth reduction. Replication runs continuously or on schedule.

Traditional approach
Rediacc (btrfs send/receive)
Full VM image transfer: 380 GB per sync cycle, hours to complete
Incremental diff: only changed blocks, 2.4 GB typical daily transfer
Vendor-locked replication (AWS to AWS, Azure to Azure)
Cloud-agnostic: any Linux machine to any Linux machine
Manual DNS failover: 15-60 minutes of engineer time
Automated health check + DNS failover in under 30 seconds
Egress fees: $0.09/GB, ~$34/sync for 380 GB full image
Egress fees: $0.09/GB, ~$0.22/sync for 2.4 GB incremental diff
WHY IT MATTERS

What you get

Always online

One cloud fails, another takes over. No manual intervention. Automatic failover triggers on health check failure. Connects to your monitoring stack.

Multi-cloud by default

AWS, Azure, GCP, Hetzner, or your own hardware. Mix and match. Any Linux machine with btrfs can be a replication target.

No vendor lock-in

Move between clouds whenever you want. Open-format snapshots. No proprietary agents. Standard btrfs — in the Linux kernel since 2013.

THE GAP

No other tool fails over across clouds in seconds

Cloud-native tools replicate within their cloud. Backup tools restore hours later. Rediacc replicates across any provider and fails over in under 30 seconds.

Capability AWS BackupVeeamZertoDruva Rediacc
Cross-cloud replication [4] [5] [6]
Failover under 30 seconds
Incremental-only transfer (98% savings) [7] [8] [9]
Any-to-any provider failover
Self-hosted, no cloud agent [10] [11]
Automatic DNS failover [12]
Full-stack replication (app + DB) [13] [14]
During the AWS us-east-1 outage last March, our 12 production services failed over to our secondary datacenter in 22 seconds. Our customers didn’t notice. Our competitors were down for 6 hours. We got three new enterprise contracts that week from their customers.
982x faster failover

Don’t bet your business on one cloud

Start with the free Community edition. Replicate across locations at no cost. No credit card.

Start Free with Community Free forever for up to 10 workloads
$ rdc repo push --to secondary-dc -m primary
Replicate any containerized workload
Databases, CI/CD, CMS, monitoring, auth, storage — if it runs in a container, Rediacc replicates it across clouds.
Sources & References
  1. ITIC, “2024 Hourly Cost of Downtime Report,” 2024. “The average cost of a single hour of downtime now exceeds $300,000 for over 90% of mid-size and large enterprises.” itic-corp.com
  2. Parametrix, “2024 Cloud Outage Risk Report,” 2024. “Critical cloud service interruption events increased by 18.0% and lasted 18.7% longer in 2024 than in 2023. Human error accounted for 68% of incidents.” www.reinsurancene.ws
  3. Splunk & Oxford Economics, “The Hidden Costs of Downtime,” 2024. “The total cost of downtime for Global 2000 companies is $400B annually, or 9 percent of profits, when digital environments fail unexpectedly.” www.splunk.com
  4. Veeam supports cross-cloud backup and replication between VMware, Hyper-V, AWS, Azure, and Google Cloud. helpcenter.veeam.com
  5. Zerto replicates workloads between VMware, Hyper-V, AWS, Azure, IBM Cloud, and 350+ cloud service providers. www.zerto.com
  6. Druva provides cross-cloud DR by storing backup data across AWS and Azure from a single console. www.druva.com
  7. Veeam uses incremental backup with Changed Block Tracking (CBT) to transfer only modified data blocks. helpcenter.veeam.com
  8. Zerto VRAs continuously replicate only changed data blocks at the hypervisor level in near-synchronous fashion. www.zerto.com
  9. Druva uses incremental-forever backup with global variable-block deduplication achieving up to 90% bandwidth savings. help.druva.com
  10. Veeam Backup & Replication is deployed on-premises on Windows Server with full customer control over infrastructure. helpcenter.veeam.com
  11. Zerto is deployed on-premises with a Zerto Virtual Manager and per-host Virtual Replication Appliances. help.zerto.com
  12. Zerto provides automated Re-IP of recovered VMs during failover with pre/post recovery scripts for DNS updates. help.zerto.com
  13. Veeam Backup & Replication provides continuous replication of full application stacks with orchestrated failover. helpcenter.veeam.com
  14. Zerto Virtual Protection Groups replicate multi-VM application stacks as a single consistent unit with write-order fidelity. help.zerto.com
Product performance claims are based on Rediacc’s btrfs copy-on-write architecture. Calculator estimates use industry-standard cost models; actual costs vary by organization.