AWS disaster recovery for UK financial services

When something breaks, your business shouldn't go dark.

Disaster recovery on AWS that's designed, tested and kept current, with evidence you can show a regulator.

Industry data

Most firms have backups. Far fewer have proof they can recover.

What independent research finds about recovery and downtime. Every source is linked.

The problem

Backups are not a recovery plan.

Restoring data is not the same as restoring a working service, on time.

Plans go untested because testing feels risky. Runbooks go stale as the architecture changes around them. And under FCA operational resilience rules, regulators now expect evidence, not assurances.

How it works

Agree the targets. Build to them. Prove them, again and again.

Three stages. Recovery targets are set per system, so you only pay for the resilience each one needs.

  1. Stage 1: Assessment

    • Fee per critical system

    Recovery targets agreed for each critical system, and a tier and design to meet them.

  2. Stage 2: Implementation Sprint

    • Optional
    • Quoted after the assessment

    We build the recovery architecture and run the first failover drill.

  3. Stage 3: Retainer

    • Recommended
    • Monthly

    Recovery that stays proven as your architecture changes.

What happens at each stage

Assessment

  • Business impact workshop with your stakeholders
  • Agree recovery targets (RTO/RPO) for each critical system
  • Recommend a resilience tier and design the architecture

Implementation Sprint

  • Build the recovery architecture
  • Includes a mandatory first failover drill: an untested DR build isn't finished

Retainer

  • Scheduled drills (quarterly by default)
  • Runbooks updated whenever the architecture changes
  • Replication monitoring, post-drill reports and an ongoing evidence trail

Key concept

RTO, RPO and resilience tiers

Tighter targets cost more, which is why they're set per system from a business impact workshop, not as one blanket rule. Most estates use a mix of tiers.

RTO · Recovery Time Objective
How long a system can be down before it seriously hurts the business.
RPO · Recovery Point Objective
How much data, measured in time, you can afford to lose.
  1. Foundational

    Data backed up regularly. No standing infrastructure in a second location: it’s rebuilt on demand.

    Typical recovery
    Hours (up to a day, depending on data volume)
    Data loss
    Back to the last backup
  2. Standard

    The data core (e.g. the database) is continuously replicated. Compute stays off until needed, then scales up.

    Typical recovery
    Tens of minutes to a few hours
    Data loss
    Minutes
  3. Resilient

    A smaller, fully working copy runs continuously in a second location, scaled up on failover.

    Typical recovery
    Minutes
    Data loss
    Seconds to minutes
  4. Continuous

    Full production running in two locations at once, both serving traffic.

    Typical recovery
    Near-instant
    Data loss
    Near-zero

    Always quoted individually

Ranges are typical, not promised. Actual targets are agreed per system in the assessment.

What counts as a critical system?

  • One business application, recovered as a single unit — not one server.
  • Usually several AWS resources: compute, database, storage and networking.
  • The count comes from the signed business impact table.

Pricing

Priced per critical system, by tier.

Choose a resilience tier and the number of critical systems to see the published rates. The more systems, the lower the rate for each.

Resilience tier
systems

1 25

Your fees · Disaster Recovery

Standard · Up to 5 systems

  1. Assessment one-off total

    £3,000

    3 × £1,000

  2. Implementation Sprint one-off · optional

    Quoted after the assessment, based on its findings. Includes the first failover drill.

  3. Retainer monthly total · recommended

    £480/mo

    3 × £160

Estimate from our published rates. Your fixed price is confirmed in writing after the assessment.

Assessment

Disaster Recovery Assessment fee per critical system, by tier and number of systems
Tier Up to 5 systems 6–12 systems 13–20 systems
Foundational £700£550£450
Standard £1,000£800£650
Resilient £1,700£1,400£1,150

Each rate applies only to the systems within its band.

Retainer

Disaster Recovery Retainer per critical system per month, by tier and number of systems
Tier Up to 5 systems 6–12 systems 13–20 systems
Foundational £110£95£80
Standard £160£135£115
Resilient £260£220£190

Each rate applies only to the systems within its band.

Continuous (multi-site active/active)
Contact us, at any system count
More than 20 systems
Contact us
What a critical system is
One business application recovered as a single unit — not one server
Assessment timeline
2 weeks (simple) · 3–4 weeks (typical) · 5–6+ weeks (complex) — mostly set by stakeholder availability for the workshop
Retainer terms
Rolling monthly, 30 days' notice

How we test safely

Every drill runs under a safety protocol.

Real failovers carry real risk. This is how we keep a test from becoming an incident.

  • Scope agreed in advance, so a test can’t spread beyond its target
  • Stakeholders notified
  • Critical business periods avoided
  • Rollback plan agreed before the drill starts
  • Results logged to a compliance evidence trail

What's included

What you get at each stage.

Stage 01

What the assessment includes

  • Business impact workshop
  • RTO/RPO per critical system
  • Tier recommendation and architecture design
  • Written assessment report

Stage 02 · Optional

What the Implementation Sprint includes

  • Recovery architecture built as code
  • Runbooks your team can follow under pressure
  • First failover drill, with a written report

Stage 03 · Recommended

What the Retainer includes

  • Scheduled drills with post-drill reports
  • Runbook maintenance
  • Replication health monitoring
  • Fixes for anything a drill exposes
  • Ongoing compliance evidence trail

Why trust the work

Tested for real, documented for the regulator.

  1. Real failovers

    Drills are real failovers, run under a safety protocol, not paper exercises.

  2. Evidence you can hand over

    Produced in a form you can give to an auditor or regulator.

  3. No shortcuts

    No shortcuts on build or testing, the parts where speed creates risk.

  4. Senior-led

    A career built in banking, where recovery is regulated.

Related insights

All Disaster Recovery insights

FAQs

Questions we get asked

What are RTO and RPO?

Which tier do we need?

Isn't having backups enough?

Do you test with live workloads?

What scenarios do drills cover?

Can you design multi-region DR?

Will the documentation satisfy our auditors?

Why is the sprint quoted after the assessment?

Why can't the sprint be rushed?

We reply within one business day

Find out whether you'd recover on target.

A free 30-minute call is enough to see which systems need what.

What do you need help with?

Step 1 of 4

Book a free 30-minute call

Free · 30 minutes

Step 1 of 4

What do you need help with?