What your console shows

  • Backups configured
  • Read replicas active
  • All checks passing

What Stronghold finds

  • Reality Gap: 56 points
  • Claimed 56% protected
  • Proven 0% recoverable

What you actually need

  • Proof-of-Recovery: 0%
  • 3 services not recoverable
  • DR debt growing for 45 days

What Stronghold does

What do we have?

Service-level mapping from CloudFormation, tags, and topology — not just resource inventory.

What breaks if this fails?

Dependency graph with blast radius analysis and SPOF detection.

Can we still recover?

Scenario coverage analysis for AZ failure, region failure, SPOF failure, data corruption.

Is the full recovery path proven?

Full-chain coverage traces every step of the recovery order and shows which links are proven, observed, or broken.

What's the proof?

Evidence maturity tracking. "Config observed" ≠ "recovery tested."

Is it getting better?

Posture history, DR debt tracking, and trend analysis across scans.

See why

TypeScript strict 736 tests 82.6% core coverage 39 DR rules 16 AWS services AGPL-3.0 Zero telemetry