Interactive Companion

BCDR Assessment

Select critical services, model composite availability, assess operational readiness, and validate commitment feasibility.

Provider scope

Source baseline: Microsoft Azure (Microsoft Online Services SLA (WW), May 2026 (verified 2026-05-15))

Before setting targets, read how Azure defines availability, how it is measured, what is excluded, and how claims are filed.

Service picker includes every SLA-tracked service. Composite availability is calculated from the modeled options you select.

Important: provider SLA is not your product SLA. Set a lower customer commitment, define an internal SLO above that target, and document how planned maintenance, excluded events, and outage criteria are handled.

The first interview is provider-neutral. It captures the shared reliability decisions that matter across AWS, GCP, and Azure before cloud-specific implementation detail appears.

Verified Multi-Cloud SLA Sources

AZURE: Microsoft Azure (Microsoft Online Services SLA (WW), May 2026 (verified 2026-05-15))
AWS: Amazon Web Services (AWS Service Level Agreements index (verified 2026-05-15))
GCP: Google Cloud (Google Cloud Service Level Agreements index (verified 2026-05-15))
OCI: Oracle Cloud Infrastructure (OCI SLA page with PaaS and IaaS Pillar reference (verified 2026-05-15))

Autosave is browser-local only. Export or print for durable records.

0. Foundational Interview

Capture the operational and business context that determines BCDR risk appetite.

Business criticality Reputation impact if unavailable Estimated churn risk (%) Maximum tolerated downtime (minutes) Recovery time objective (RTO minutes) Recovery point objective (RPO minutes) Cross-cloud connectivity resilience Recovery runbook quality Primary recovery posture Graceful degradation allowed? Failover and failback plan Restore and drill cadence Monitoring tied to critical flows Recovery constraints

Team Readiness

Assess the operational maturity and team capability for recovery execution.

Primary on-call responder Last recovery procedure execution Team can execute recovery within RTO? Backup/restore expertise available?

Readiness score

High gaps

Medium gaps

RTO vs MTD

Reputation exposure

Reliability posture

Team readiness

0a. Critical Flow Mapping

Map user journeys to services. Ensures services are selected for a reason.

1. Critical Path Services

Add only services in the transaction path. Each service field is searchable inline.

Catalog coverage: 689 services total (Azure 128, AWS 321, GCP 165, OCI 75).

2. Composite Availability and Commitment

Dependency availability estimate

Monthly downtime budget

Yearly downtime budget

Customer SLA target (%) Internal SLO safety margin above SLA (basis points)

Internal SLO target

Max SLA from dependency estimate

Model check (dependencies only)

This check models dependency availability only. Final SLA and SLO decisions must also include code quality, release risk, maintenance policy, exclusions, and outage definition.

2a. Business Impact and DR Decision

Translate reliability targets into financial exposure and force an explicit architecture decision when targets and posture conflict.

Estimated revenue at risk per hour (USD) Estimated write rate (records/minute)

Regulatory exposure Mismatch decision (required when posture and RTO conflict)

Max downtime loss (MTD)

Annual expected loss

Data loss exposure (RPO)

Customer trust risk

DR compatibility

Maturity path

4. Fastest Ways to Improve Availability

Resource-Specific APRL Recommendations

Recommendations are filtered from APRL using your currently selected resources.

3. WAF Reliability Crosswalk Coverage

Checks are provider-specific for single-cloud scope. Multi-cloud scope evaluates each provider separately.

Assessment Findings Register

Prioritized findings and actions based on interview inputs, commitment feasibility, and selected resources.

Cost-Benefit Simulator

Compare recovery posture costs, complexity, and RTO tradeoffs.

Scenario Simulator

Dependency failure scenario

Regional outage scenario

Data corruption scenario

5. Executive Evidence Pack

Executive narrative

6. Export Before You Leave

Downloaded locally from browser

This prototype uses local state only; no server-side data persistence is enabled.

No export yet in this browser session.