AI Sovereignty Analyst Govrin: No Solution for Hyperscalers Regarding the US CLOUD Act
Amit Eyal Govrin, Chief Sovereign AI Analyst at theCUBE Research, announced at SC26 an assessment covering seven hyperscale cloud providers and 40 solutions. He argues that sovereignty is a five-layer control stack rather than a simple checkbox. The core finding is that all providers face an insurmountable legal risk regarding data access under the United States CLOUD Act. Using AWS's Frankfurt region as an example, Govrin illustrates that geographic data location does not equate to actual control.
During the SC26 Supercomputing Conference, Amit Eyal Govrin, lead analyst for sovereign AI at theCUBE Research and chief executive officer of Agentcy Labs, released the results of an assessment covering seven hyperscale cloud providers, 40 product offerings, and five regions. The most surprising discovery for Govrin was not that any specific provider performed poorly, but that every provider faced an intractable legal risk when confronted with the same issue: the United States CLOUD Act.
Govrin’s central argument is that AI sovereignty is not a single checkbox but a stack of control layers that must be examined one by one. He breaks sovereignty down into five pillars: territorial (the physical location of data centers), operational (jurisdiction over daily operations and incident response), technological (the actual location where models and data are processed), legal (applicable judicial jurisdiction), and financial (costs and contractual constraints). The territorial layer is the easiest to satisfy; providers can simply claim compliance by building a data center in the target region. However, Govrin points out that the operational layer is far more complex than it appears.
He cited the Amazon Web Services (AWS) Frankfurt region as an example: as a German customer, your data is indeed stored within the European Union, and AWS operates a sovereign region in Brandenburg. However, if that region experiences an outage, PagerDuty alerts may not be routed to operations personnel located in Germany, but instead sent to Seattle or Hyderabad. Geographic attribution of data and the attribution of actual control are two different things.