Digital Sovereignty: Why Europe May Replace US Tech

7 min read · Last updated: October 24, 2026

According to the Wall Street Journal, as cited by Steve Blank on October 24, 2026, Elon Musk personally ordered restrictions on Starshield, the military version of Starlink, in Ukraine. Blank says Europe now sees every US tech vendor as a possible kill switch, and that AI has made building sovereign replacements affordable for the first time.

Came here from Instagram, LinkedIn, X or YouTube? Here is the full source list you came for. Everything below is built from these, nothing else.

The essay

• Steve Blank, "Elon Musk Just Gave Europe a Reason to Replace American Technology", October 24, 2026

The discussion

• Hacker News thread, 135 points and 79 comments as of October 24, 2026

Key takeaways

• Steve Blank spent the last month in London listening to policymakers react to the Starshield restrictions in Ukraine.
• Citing the Wall Street Journal, he says the restrictions were ordered personally by Elon Musk, not announced as US foreign policy.
• European decision makers are now asking what happens if Microsoft, OpenAI, Anthropic, Oracle, Palantir or Google cut access too.
• Blank estimates the loss of trust may cost American companies tens if not hundreds of billions in revenue over the coming years.
• His core argument on digital sovereignty: AI collapses the cost of rebuilding Office, Oracle, Salesforce, Palantir and Anduril class products.
• His sales advice: a US founder selling to European defense or government now needs an answer to "who holds the switch" before the first meeting.

What happened with Starlink and Ukraine?

The United States shut off intelligence to Ukraine and throttled Starshield, the military version of SpaceX's Starlink satellite internet service. Steve Blank writes that, according to the Wall Street Journal, Elon Musk personally ordered the restrictions, and that the effect was to tilt Russia's war against Ukraine in favor of Russia.

Blank stresses that this was not an articulated US foreign policy or an announced act of government. From news accounts, he writes, it looks like the personal decision of one American CEO acting alone. Why Musk did it is unclear, and commenters under the essay dispute the motive with claims nobody has verified. Blank's point is that, for Europe, the reason is "almost beside the point."

Why does a tech kill switch matter to developers outside defense?

It matters because the same logic applies to software you depend on every day. Blank reports European leaders now asking what capabilities they would lose if enterprise software or AI from US companies went dark. If a vendor can switch off a military network mid-war, a buyer will assume it can switch off an API, a cloud account or a model.

Here is the quote that captures the mood in Europe, in Blank's words:

The U.S. is an unreliable security and technology partner willing to throw any partner under the bus, at any time, for any reason.

That is how European buyers are hearing it, according to Blank. It is not a neutral finding. But buyers act on how risk feels, and that feeling just changed.

For years, doomsayers in the UK and Europe worried that the US held a kill switch over weapon systems and critical commercial technology. Blank admits he thought that was "a paranoid fantasy." Then it happened.

The specific companies named in the conversations he heard are the ones most of us build on: Microsoft, OpenAI, Anthropic, Oracle, Palantir and Google. A scenario he calls "laughable" until this week is now, for many European decision makers, "no longer outside the realm of possibility."

If your product sits on top of those platforms and you sell to European customers, your vendor's risk is now your risk in their eyes.

What is digital sovereignty, and why is AI changing the math?

Digital sovereignty is a nation's ability to run its critical software, data and infrastructure without depending on a foreign supplier who could cut it off. Blank argues Europe debated it for years but saw cloning top US products as "an insurmountable problem." AI changes that, he says, by collapsing the cost of building sovereign software.

The timing is the key part of his argument. Two things moved at once:

1. Geopolitical risk went up, so customers are more willing to switch.
2. The cost of building went down, because AI makes it cheaper to recreate features, functions and compatibility.

Blank names the products he thinks are now within reach to recreate: Microsoft Office, Oracle, Salesforce, Palantir and Anduril. He says AI puts this "well within the capabilities of most nations."

He is also clear about the limits. Some capabilities, like low-cost access to space, are still out of reach. Software is the easy part. Rockets are not.

If you want the longer view on what AI does to the cost of writing software, I covered it in how AI is actually changing developer work in 2026.

What changes in practice?

In practice, "who controls access" becomes a buying criterion next to price and features. Blank says US founders selling into European defense or government must answer "who holds the switch" before the first meeting, and European founders can now sell sovereignty itself as a feature. Over time, he expects Europe to find and build alternatives.

Here is the shift, using only what Blank describes:

