Who Controls the Kill Switch? When One Man Can Veto a War

In September 2022, Ukrainian forces prepared to launch a drone strike on the Russian naval fleet anchored off Crimea. The drones never arrived.

Elon Musk had decided, unilaterally, not to activate Starlink coverage over the region. But he wasn't simply declining to help. SpaceX had already been managing battlefield access for both sides: restricting Russian use, imposing speed limits to prevent drone integration, and maintaining a verified whitelist with Ukraine's Ministry of Defense. One private citizen, with no security clearance and no accountability to any electorate, was governing the battlefield connectivity of an active war.

The public debate treats this as a story about Elon Musk — his politics, his proximity to the White House, his X posts. That framing lets the actual problem off the hook. Replace Musk with the most patriotic, internationalist, apolitical CEO imaginable and the structural problem remains identical. The Pentagon has spent a decade building critical military functions on infrastructure it can’t legally compel, and the consequences are now arriving in real time.

A common reflex is to argue that private defense contractors have always been central to American military power. Lockheed Martin builds the F-35; Raytheon builds the Patriot. What’s different now is the control plane: who has real-time administrative control during use. When the government buys a tank, it owns it. The keys don’t expire. The manufacturer can’t disable it mid-mission or impose terms in combat. Software and AI are different. Vendors keep ongoing control — updates, access, and usage limits. They don’t sell a capability; they license access to one, and the license has conditions.