Teams only plan for AZ resilience, not full region loss. When a region goes down (war, natural disaster), migration is chaotic and often too late.
Continuously replicates infrastructure-as-code and critical data to a standby region. Monitors geopolitical and infrastructure risk signals. One-click failover when a region becomes compromised, with pre-validated Terraform plans ready to apply.
subscription
When a region goes down, the pain is existential — total service loss, potential data loss, chaotic manual migration under extreme time pressure. The Reddit thread shows real teams caught with zero cross-region preparedness during the Bahrain incident. Pain is acute but INFREQUENT, which is the key tension — teams know they should prepare but deprioritize until disaster strikes. The 'those who haven't started yet, I don't think there's any possibility for recovery' quote shows catastrophic, irreversible consequences.
TAM is large ($4-6B cloud DR market) but CloudEvac targets a specific niche: AWS-centric teams needing cross-region IaC-native failover. Addressable market is DevOps teams running production in single-region or geopolitically sensitive AWS deployments. Estimate ~50K-100K such teams globally. At $500-2000/month, SAM is $300M-2B. Meaningful but requires expanding beyond AWS to reach full potential.
DR is a known budget line item in enterprises — CISOs and CTOs sign off on DR tooling regularly. BUT: this is insurance-product psychology. Teams chronically underinvest in DR until after an incident. Selling pre-disaster is hard. Post-disaster windows create urgency but are brief. AWS DRS at $20/server/month sets a low price anchor. CloudEvac needs to sell the IaC-native + geopolitical intelligence premium, which is a harder value prop to quantify pre-incident. Compliance mandates (DORA, SOC2) are the strongest forcing function for budget allocation.
This is HARD for a solo dev in 4-8 weeks. Core challenges: (1) continuous IaC replication requires deep Terraform state parsing and dependency resolution, (2) cross-region data sync for RDS, S3, DynamoDB each have their own replication mechanisms, (3) pre-validating Terraform plans across regions requires running speculative plans against live infrastructure, (4) geopolitical risk signal ingestion is a whole data pipeline, (5) one-click failover must handle DNS, certificates, IAM, networking — any missed dependency means total failure. A credible MVP would need to scope down dramatically — perhaps just Terraform plan pre-staging for a single architecture pattern, no geopolitical monitoring. Even scoped-down, 8-12 weeks minimum for a senior infra engineer.
The gap is genuinely clear and validated. NO existing tool combines IaC-native DR + geopolitical risk monitoring + pre-validated Terraform plans. DR tools (DRS, Zerto) ignore IaC. IaC tools (Terraform Cloud, env0, Spacelift) ignore DR. This is a structural market gap, not just a feature gap. The risk is AWS adding IaC awareness to DRS or IBM adding DR features to Terraform Cloud — but both orgs move slowly and this is a niche neither has prioritized.
Natural subscription model — continuous replication, ongoing risk monitoring, and regular plan validation are inherently recurring activities. Customers cannot cancel without losing their safety net. High switching costs once failover plans are configured and validated. Similar to insurance — once you're paying, inertia keeps you paying. Usage-based pricing (per workload, per region pair) scales naturally with customer growth.
- +Genuine whitespace — no one combines IaC-native DR with geopolitical intelligence
- +Pain is real and validated by recent incidents (Bahrain AWS, Ukraine)
- +Strong recurring revenue dynamics with high switching costs
- +Market tailwinds from compliance mandates (DORA, SOC2, SEC) forcing DR investment
- +Cloud-native architectures are exposing fatal gaps in VM-centric legacy DR tools
- !Insurance-product sales psychology — hard to sell pre-disaster, teams chronically underinvest
- !AWS could add IaC-aware DR to DRS or acquire a startup in this space
- !Technical complexity is very high — Terraform state management, multi-service data sync, and cross-region networking are each individually hard problems
- !Geopolitical risk monitoring is a separate discipline entirely — building credible risk intelligence requires domain expertise beyond DevOps
- !Small initial market of teams who both use Terraform AND need cross-region DR AND will pay before experiencing a disaster
Native AWS service for continuous block-level server replication and cross-region failover. Replicates source servers to a staging area in a target region and launches provisioned servers on failover.
Enterprise-grade journal-based continuous data replication and DR platform. Supports VMware, Hyper-V, AWS, Azure with near-zero RPO and automated failover runbooks.
SaaS-native backup and DR platform with AWS snapshot orchestration. Automates EBS, RDS, Redshift snapshot scheduling with cross-region and cross-account copy.
IaC execution platform providing remote state management, plan/apply workflows, policy-as-code
Cloud-native DR automation platform providing application-centric disaster recovery for cloud workloads with some automation and compliance reporting.
Scope way down. MVP = 'Terraform DR Plan Validator' — connects to existing Terraform state, generates and pre-validates a cross-region failover plan (speculative terraform plan against target region), reports gaps (missing AMIs, unsupported services, IAM issues). NO data replication, NO geopolitical monitoring, NO one-click failover in v1. Sell the audit/readiness report first. This is buildable in 6-8 weeks by one senior infra engineer and immediately valuable as a compliance artifact.
Free DR readiness scan (lead gen) -> $299/month for continuous plan validation and gap monitoring -> $999/month for pre-staged failover with data sync orchestration -> $2,500+/month enterprise with geopolitical risk alerts, compliance reporting, and managed failover support
3-5 months. Month 1-2: build MVP readiness scanner. Month 3: launch with free tier + paid validation. Month 4-5: first paying customers from compliance-driven teams. Geopolitical monitoring and one-click failover are 6-12 month features that unlock enterprise pricing.
- “those who haven't started yet or are in progress, I don't think there's any possibility for recovery”
- “We were only planning for AZ resilience before the war”
- “the whole transition to another region took less than a day - implies most teams can't do this”
- “Our RDS database was constantly losing storage”