Ukraine’s wartime playbook shows how the Gulf can protect AI infrastructure

Foreign Policy’s core argument is straightforward, and it matters: Ukraine offers lessons in how to keep infrastructure alive in wartime, and those lessons apply to the Gulf’s AI ambitions even as the region faces Iranian attacks. In other words, the question is not whether tensions exist, but whether AI-relevant systems can keep operating when the real world gets noisy and unsafe.

That framing changes how executives should think. AI buildout is not just algorithms and models. It is power, connectivity, data centers, cloud capacity, procurement, and the ability to maintain services while disruptions multiply. Ukraine’s wartime experience becomes less of a distant geopolitical sidebar and more of a practical operations blueprint: protect the underlying systems that make AI work, so your roadmap survives the moment your environment stops being predictable.

To understand why this is the right lens, it helps to remember how AI ambitions typically get resourced and governed. Many Gulf initiatives are presented as national or sector strategies, but execution still depends on a chain of infrastructure decisions: generation and distribution of electricity, secure network routing, hardware availability, cybersecurity controls, and the logistics of keeping facilities staffed and stocked. In stable times, those dependencies can look invisible, because performance is consistent and incidents are rare. In wartime conditions, the same dependencies stop being background and become the main story. If your infrastructure fails, your AI plans do not simply “pause.” They lose momentum, trust, and sometimes regulatory standing.

Regulatory and risk framing also tends to follow operational reality, not ambition. Governments that want AI to scale must address security, data governance, and continuity of services. When attacks happen, regulators and risk committees shift from long-range compliance to emergency readiness. That shift can be costly if organizations have treated resilience as an afterthought. Ukraine’s experience, as summarized by Foreign Policy, pushes the opposite approach: assume disruption, design for continuity, and keep systems functioning long enough for the business side to make it through the crisis.

There is also a second-order board-level dynamic here. Boards and executive teams often face a temptation to respond to geopolitical shocks with messaging, reprioritization, and selective investment. Those moves can be necessary, but they can also create a dangerous illusion that strategy is driving outcomes. The Ukraine lesson is that outcomes are often driven by whether critical infrastructure is kept running and recoverable. That means governance should ask harder questions about resilience metrics: what happens to compute capacity during outages, how quickly services can be restored, what redundancies exist in power and network, and how incident response plans connect to operational owners across suppliers.

Capital allocation is where the stakes become personal for executives and investors. AI initiatives are typically capital intensive and timeline sensitive. If resilience planning is weak, funding may get trapped in timelines that slip, contracts that fail, or projects that stall because a dependency was not protected. Conversely, organizations that internalize the wartime mindset can preserve delivery schedules even when the external environment deteriorates. The advantage is not that they avoid risk entirely. The advantage is that they do not let risk become a full stop.

For peers building AI in the Gulf, the broader strategic implication is a shift in what “ambitions” means. Ambitions without operational continuity are fragile. The Gulf’s AI roadmap, in this Foreign Policy framing, should be judged by whether infrastructure stays alive when attacks occur, not by whether plans look good in calm periods. The executives who take that seriously now will be better positioned when the next disruption hits, because they will already have the playbook for keeping the engine running.