Pre-Flight Readiness Checks

Prove you're ready
before the moment.

Before peak season, a launch, an audit, or a failover — Pre-Flight runs evidence-backed readiness checks against your declared posture, on a cadence. Every expected resource reporting, evidence fresh, dependencies viable, and every unknown surfaced ahead of the moment.

Pre-Flight·Q4 peak readiness · weekly run 12
Not yet proven
Coverage · expected resources reporting
94/100
94 of 100 expected reporting · 6 UnknownOldest evidence: 38m
Failover path · us-east-1 → us-west-2
12 dependencies viable
at target
Certificate expiry · 60-day horizon
84 endpoints evaluated
at target
Restore proof · finance tier
last attempted 6d ago
off target
Break-glass sign-in · 4 accounts
2 not reporting
Unknown
At target
41
of 48 checks
Off target
5
2 blocking
Unknown
2
never a pass

Ready means proven. Not assumed.

Zero
writes to your providers

Verification starts with scoped observation. Panaptico reads live state from each provider and verifies it against your declared posture. Providers stay authoritative — Panaptico never holds write access.

94 / 100
Coverage is a denominator

Every check declares its expected population up front. If 94 of 100 expected resources report, readiness is 94 out of 100 with six named gaps — not 100% of whatever happened to answer.

Unknown
is a first-class result

A resource that stops reporting doesn't vanish from the result — it turns Unknown, and Unknown blocks. Silence never becomes a pass, least of all the week before the moment.

Readiness run · Q4 peak
weekly cadence
Verification contract
scopefinance-prod · 100 resources
target_conditionwarm-standby ready
coverage_floor100% reporting
freshness_windowevidence ≤ 24h
definition_versionreadiness.q4-peak · v3
Observing expected population62 / 100
denominator declared up frontread-only

Declare what ready means

A readiness run starts as a verification contract — scope, target condition, coverage floor, freshness window, and definition version, pinned before anything is evaluated. Panaptico then observes live provider state against it. Observation only; never a write.

Conformity · field by field3 fields off target
~payments-standby replicaRecovery path
Resource id
rds · payments-standby-replica · us-west-2
Declared target
multi_az: true
Current state
multi_az: false
Evaluated 97 of 100 expected · 3 UnknownEvidence 12m old

Current state vs declared target, field by field

Readiness isn't a vibe — it's a comparison. Every field on every expected resource is evaluated against its declared target, with the evidence and its age behind each result. Resources that never report show up as Unknown, not as passes.

HIGHoff_target · recovery path
blocking
Standby replica lags declared target by 13 minutes

payments-standby-replica reports replica_lag of 14m against a declared target of ≤ 60s. Evidence from provider API read, 41s old.

Blast radius
2 services · 14 identities · 1 recovery path
evidence · provider read · 41s

Every finding names its blast radius

Findings carry severity, evidence, and a named blast radius — the affected resources, identities, and paths downstream of the divergence. You walk into the review knowing exactly what's exposed, with every unknown and stale dependency surfaced ahead of the moment.

Readiness resultProven · fresh
What proven means here
coverage_complete
evidence_fresh
dependencies_viable
paths_effective
restore_proven
signin_probe_passed
unknowns_zero
readiness_result
Ready · run 12 of 16 · definition v3 · evidence window 24h
goes stale with its evidence

Ready is a result that can go stale

A readiness result is pinned to the evidence that produced it. When evidence ages past its freshness window or a dependency shifts, the result goes stale — visibly, with history. Ready means proven on a cadence, not asserted once and assumed forever.

Coverage

Verified against your real estate.

Pre-Flight runs on the providers Panaptico already observes. Live state is read across them and verified against your declared posture — providers stay authoritative, and every result carries the evidence behind it.

AWSobserved
Azureobserved
Terraformobserved
GCPplanned
Oktaplanned
Cloudflareplanned
Microsoft Graphobserved
Datadogplanned
Snowflakeplanned
Databricksplanned

Walk into the moment proven.

Peak season, the audit, the launch, the failover — declare what ready means, run the checks on a cadence, and surface every unknown before it matters.