Free download · A4 PDF · CISO / CTO grade
Multi-Cloud Always
AWS US-EAST-1 went dark for 15 hours on October 20, 2025. Snapchat, Robinhood, Uber, Delta. Could you have switched clouds in time?
One email. Confirmation by mail. Unsubscribe with one click.
What's inside
The brief covers the architecture, the failure modes it blocks, the regulatory map, and the operator-level evidence an auditor will ask for. Roughly 10 to 14 dense pages.
- The threat model in concrete operator terms
- Architectural mechanism, with adversary-model reasoning
- Failure modes blocked, with named precedents
- Compliance map: specific rules, fines, reporting windows
- ROI math grounded in published numbers
- Vendor comparison on technical approach (not ARR)
- Onboarding shape and known scope limits
- Audit-ready evidence the architecture produces
Related solution pages
The same architecture, applied to specific buyer questions:
When AWS goes down, you don’t
Your infrastructure runs on multiple clouds. When one fails, the others take over. Automatically.
Read moreTest your failover before you need it
Run disaster simulations safely. Know your recovery actually works. No surprises when it matters most.
Read moreYour infrastructure. Your choice. Always.
Deploy anywhere. Migrate anytime. No lock-in contracts. No proprietary formats. Your data stays yours.
Read moreQuestions readers asked
Who is this brief written for?
A CISO, CTO, or senior infrastructure engineer evaluating the architecture. It assumes familiarity with backup workflows, filesystem fundamentals, and the regulatory landscape your stack already touches.
Is there a non-technical version?
Yes. After you submit your email, the same page links to a five-minute executive PDF you can forward to a CFO, IT director, or board member.
What happens to my email?
One confirmation email. You're added to our newsletter (one short post per month, all-product). Unsubscribe with one click. Your email lives in the EU by default per Rediacc's data-residency policy.
Why btrfs?
The brief explains in detail. The short version: btrfs makes immutability, copy-on-write snapshots, and incremental send/receive properties of the storage layer rather than of an application running on top of it. That changes what an attacker holding root credentials can defeat.
Does this apply to managed services like AWS RDS?
Not directly. The architecture covers self-managed compute with containerized databases on btrfs-backed volumes. If your recovery-critical estate sits in RDS or Aurora, the brief flags this explicitly and points to where the model does and doesn't apply.
About this brief
Rediacc is a Tallinn-based infrastructure protection company building btrfs-native backup and disaster recovery on commodity Linux. This brief was written by the engineering team, edited against an anti-AI-slop style guide, and reviewed for technical accuracy before publication.
Have a question we should add to this page? Tell us at hello@rediacc.com.
Download short brief (PDF)