Turning compliance into a controlled onboard process

LEO connectivity in China is being discussed a lot right now, and it makes sense.

LEO, or Low Earth Orbit satellite internet, has quickly become a natural part of modern onboard connectivity. Services like Starlink have raised expectations for bandwidth, latency, and everyday usability onboard, and many vessels now depend on this type of connection for both operations and crew welfare.

What used to be a “theoretical topic” has started to turn into something operational and enforceable.

China has strict requirements around radio equipment, licensing, and satellite communications within its jurisdiction. For vessels operating in or near Chinese waters, the practical expectation is becoming clearer: if an onboard connectivity service is not authorised, you need to be able to ensure it is deactivated, and you need to be able to prove it.

This creates a real operational challenge, because LEO is no longer a “nice to have”. Many vessels rely on it daily for crew welfare, operational communication, reporting, and business continuity. So the question becomes how to stay compliant, without creating uncertainty onboard, or relying on manual workarounds.

At Sea IT, we are currently developing a practical approach to this directly in the Sea IT Onboard Dashboard, together with our customers.

The feature allows the vessel to physically cut power to Starlink when required, and automatically logs the shutdown event with timestamp, GPS position, and user identity, meaning who initiated the shutdown, and when. This creates a controlled, predictable process for crews onboard, and provides traceability if needed.

This is not about slowing down digitalisation.
It is about making sure your connectivity setup can support new requirements without adding risk.

How are you handling LEO compliance today when calling China, or operating in sensitive regions?