Question	Before this week	After this week (per Blank)
Is a US kill switch real?	"A paranoid fantasy"	It happened, without warning
Is the US a reliable tech partner?	Assumed	Openly questioned in Europe
Can Europe clone top US software?	"An insurmountable problem"	Within reach, because of AI
What does a US founder pitch first?	Features	"Who holds the switch"
What can a European founder sell?	A cheaper copy	Sovereignty as a feature
Cost to US companies	None expected	Possibly tens to hundreds of billions

Blank's business argument is simple. If every US vendor is now a kill-switch risk, the allied market for that whole ecosystem shrinks. He writes that the US spent decades becoming the world's indispensable technology supplier, and that a big part of that advantage depended on customers believing American technology would stay reliable and available.

His closing line: "What was done in a fit of pique will cost the U.S. both leadership and jobs."

You do not have to agree with his politics to see the engineering lesson. A single external dependency with a single person able to turn it off is a design risk. We already treat a single database server that way. Europe is now treating whole vendors that way.

What should you do this week?

Start by finding out which of your critical features depend on a single vendor you cannot replace quickly. Then make one of them swappable. You do not need a full migration. You need a written answer to "who holds the switch" for each dependency, and a fallback for the one that would hurt most.

Here is a five-step version you can finish in a week.

1. List your hard dependencies. Cloud, auth, payments, email, AI models, maps. Anything where an outage or a cutoff stops your product.
2. Find them in code. In a JavaScript or TypeScript project, this shows which vendor SDKs you import and how often:

grep -rEoh "from ['\"](openai|@anthropic-ai/sdk|@google/genai|@aws-sdk/[a-z-]+|stripe)['\"]" src \
  | sort | uniq -c | sort -rn

3. Write down who holds the switch. One row per dependency, like the table below.
4. Put your riskiest dependency behind your own interface, so swapping it is a config change, not a rewrite.
5. Keep one path you can run yourself. Containers make that much easier. If you are new to them, start with what Docker is and why it matters.

A simple audit sheet looks like this:

Dependency	Who can switch it off	Time to replace	Fallback
AI model API	The provider	?	Second provider
Cloud hosting	The provider	?	Container on another host
Auth	The provider	?	Export users regularly
Payments	The provider	?	Second processor account

Fill in the question marks honestly. The longest one is your real exposure.

For step 4, the AI layer is usually the fastest win. A small wrapper lets you try providers in order and fail over when one refuses or goes down:

type Provider = {
  name: string;
  call: (prompt: string) => Promise<string>;
};

export async function withFallback(providers: Provider[], prompt: string) {
  const errors: string[] = [];
  for (const p of providers) {
    try {
      return { provider: p.name, text: await p.call(prompt) };
    } catch (err) {
      errors.push(`${p.name}: ${(err as Error).message}`);
    }
  }
  throw new Error(`All providers failed:\n${errors.join("\n")}`);
}

Your app calls withFallback, never a vendor SDK directly. Adding or removing a provider is now one line in the array. If cost is part of how you choose providers, the numbers in our breakdown of Claude cache pricing show how much the choice can move your bill.

If you sell to European customers, add one more thing: a short, plain paragraph in your docs or sales deck that answers "who holds the switch" for your product. Blank says buyers in defense and government will ask before the first meeting. Smaller buyers will start asking too.

FAQ

What is Starshield?

Starshield is the military version of Starlink, SpaceX's satellite internet service. Steve Blank writes that its throttling in Ukraine, which the Wall Street Journal reported Elon Musk ordered personally, is what triggered Europe's current concern about US technology.

Did the US government order the Starshield restrictions?

Blank writes that the US shut off intelligence to Ukraine, but describes the Starshield restrictions as a personal decision by Musk, citing the Wall Street Journal. He says it was not an articulated US foreign policy. Whether it followed a White House request or personal animosity is unknown, and he argues it does not matter to Europe.

Which US companies does Europe worry about next?

According to the conversations Blank heard in London, Microsoft, OpenAI, Anthropic, Oracle, Palantir and Google. The question being asked is what Europe would lose if enterprise software or AI from these companies were restricted or denied.

How much could this cost American tech companies?

Blank estimates it may cost American companies tens if not hundreds of billions of dollars in lost revenue in the years ahead. That is his projection, not a measured figure. His reasoning is that the allied market shrinks as Europe builds alternatives.

Pick your single riskiest dependency and put it behind your own interface this week. For the boring parts, use the free tools on Art of Code, and if you want to work on this kind of problem, browse the developer jobs board.

Written by Adithya Guttha, Founder of Art of Code.