Ukraine kept the satellite. America changed the password.
Maxar confirmed that imagery shared with Ukraine through a US government programme had been suspended on 7 March 2025. Other imagery sources, existing data and the duration of the restriction were not established.

During Washington’s assistance pause, Ukrainian accounts lost access to Maxar imagery through a US government purchasing programme. The satellites still orbited and the company still existed; the route delivering the pictures was switched off. This was not a total intelligence blackout, but it showed how commercial capability can remain government-controlled at the access layer.
Hardware ownership is only one kind of leverage. Sometimes sovereignty is a credential that somebody else can disable.
The sales presentation will focus on performance, price and partnership. It is less likely to dwell on source code, encryption keys, mission data, cloud access, update servers, geofencing and proprietary integration rights. Yet that is where the real leverage sits once control of the hardware is treated as control of the capability. That is the control point hiding behind the headline fact: Ukraine kept the satellite.
For Ukraine, you can own the hardware and rent the mission.
The supplier may never issue a written refusal. It can explain, review, consult and postpone. The result may still be to disable, narrow or degrade the capability through software without moving a single physical asset. Your forces experience the result long before your lawyers agree on the label. For Ukraine, the warning is captured by what followed: America changed the password.
There is also a timing problem. The alternative supplier, component or service may exist, but it may need qualification, integration, training and fresh political approval. Those months count. A substitute that becomes usable after the crisis is over is not a substitute. It is an explanation for the inquiry that follows. The exercise has a concrete starting point in this case: Ukraine kept the satellite.
Your technical team will test performance. Your commercial team should test dependence just as aggressively. Who controls mission data, encryption keys and software updates? Can national engineers integrate a new weapon or sensor? Is any geography, target type or mode restricted in code?
Finally, ask what happens under pressure. What happens when cloud access or a subscription ends? Do you possess usable source code, or only an escrow promise with conditions? Can the system operate when disconnected from the supplier? A contingency that has never been funded, integrated or exercised is only optimism with a heading.
The buyer still has options: negotiate integration rights before signing the platform contract, create a national fallback for cloud and communications services and treat software support withdrawal as an operational contingency. These measures are rarely as exciting as the platform. They are often what make the platform usable.
Price that exposure honestly. A cheaper bid with one unmanageable control point may be more expensive than a higher bid that preserves options. Acquisition teams are good at comparing purchase prices. They are less consistent at pricing the cost of a grounded fleet, an empty magazine or a capability that arrives after the political need has passed. The headline fact, 'Ukraine kept the satellite', should carry that exposure in its score.
No serious buyer needs every line of source code. It does need control over the functions, data, keys and integration rights that determine whether the system can perform its national mission. That distinction matters here: America changed the password.
The final test for Ukraine is simple: what remains usable when the foreign network, update server, cloud account and integration team are unavailable? If the honest answer begins with 'provided that somebody else agrees', that condition belongs on the first page of the procurement decision, not in an annex nobody reads.
The equipment can remain in your hands while its useful functions disappear behind a login, a server decision or a line of code. The kill switch does not have to be a red button. It can be an expired credential. That risk is easy to miss when the announcement stops at 'Ukraine kept the satellite'.
AI-generated representative image.
What Unstrat can offer as a non-aligned vendor
Explore the relevant market and capabilities available through Unstrat.
