ReplicateHQ

The listing describes whole-server replication to a secondary AWS region, which is closer to AWS Elastic Disaster Recovery than to a simple snapshot backup. AWS DRS uses continuous block-level replication and recovery orchestration, but ReplicateHQ's exact underlying service should be confirmed. ([AWS Elastic Disaster Recovery](https://docs.aws.amazon.com/drs/latest/userguide/FAQ.html))

That is the stated purpose of the product: replicating the server environment, including the operating system, applications, and data. Ask which source systems, hypervisors, and operating systems are supported before relying on it for a specific workload.

The listing calls the approach agentless, but AWS Elastic Disaster Recovery normally installs a Replication Agent on each protected source server. Clarify whether ReplicateHQ uses a different capture method or is using agentless to describe its management layer. ([AWS DRS implementation guide](https://docs.aws.amazon.com/pdfs/guidance/latest/deploying-cross-region-disaster-recovery-with-aws-elastic-disaster-recovery/guidance-ug.pdf))

AWS documentation describes typical Elastic Disaster Recovery results in the sub-second RPO range and roughly 5 to 20 minutes for RTO, but those figures are not a ReplicateHQ guarantee. Network bandwidth, source workload, target instance size, and application startup order can change the result. ([AWS DRS user guide](https://docs.aws.amazon.com/pdfs/drs/latest/userguide/drs-service-guide.pdf))