Why can't an offshore operator simply buy Starlink Maritime and be done with it?

Commercially available services like Starlink Maritime (SpaceX) and Inmarsat Fleet Xpress work well day-to-day, but the service terms, pricing, and spectrum licences sit under a foreign jurisdiction. If relations with that jurisdiction deteriorate — or if the operator faces bankruptcy or acquisition — the offshore installation loses connectivity with no recourse. A sovereign LEO constellation keeps the kill-switch at home.

What minimum throughput does an offshore platform actually need?

IMO GMDSS requires only 9.6 kbps for distress and safety traffic under MSC.436(99), but modern operational needs are far higher: crew welfare video calling, SCADA telemetry, remote diagnostics, and HD CCTV security feeds together typically consume 50–200 Mbps of aggregate capacity per large platform. Sovereign architecture planning should size for the operational floor, not the regulatory minimum.

Is a dedicated sovereign offshore constellation economically viable, or does demand not justify the capex?

A single sovereign constellation rarely serves offshore connectivity alone. The business case improves substantially when the same LEO microsatellite constellation serves maritime broadband (§1.8.2), fishing vessel monitoring, AIS, environmental sensing, and EEZ surveillance simultaneously — shared infrastructure across multiple government mandates. The World Bank's Broadband for All framework explicitly recommends multi-mission sovereign architectures to achieve unit-cost parity with commercial services.

How does satellite connectivity interface with the offshore platform's local network?

The satellite terminal connects to a ship-board or platform LAN running either VSAT modem with IP gateway or, increasingly, a flat-panel phased-array terminal (e.g. Intellian v110NX class). From there, traffic is segmented into IT (crew and business) and OT (SCADA, safety) VLANs, typically enforced by a firewall appliance meeting IEC 62443 industrial cybersecurity standards. Sovereign ground segments should mandate encrypted uplinks and provide government-operated network operations centres with visibility into traffic metadata.

What orbit is best for offshore connectivity — GEO or LEO?

LEO constellations at 500–1,200 km altitude deliver 40–60 ms latency versus 600 ms for GEO, which matters for real-time monitoring and crew video calls. For most offshore applications, a sovereign LEO constellation of 24–48 microsatellites in sun-synchronous or inclined orbits provides adequate revisit and continuous connectivity within the nation's EEZ. GEO may be retained as a high-capacity backbone for very high throughput fixed-platform links in benign weather regions.

Does the GMDSS reform (MSC.436(99)) affect which satellite providers an offshore operator can legally use for safety comms?

Yes. MSC.436(99) (adopted 2019, entry into force 2024) removes Inmarsat's monopoly on GMDSS recognition and opens the door for new satellite service providers — including potential sovereign operators — to gain IMO recognition as GMDSS providers, provided they meet performance standards for distress alerting, availability, and global coverage. Nations running their own constellations can apply for recognition, giving their satellites legal standing in safety communications alongside Iridium and Inmarsat.

How do offshore wind farms differ from oil platforms in connectivity requirements?

Offshore wind farms are often connected to shore by subsea fibre for high-volume SCADA, but individual turbines and service operation vessels (SOVs) in the array rely on satellite for redundancy, secondary telemetry, and crew welfare. The intermittent nature of SOV missions and the proliferation of turbines (sometimes 200+ per array) makes a satellite overlay cost-effective where fibre is impractical. WindEurope data show European offshore wind installations growing to over 35 GW by 2024, each turbine requiring continuous low-latency health monitoring.

What cybersecurity standards apply to satellite links serving offshore critical infrastructure?

Offshore platforms classified as critical national infrastructure should apply NIST SP 800-82 Rev 3 (Guide to OT Security) to their satellite-connected SCADA segments, and IEC 62443-3-3 for system-level security requirements. The UK's National Cyber Security Centre and the US CISA have both issued specific advisories noting that VSAT modems are a high-risk attack vector following the Viasat KA-SAT incident in 2022, which disrupted wind farm control links across Europe.

1.8.3Live

Offshore Connectivity

Crew member sitting on ship deck using a laptop or phone to communicate — Passengers strolling the deck of a cruise ship stay connected to shore through satellite broadband links.

Satellite Broadband Linking Ships to Shore

1
Satellite Constellation
LEO/GEO birds relay vessel signals
2
Ground Station
Coastal teleport decodes ship uplink
3
Network Hub
Routes data to public internet backbone
4
Vessel & Crew
Wi-Fi aboard enables voice, data, safety

Satellite signals travel from orbiting spacecraft through coastal ground stations to deliver broadband directly aboard ships at sea.

Page in the build queue

This application has its place in the atlas. The full page — short and long descriptions, what-matters bullets, sovereignty rationale, and the eight-field architecture block — is being written next.

Maturity reading: Operational systems exist with paying customers. Phase 1 built §4.1 (Maritime Intelligence) end-to-end as the depth-and-format reference. Section 4 is the next section to graduate from scaffold to full content; the rest follow on the roadmap.

Related applications

1.8.2 · Previous

Maritime Broadband

All in airborne & maritime connectivity

1.8.4 · Next

Cruise Ship Connectivity

Bring this into your sovereign programme.

All solutions Speak with engineering