- Review platforms (G2)
- Overall sentiment on G2 is very positive:
- Rating shown: very high rating with a small review footprint (as of the page crawl).
- Distribution shown: majority 5-star with some 4-star, and no 1–3-star reviews visible in the captured section.
- Positive quotes (G2)
- Verified User (Computer Software, mid-market) highlights setup via CloudFormation templates and ease of selecting resources, plus recovery testing and “failback is properly engineered.”
- Robert M. (mid-market) states: “Setup is easy, and above all, the service is reliable,” and claims other solutions had “major shortcomings and were painful to set up.”
- Negative / critical quotes (G2)
- The most concrete criticism captured: “Certain niche AWS services may not be supported… AWS SES is a good example. You can manually setup this complicated service in your alt account and it'll be there when you need it.”
- Many reviews shown in the captured section report “no dislikes,” which can be genuine but also reduces the ability to understand failure modes from reviews alone.
- Review quality considerations
- At least one review in the captured section indicates an incentivized source, which can introduce positivity bias. G2 does run verification processes, but buyers should still consider potential selection bias.
- Community/social (Reddit)
- In an r/aws thread about EC2 DR, one commenter says: “We use a service from Arpio.io that replicates resources from one account / region to another.” This suggests real-world usage, but it’s a single anecdote without details on scale/cost.
- In another r/aws thread, a commenter explicitly states: “I work for Arpio and we automate cross-region failover and fallback…” This is valuable context but is not an independent user review.
- Hacker News (news.ycombinator.com)
- Mixed technical scrutiny during the 2021 “Launch HN” thread:
- Questions about S3 replication and Lambda support; founder response indicates those were not yet supported at that time and were on the roadmap.
- A commenter questions whether “doubling down” on AWS is the right approach to AWS outages; founder argues redundancy within a cloud is a common reliability pattern.
- Founder acknowledges consistency limitations when snapshotting clustered systems (snapshots “won't be fully consistent across nodes”), and suggests applications typically handle such inconsistency similarly to power-loss recovery.
- Why customers chose Arpio over alternatives (themes across reviews and case studies)
- Reduced operational burden versus scripts/runbooks/manual DR.
- Faster time-to-implement and faster/more frequent testing.
- Broader “environment recovery” vs data-only backup/restore.
- Why some customers left for competitors (churn reasons)
- No clear churn narratives were found in the accessible sources reviewed (a common limitation when vendor case studies dominate and review counts are low).
- Specific outcomes customers achieved (with metrics when available)
- Workwell case study (vendor-published) claims:
- DR implemented/verified for a small number of workloads by a single engineer in a short timeframe.
- Outage recovery reduced from multiple hours to minutes.
- Manual processes were reported to be substantially reduced.
- DR testing cadence increased from infrequent to more frequent (monthly).
- These metrics are strong but are vendor-published and methodology is not independently validated.
- Workwell Achieves AWS Resilience in a fraction of the time (vendor-published)
- Claimed challenges
- Complex DR made of scripts and multiple tools; recovery was manual and described as “error-prone,” taking multiple hours.
- Claimed solution and implementation
- POC reportedly achieved cross-region and cross-account DR for an initial workload within a short initial period.
- Quote from Workwell SVP Engineering claims a fully functional DR environment in minutes.
- One engineer onboarded remaining workloads in around a week, mostly spent testing.
- Claimed results (metrics)
- A small set of workloads protected within a short multi-day period by one engineer.
- Recovery time reduced from several hours to minutes.
- A large reduction in manual processes.
- Testing cadence moved from infrequent (annual) to regular (monthly).
- Critical evaluation
- All metrics and quotes are vendor-published; there is no independent validation, and there is limited detail on measurement methodology (definition of “recovery time,” scope of workloads, data consistency constraints, and recovery completeness).
- NurseGrid case study (vendor-published)
- Positioning
- Emphasizes Arpio’s discovery of security groups, IAM roles, and network configuration to enable full recovery.
- Critical evaluation
- Strong claims but largely qualitative in the accessible excerpt; buyers should request technical architecture diagrams, validation evidence, and references.
- Additional case studies listed (not all opened in this run)
- Choice Hotels, Scotts Miracle-Gro, Relay Network, SAP HANA workloads (GILM) are listed in Arpio’s case study archive. These may provide additional industry-specific metrics, but remain vendor-authored.