A few days ago I sat in a workshop where someone raised the question of cloud kill switches. My intuitive reaction to this debate is always that this scenario shouldn’t drive what we do in terms of sovereignty. But the question stuck with me on the way home. Not because the idea is new, but because I realized I had never actually thought it through myself. What would it concretely look like? What would happen in the first hours? And what would the world look like a month later?
What follows is my attempt to think out loud. I don't claim to have the definitive answer, and I am sure I have gotten things wrong or missed things entirely. But I'd rather put an imperfect map on the table than leave the question hanging. Pushback and additions very welcome.
Let´s start with definitions
What is a kill switch?
In tech, a kill switch is a mechanism that lets somebody disable a service, software or device against the will of the legal owner or user. It can be as narrow as revoking a single API key or as sweeping as taking down an entire infrastructure region.
Where could be a kill switch?
Everywhere there is software. That is now everything with a chip: phones, laptops, cars, tractors, medical devices, payment terminals, industrial control systems, building management, smart appliances. Your fridge.
Most people only think of cloud services, but the same logic applies to any software. It can phone home to verify a license (and stop if the answer is no), check a hardcoded expiry date, count down a usage limit, or simply require a periodic "still alive" signal and go dark when it stops arriving. No human needs to press a button. The condition triggers itself. And any device that doesn't have this today can receive it through a routine update tomorrow.
Why does everyone talk about it?
The world has become more hostile. Major powers are competing harder, trust between blocs is eroding, and open conflict is no longer unthinkable. In that environment, every shared dependency becomes a potential weapon. And as the tech stack is one of the deepest shared dependencies that exists, it is obvious we think about a scenario where such dependencies are being used to exercise power.
What analogy could help us think?
The mental model I follow during this article is to learn from what happened in Ukraine and Iran. A powerful aggressor is exercising force on a smaller entity, but not in an evolutionary careful manner but in a bombastic, overwhelming fashion expecting quick submission. Two recent examples
- Russia invaded Ukraine expecting days. Instead the aggression unleashed creativity and determination that nobody had modeled. Ukraine shot at fuel trucks to stop advancing columns, blew dams to flood enemy positions, improvised battlefield software in Kyiv apartments. Europe, slowly and expensively, got its act together and financed a wave of defense innovation that has, after enormous human and financial cost, shifted the momentum building on European industry capabilities.
- The current Iran war follows the same pattern. The U.S. has overwhelming conventional superiority. But Iran's cheap drone swarms have no good answer in the classical weapons inventory. A $5,000 drone forces a $2 million interceptor missile to be fired. Do that at scale and the math collapses. And for all the military options on the table, the aggressor is more constrained by what the conflict does to oil prices and domestic voters than by anything Iran can do militarily.
Secondary and tertiary effects, that is my learning, are the actual battlefield.
The Scenario: Google vs. Spain
The scenario we talked about in this workshop was that Spain, in a serious political rupture with Washington, expels U.S. military bases from its territory. Trump, treating the tech stack as a foreign policy instrument, pressures Google to terminate its operations in Spain. Google complies.
Internet research says that Google has the following operations in Spain:
- Cloud region in Madrid (europe-southwest1), one of Google's main Southern European hubs
- Grace Hopper subsea cable landing in Bilbao, connecting Spain directly to the U.S. and bypassing congested Northern European routes
- Headquarters in Madrid with around 300 employees
- Commercial office in Barcelona focused on digital transformation
- Cybersecurity center of excellence in Malaga with around 40 engineers
Beside cloud, also these services must be cancelled then for Spain:
- Google Search, the default entry point to the internet for most Spanish users
- Gmail and Google Workspace, used across Spanish businesses, schools, and government agencies
- Google Cloud, hosting startups, banks, retailers, hospitals, and public sector workloads
- Android, running on the majority of Spanish smartphones
- Google Play Store, the distribution channel for essentially all apps on those phones
- Google Maps, embedded in logistics, delivery, navigation, and emergency services
- YouTube, a primary media and news consumption channel
- Google Ads, the revenue backbone for most Spanish independent media and publishers
- Google Chrome, the dominant browser
- Google Translate, heavily used across a multilingual country with regional languages
- Chromecast and Google TV in living rooms
- Google Pay in payment terminals
Google`s Challenge: Figuring out “What is Spain, actually?”
I am not an enterprise architect at Google. But it is very likely that Google tech has not prepared for a single "Spain off" switch. Each service, Search, Gmail, Cloud, Android, Ads, is a separate engineering stack built by different teams who most likely will not have had the requirement to implement a country kill layer. Spanish users and companies will lack a clean identifier: IP addresses are bypassable, account data is inconsistent, and device registration is unreliable. Also: Past experience with Huawei is, that Android are not instantly being disabled; degradation happens over days as services time out and updates stop arriving.
A coordinated shutdown would require weeks of engineering preparation that has never been designed for and that most likely would leak as Google employs quite a few Europeans also in US engineering.
Hence, the US desire to act quickly will result in a rather dirty yet fast shutdown. The result would not be a clean surgical isolation of Spain. It would be a rushed, incomplete, partially effective shutdown that breaks things unpredictably, leaves gaps, and creates failures nobody anticipated.
Primary Effects of a Google Shutdown
Dirty Degradation
The shutdown would be a degradation, not a blackout. Google's systems are engineered for resilience and uptime, not for the abruptness of a forced shutdown. Every redundancy mechanism, every failover path, every retry logic that was built to keep services running becomes an obstacle to turning them off cleanly.
On the network side, major Spanish IP ranges go dark but smaller ISPs, mobile carriers, and corporate ranges are missed, leaving traffic reaching Google through unblocked paths. Account suspension hits high-confidence Spanish users but leaves millions of edge cases intact, expats, tourists, and dual-registered accounts, making the identity cut jagged rather than clean.
The loss of the cloud region leaves customer data in an ambiguous state, neither accessible nor formally handed over. Critically, the Madrid region hosts not only Spanish companies but multinationals with Southern European operations, including U.S. companies' own subsidiaries. American firms would find their European workloads disrupted by their own government's political decision.
On Android, Play Store access breaks for most Spanish IPs but not all, and existing apps keep running while updates and security patches stop arriving silently with no error message. Advertising payouts freeze mid-cycle, ads stop serving to most Spanish IPs but bleed through on unrecognized ranges, and publishers lose revenue immediately with no notice. DNS breaks Google.es for most users but Google.com remains reachable through unblocked paths.
The damage is real and immediate, but the shutdown itself is full of holes.
Creative adverse effects
Within hours, technical users and businesses discover that Google.com remains reachable and VPNs restore full access. Corporate IT departments route their traffic through VPN endpoints outside Spain almost immediately. The most technically capable users effectively never lose service.
Within days, the Android degradation becomes visible. Developers and businesses begin sideloading apps directly from APK files, bypassing the Play Store entirely. Alternative app stores gain traction overnight. Google Mobile Services workarounds circulate through developer communities.
The cloud region is the hardest hit. Businesses with workloads hard-terminated in Madrid have no immediate path back. Those with disaster recovery plans activate failover to other regions. Those without face days or weeks of downtime while they manually reconstruct their infrastructure elsewhere.
Spanish publishers hit by the advertising freeze pivot to alternative ad networks, primarily Meta and local Spanish platforms, within days. The revenue loss is permanent for that period but the dependency on Google Ads begins structurally unwinding.
On the DNS side, Spanish ISPs and technical communities rapidly publish alternative resolver configurations pointing to Google.com or competing search engines. Bing and local alternatives see sudden traffic spikes.
The pattern across all of it is the same. The shutdown creates immediate pain for ordinary users and unprepared businesses, but the technical community routes around it quickly, exposing the holes in the degraded shutdown and accelerating Spain's structural migration away from Google dependency.
Secondary Effects will come fast
US clouds regions will crush
European companies move workloads to U.S. regions immediately. The reasoning is simple: a U.S. region under U.S. jurisdiction is the most stable place to be when the instability is geopolitical. U.S. data centers are not going anywhere, and migrating between regions of the same hyperscaler is straightforward. That migration wave is massive, and U.S. regions absorb an enormous spike in demand until the capacity cracks under it. U.S. companies will struggle to serve own demands and might be forced to look for cloud space in Latin America, Asia or even the now increasingly empty EU hyperscale clouds.
In parallel, companies start closing the ambiguities that made the Spain shutdown so jagged. They watched Google struggle to identify who was Spanish and who was not, and draw the obvious lesson: make yourself appear unambiguously American, or at minimum so structurally opaque that no algorithm can cleanly flag you as European.
Billing details get updated to U.S. addresses, typically through U.S. subsidiaries that already exist or get incorporated quickly in Delaware for exactly this purpose. Credit cards get replaced with U.S.-issued corporate cards tied to those subsidiaries. Cloud subscriptions get transferred to U.S. legal entities so the contract sits under U.S. jurisdiction rather than European. Domain registrations, DNS configurations, and account ownership all get migrated to U.S. entities.
The goal is to look, from Google's or AWS's perspective, like a U.S. customer. Not because anyone is hiding. But because a U.S. customer sitting in a U.S. region with a U.S. billing address is the entity least likely to get caught in the next geopolitical crossfire, wherever it originates. This may not be entirely consistent with every regulatory guideline that exists, particularly around data residency and GDPR. But the beauty of such crisis is, that you don’t have to care much anymore.
The Spain shutdown inadvertently publishes the playbook for how to be unswitchable for the time being. European companies read it and execute.
The Cascade
As the global tech stack is interconnected, unexpected side effects will cascade down across dependencies that nobody has fully mapped. Maybe Stripe relies on an API that relies on GCP Madrid. Then everything that relies on Stripe is off, too. Then “Google vs. Spain” propagates through dependency chains, surfacing failures in places that have no logical connection to the original political dispute.
Broader Economic Effect
The first reaction is to game the gaps in the shutdown. But that buys days, not a solution. Everyone starts looking for alternatives simultaneously. Europe has cloud providers. There is open source. But European clouds do not have the physical capacity to absorb a continent-scale migration. The data centers are not there. The hardware is not there. Much of the compute that exists in Europe runs on infrastructure that is somewhat under U.S. control anyway. And Google might be just the first domino. VMware could be next. Cisco. Oracle. The entire U.S.-dominated stack is now in question at once, and the demand shift hits every layer simultaneously.
That means tech resource prices go up across the board:
- European cloud providers finally get the demand surge they always wanted, and price accordingly
- GPU and server hardware prices explode globally as every actor tries to procure at once into an already strained supply chain
- Every engineer who vaguely knows how software and hardware works has just won the lottery
- Everything else touching information technology, construction, power, cooling, networking, follows the same direction
What goes down are stock markets globally:
- Big tech shares will drop by 30-70%
- Google takes the sharpest hit as the company that pulled the switch
- Every U.S. enterprise with European revenue sees its multiple compress as investors permanently price in geopolitical dependency risk
- Every EU company with relevant revenues in the US goes down with them
Political counter measures? Not likely
The political reaction begins with noise: open source manifestos, emergency parliamentary sessions, competing national responses, and the inevitable chorus of those who warned about dependency for years. But underneath the cacophony, a harder and more rational response takes shape.
Following the playbook of gas storage confiscation after the Ukraine crisis, European authorities place U.S. tech subsidiaries under emergency trusteeship. This covers primarily European sales and distribution entities, but also the engineering capacity that exists on European soil. AWS's European operations, Google's Madrid, Munich, and Warsaw engineering offices, Oracle's European cloud infrastructure, and chip research facilities with European footprints all get placed under European administrative control. Leadership at every affected entity receives formal notice from European authorities that shutdown orders arriving through their normal U.S. reporting chain are legally void on European territory.
A parallel authority begins cataloguing European leverage. Deutsche Telekom operates the largest private telecommunications network in the United States. SAP sits at the operational core of a significant share of global Fortune 500 companies. European aerospace and defense supply chains run through components that U.S. defense contractors cannot replace quickly. But there are more: Contentful, Celonis, small, but many. This is not retaliation. It is the assembly of a negotiating position.
Finance ministries activate the emergency spending playbook developed during COVID and the Ukraine crisis. A €5 trillion aid package gets prepared to backstop affected industries, accelerate European infrastructure buildout, and absorb the economic shock of a prolonged disruption.
Tertiary effects are the most interesting
The tertiary effect is settlement, forced by the market crash. The aggressor will likely back down. But the crash has already done something irreversible: it has made the case for decoupling more powerfully than any politician or analyst ever could.
A EuroStack, finally.
Europe now really needs its own. Not as a political project but as an economic necessity proven in real time. The investment wave is a private capital bonanza, the largest reallocation of technology investment in European history. Every layer of the stack, cloud, operating systems, productivity software, networking, security, gets funded aggressively because the market has just demonstrated what dependency costs.
Capital detanglement
The Spain scenario exposed that nobody actually knew who controlled what. Complex cross-border shareholder structures, holding companies, and subsidiary chains made it impossible to answer the simple question: whose side is this company on? That ambiguity gets resolved by force. Regulators on both sides demand transparent ownership. Companies are required to demonstrate clear jurisdictional identity. The era of deliberately ambiguous corporate geography ends.
Deglobalization on steroids
Once ownership is clear and stack allegiance is established, procurement follows in both directions.
Not just software, but hardware economy decoupling becomes truly painful. ASML, Dutch, is the sole supplier of the machines that print every advanced chip on earth, including American ones. U.S. pharma manufactures its active ingredients heavily in Ireland and Germany. F-35 components are built across nine countries including the UK, the Netherlands, and Italy. These dependencies took decades to build and cannot be unwound without destroying value on both sides.
The world does not split dramatically. But once nations start thinking in independence rather than counter-dependence, the logic is self-completing. Every dependency identified becomes a vulnerability to be eliminated. Every dependence eliminated becomes a market to be built domestically.
The good old days of globalization
Remember the G8 summit in Genoa, July 2001? Three hundred thousand people on the streets. Carlo Giuliani shot dead by police. A generation defined its politics by opposing globalization, free trade, and global interconnectedness.
After this imaginary Spain/Google event, the same generation will sit in armchairs watching their streaming service buffer on a locally compliant European cloud, paying more for everything. And they will quietly shed a tear for the globalization they once marched against.
