Recovery target and evidence
For the base review, agree the service boundary and selected dependencies, then compare the business recovery objectives with existing records.
Cloud platforms · 01 · The problem and the decision
Resilience and disaster-recovery reviewWhen did you last fail over on purpose?
Recovery exists as a document, but the team cannot say which parts are supported by evidence. Review one platform's recovery design and decide which gaps need attention. A bounded rehearsal can be agreed as an optional extension to the review.
For platform leaders responding to an incident, audit finding or business-continuity question.
Elapsed review window agreed after scope; rehearsal scheduled separately if selectedOne agreed platform; review of recovery design and existing evidenceA named architect accountable
02 · What we check
Agree the scope. Inspect the evidence.
The base review compares the business recovery target, documented design and existing evidence. It identifies what remains untested. An optional rehearsal adds observed behaviour only for the separately agreed test boundary.
Design and runbooks
Review the agreed backup or replication paths, identity and network dependencies, recovery instructions and ownership. Record gaps and questions requiring a test.
Optional bounded rehearsal
If selected in the proposal, plan and run one authorised rehearsal within its agreed boundary. Capture behaviour and timing, and complete the agreed recovery or rollback. The review-only scope does not execute a failover.
What we need from you
- For the review: one agreed platform, an inventory of the selected dependencies, a service owner and recovery objectives set by the business.
- For the review: read access to the agreed configuration, runbooks and existing recovery evidence, plus access to the relevant owners.
- Only for the optional rehearsal: approved environment and test data, explicit execution permissions, a test window, an authorised test plan and a workable rollback or recovery path.
Scope and boundaries
- The review-only scope excludes failover execution and production changes. No disruptive test starts without separate client authorisation.
- A DR build, remediation, detailed implementation-ticket engineering, additional rehearsals and recovery guarantees are outside this scope.
03 · What you get
A decision you can act on.
- A review of the agreed recovery design and selected dependencies, based on existing evidence.
- A gap list comparing the recovery objectives with the evidence available and identifying untested assumptions.
- Prioritised next actions with suggested owners, including a recommendation on whether a rehearsal would resolve an important uncertainty.
- Only when the optional rehearsal is agreed: an authorised test plan and a record of its results, limitations and unsuccessful steps.
04 · Relevant work and a sample
See the thinking behind the review.
Separate documented design from demonstrated behaviour
The sample shows a finding from a review of existing evidence and how an optional rehearsal could test it. It is not a client recovery result or a promise that the review includes a test or will establish a recovery time.
05 · Duration and price
A defined engagement. An agreed scope.
From €6,500Starting price, excluding VAT
Review only from €6,500, excluding VAT. We quote a fixed fee after agreeing the platform and dependency inventory, access and review depth. The elapsed review window is confirmed in the proposal. Review plus one bounded rehearsal has a provisional total starting price of €9,500, excluding VAT; this is the total for both parts, not an add-on. That option requires an agreed test boundary, permissions, window and recovery plan. Remediation and detailed implementation-ticket engineering are separate.
We agree the included scope, deliverables and fixed fee in the proposal before work starts.
- Duration
- Elapsed review window agreed after scope; rehearsal scheduled separately if selected
- Base scope
- One agreed platform; review of recovery design and existing evidence
- Your data
- The base review uses read access to the agreed evidence. Only an optional rehearsal requires execution permissions, an authorised test window and a documented rollback or recovery path. Data handling is agreed before evidence is collected.
Our own AI-assisted tooling collects evidence and drafts findings; a named architect checks and signs them. How we work and handle data →
06 · Request a working session
Start with the question you need to resolve.
In 45 minutes, discuss the recovery target, existing evidence and the design questions to review. If a rehearsal would be useful, identify the separate scope and authorisation it would need.
This requests a 45-minute conversation. We confirm a suitable time with you.
Are the immediate questions about Kubernetes production readiness? Explore the Kubernetes review.