
Customer scenarioIllustrative composite, not a named customer
Provincial shared-services agency
Multi-cloud on paper became multi-cloud in practice.
The situation
A provincial shared-services agency serves 12 ministries and holds 18 PB across three hyperscalers. Each workload was still tied to a single provider.
What forced the question
- The Auditor General flagged cloud concentration risk
- Single-cloud lock-in per workload, despite three providers
- Renewals were negotiated without a credible alternative
What was deployed
6 of 9 fragments · any 6 rebuild the data
Hyperscaler A · 2Hyperscaler B · 2Hyperscaler C · 2Sovereign DCs · 3
Site you control or sovereignCloud or outside provider
- Delivered as
- A shared service, weighted per ministry
- Timeline
- 14 months, 47 workloads
“For the first time, our cloud negotiations are conducted from actual optionality, not performative optionality.”
What changed
$8–14Maggregate annual savingall three providers improved terms
Acknowledgedby the Auditor Generalconcentration mitigation
$0data-movement costtwo workloads moved between providers
Questions a buyer asks
How does a workload move?By re-placing a minority of fragments. Two workloads moved between providers at no data-movement cost.
Can any one provider rebuild the data?No. Each holds two of nine fragments and six are needed.
What if a provider is lost?Any one provider can be offline and seven fragments remain.
How do ministries differ?The service is shared, with fragment weighting set per ministry.