Sovereign by default: the group’s operating commitment

Sovereignty is usually sold as a compliance checkbox. We treat it as an architectural constraint, applied from the first design review, because retro-fitting it is not possible in any honest sense.

What the commitment means in practice

• Data residency is a deployment parameter, chosen by the customer, not a contractual promise about someone else’s cloud region.
• The group operates the infrastructure layer itself, so the chain of custody from build artefact to running workload is auditable end to end.
• Cryptographic key material is held separately from the workloads it protects, with documented custody and rotation.
• Every production change is reviewed independently of the team that wrote it.

This is more demanding than the alternative, and slower in the short term. It is also the only version of the promise that survives contact with an auditor.