The US just announced Project Freedom: guided-missile destroyers, over 100 aircraft, and 15,000 service members deployed to escort stranded commercial vessels out of the Persian Gulf through the Strait of Hormuz starting May 5. Every tanker, bulk carrier, and yacht stuck behind Iran's near-complete blockade gets a military convoy escort to open water.
I spent a decade in military aviation. I can tell you exactly what happens to a commercial vessel's satellite link when it joins a naval escort column. It does not improve.
What a convoy does to your connectivity
Military escort operations impose communications restrictions that most commercial operators have never encountered. Emissions control protocols limit or silence non-essential RF transmitters, which includes commercial satellite uplinks. Starlink Maritime, VSAT, even backup L-band terminals can all be affected when the escort commander restricts emissions to protect the force.
Even outside full emissions control, the electromagnetic environment around a carrier strike group is dense with high-power radar and communications emitters. That hardware was designed for military systems, not for your vessel's antenna. Interference is not hypothetical. It is physics.
Then add the electronic warfare activity already documented in the strait. GPS jamming and spoofing have been standard in and around Hormuz for years. Put those together with emissions control restrictions and you get hours or days of degraded or absent satellite connectivity for any commercial vessel in the escort column. That is not a pessimistic scenario. That is the operating environment.
Cloud AI fails at the worst possible moment
If your vessel's AI runs on shore-side infrastructure, every one of those degraded hours is an hour where your systems go dark. Route optimization, guest services, crew knowledge tools, maintenance monitoring, damage assessment. Whatever your cloud-hosted AI was handling stops the moment the link degrades beyond what the API needs to function.
The irony writes itself. A military escort exists because conditions are dangerous. Dangerous conditions degrade connectivity. Degraded connectivity kills cloud AI. The net result: vessels enter the most operationally complex transit of their year with less capability than they had sitting in a calm anchorage in Dubai.
I have written before about why cloud architectures fail at sea. Hormuz is the extreme version of the same thesis. You do not need a storm or a hardware failure to lose the link. You just need to be operating near a military force. In 2026, that means the Persian Gulf, the Red Sea, the Taiwan Strait, and a growing list of contested waterways where commercial and military traffic share the same sea lanes.
What sovereign AI looks like in an escort column
A vessel running a local inference stack built on the knowledge-ark model does not notice the connectivity change. The AI keeps running on vessel hardware. Crew queries, guest requests, operational monitoring, maintenance logging: all of it functions normally because none of it depended on a shore-side API call that just timed out.
When the link comes back (likely after the vessel clears the strait and exits the escort column), the system syncs with shore-side infrastructure on its own schedule. Model updates, data exports, heavy compute jobs flow during the connectivity window. Nothing operationally critical was waiting on that window to open.
This is the same architecture we design for extended open-ocean transits and for single-provider satellite failures. The Hormuz convoy happens to be a particularly vivid demonstration of why building for disconnected operations is not paranoia. It is operational planning.
The signal for fleet operators
Project Freedom is not a one-off event. Maritime security operations in contested waterways are becoming a persistent feature of global shipping. The Red Sea rerouting around the Cape of Good Hope has been the new baseline for over a year. Emissions control conditions, electronic warfare, and military escort protocols are going to affect more commercial vessels more often.
If your fleet's AI capability disappears every time a vessel enters a security zone, you do not really have an AI capability. You have a feature that works in fair weather and safe water.
Build the vessel's intelligence to work without the link. When the destroyer takes station on your beam and the radios go quiet, that is the moment your AI architecture proves whether it was designed for the real world or for a slide deck.
Planning a vessel AI deployment that works in contested waters? Let's talk. We design sovereign AI architectures that stay operational when the satellite link drops, whether the cause is weather, distance, or a military escort column.