Failover as a rehearsed runbook.

Continuous replication to a second sovereign zone with orchestrated failover — drilled quarterly, measured in minutes, evidenced in writing.

RPO/RTO per tierOrchestrated failoverQuarterly drills

Talk to us All Resilience

Capabilities

Recovery, engineered and rehearsed

Tiered objectives

RPO and RTO agreed per workload tier, in business terms.

Spend where minutes matter

Orchestrated failover

One action runs the whole sequence — networks, order, dependencies.

One action, whole sequence

Quarterly drillsReal rehearsals with stakeholders, measured recovery times.Rehearsed with stakeholders

Evidence packsEvery drill produces a report your board and regulator can read.Reports boards can read

Continuous replicationChanges stream to the second zone as they happen.RPO in minutes or less

In-jurisdiction recoveryThe recovery site is a second sovereign zone in the same jurisdiction.Residency survives failover

Network failover includedIP, DNS and firewall changes are part of the runbook, not an afterthought.Users find the new site

Failback plannedReturn to primary is orchestrated with the same rigour as failover.The way back is a plan

Non-disruptive testingIsolated test bubbles rehearse recovery without touching production.Drill without downtime

Managed invocationUnder Managed Recovery we invoke within your mandate and evidence every step.A pager that is not yours

Compare the recovery shapes

Warm, hot, or active-active

Continuous replication and rehearsed runbooks throughout — the difference is how much capacity waits for you on the other side.

ProductionEdgeComing soon

SHAPE 01Most common

Warm Standby

Hours, not days

Replicated data with a scaled-down environment in the second zone, brought up to full size when failover is called.

Best for

Business applicationsSecond-tier systemsFirst DR programmes

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

WarmRPO 15 min · RTO 4 hours · annual drillSign in →Warm PlusRPO 5 min · RTO 2 hours · semi-annual drillsSign in →CustomAny RPO, RTO and drill cadenceSign in →

SHAPE 02

Hot Standby

Minutes, orchestrated

Full-size capacity waiting in the second zone with orchestrated failover, for systems where hours of downtime is not survivable.

Best for

Core bankingERP & financeCustomer platforms

Where it runs

Dubai AZ1RiyadhBahrainMumbaiDubai AZ2Nairobi

Plans

HotRPO near-zero · RTO 30 min · quarterly drillsSign in →Hot PlusRPO near-zero · RTO 15 min · quarterly drillsSign in →CustomAny capacity reservation and objective setSign in →

SHAPE 03

Active-Active

Both zones working

Traffic served from two zones at once, so a zone loss is a capacity event rather than a recovery event.

Best for

Systemically important servicesAlways-on platformsRegulated continuity mandates

Where it runs

Dubai AZ1Dubai AZ2RiyadhLagos

Plans

Active-ActiveBoth zones live · automated traffic steeringSign in →Active-Active PlusBoth zones live · data-tier replication designSign in →CustomAny topology and consistency modelSign in →

Two ways to run it

Replication, or a rehearsed service

Both replicate continuously. The difference is who runs the failover when it matters.

ReplicationYou declareWe keep the replica current and the runbook tested; your team decides when to invoke and runs the sequence.

Continuous replication monitored

Runbooks maintained with you

Drill support on your schedule

Best for:Teams that want the switch

Explore Replication plans

Managed RecoveryWe declare and runUnder an agreed mandate our engineers invoke, execute and evidence the failover, then plan the return.

Failover executed to the objective

Quarterly drills run for you

Board-ready evidence after every event

Best for:Regulated continuity obligations

Explore Managed Recovery plans

Who decides, who runs it

What each group gets from Disaster Recovery

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“Continuity is rehearsed, not promised”

Objectives are agreed per tier and proven by drills, so continuity claims survive both a board and a regulator.

GovernedSovereignPredictable

FAQs

How often do we rehearse?

Annually to quarterly depending on the shape — with stakeholders involved and recovery times measured.

What RPO and RTO can you commit to?

From 15 minutes down to near-zero RPO, and RTO from four hours to fifteen minutes, agreed per workload tier.

Does the recovery site stay in-country?

Yes — a second sovereign zone in the same jurisdiction unless you specifically ask otherwise.

Who invokes failover?

You do by default. Under Managed Recovery we invoke within an agreed mandate and report afterwards.

How does this differ from Backup?

Backup gets data back; DR gets the service running again in a second zone, in a defined time.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

Can we drive it from Terraform and CI?

Yes. Every operation is exposed through the REST API, CLI and a maintained Terraform provider, with scoped API keys per team. If the console can do it, your pipeline can do it.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together