Sovereignty is a genuine requirement for a segment of Malaysian organisations — government, banking, and any estate that has to prove data residency. But paying a premium on every workload to satisfy a requirement that only applies to some of them is one of the most common cloud overspends we see.
A workload-by-workload view
- Regulated and resident-mandated data → sovereign or private cloud
- Elastic, bursty workloads (AI inference, testing, dev) → public cloud where residency rules allow
- Everything in between → hybrid, with the boundary drawn by policy, not convenience
The mistake is a single big answer — all public, or all private. The defensible one is a per-workload decision, documented, because a regulator will ask you where specific data lives and why.