Sovereignty by procurement: how the kill switch became a cloud contract line item

When a major European industrial buyer writes a cloud contract today, the kill-switch question is now on page one of the RFP.

Catherine Jestin's remarks in the Reuters wire, naming "protection against the kill switch and against the application of extraterritorial laws" as a procurement criterion after Airbus assessed more than 150 technical and legal requirements, expose a repeatable mechanism: industrial sovereignty has migrated from policy paper to vendor-selection checklist. The roughly seventy critical applications Airbus plans to move to Scaleway by the end of 2028 are not a vendor announcement; they are the first measurable test of the European Commission's June 2026 Cloud and AI Development Act, which proposed domestic capacity for exactly this kind of workload. A broader programme potentially covers up to nine hundred applications over the next five to six years.

A French defense ministry accord-cadre with Mistral AI layers a sovereign model on a sovereign cloud. Airbus is now asking the same questions about its Mistral-on-Scaleway deployment — though Airbus has not confirmed it applied the same kill-switch and extraterritorial-law RFP filter to that stack. Other European buyers with sensitive industrial data could, in theory, apply the same filter — a capability Airbus is now demonstrating. US hyperscalers are now the providers to be justified, not defaulted to.

The dynamic, as the Airbus case illustrates, is straightforward: who controls the off-switch now controls the negotiation.