What is the difference between satellite AIS and a maritime IoT network — aren't they the same thing?

Satellite AIS (S-AIS) is one specific application: it captures self-reported vessel identity and position broadcasts. A maritime IoT network is broader — it aggregates S-AIS alongside engine telemetry, container reefer temperature, bilge sensor data, environmental buoy readings, and port logistics signals, all via satellite backhaul. AIS is the vessel's loud announcement; maritime IoT is the full-body health check.

Why can't a nation just subscribe to Spire, HawkEye 360 or MarineTraffic instead of building its own system?

Commercial services offer fast time-to-value, but the data owner sets the access terms, retention policies, and priority queuing. During a geopolitical dispute or supply-chain disruption, a foreign provider can throttle, delay, or revoke access. A sovereign constellation gives the nation raw data custody, the ability to classify certain vessel movements, and leverage in bilateral maritime agreements — none of which a subscription can guarantee.

How many satellites does a nation actually need for adequate maritime IoT coverage?

For basic S-AIS with median latency under 30 minutes across a 200 nautical mile EEZ, modelling by ESA's ARTES programme suggests a minimum of 6 polar-inclined LEO satellites at 500–600 km altitude. A 12–18 satellite constellation brings median latency under 10 minutes. Nations with large exclusive economic zones — India's 2.37 million km², for instance — should plan for 24+ satellites to maintain near-continuous coverage.

Is a nanosatellite platform robust enough for a national maritime surveillance programme?

For S-AIS and basic IoT aggregation, 3U–6U CubeSat platforms are operationally proven — Spire and Orbcomm have demonstrated this at scale. For more demanding tasks like wideband RF geolocation (vessel fingerprinting independent of AIS self-reporting), 50–150 kg microsatellites with larger antenna apertures are preferable. A tiered architecture — nanosats for coverage, one or two microsats for precision — is a practical sovereign design choice.

How does the IMO's cyber risk management requirement affect a sovereign maritime IoT programme?

IMO Resolution MSC.428(98) requires shipowners to address cyber risk in their Safety Management Systems by 2021, but it equally implies that any national Maritime Administration offering an IoT-based vessel monitoring service must itself meet comparable cyber hygiene standards. A sovereign ground segment must implement end-to-end encryption, authenticated command uplinks, and anomaly-detection on the data pipeline — not just the vessel endpoint.

Can satellite maritime IoT help with illegal, unreported and unregulated (IUU) fishing enforcement?

Yes — and this is one of the strongest sovereignty arguments for small island and coastal developing states. Satellite IoT combined with S-AIS dark-vessel detection (cross-referencing RF emissions against declared AIS positions) has been used by Global Fishing Watch and partner nations to identify vessels fishing illegally inside EEZs. A sovereign system lets a nation act on that intelligence directly, without waiting for a third-party provider to share findings through a commercial API.

What spectrum coordination steps are required before launching a national maritime IoT satellite?

The nation must file an ITU coordination request through its national administration under the Radio Regulations Article 9 procedure, specifying orbital parameters, frequency bands, and power flux density limits. For maritime VHF bands (156–162 MHz), coordination with ITU-R Study Group 5 recommendations — particularly ITU-R M.1371 — is mandatory. The full coordination cycle typically takes 2–5 years, so spectrum filing should begin concurrently with satellite design, not after.

What happens to the investment if a sovereign constellation becomes obsolete due to rapid commercial advancement?

Satellite hardware depreciates, but the institutional capability — orbital slot registrations, trained operators, ground station infrastructure, and data-fusion pipelines — retains sovereign value regardless of which generation of hardware occupies the orbit. Nations should plan 5-year hardware refresh cycles into their programme business cases, mirroring how militaries treat radar systems: the platform ages, the capability endures.

1.5.4Live

Maritime IoT Networks

Fisherman on a small wooden boat at sea holding a handheld tracking or communication device — A fishing boat isolated at sea gains a lifeline through satellite IoT, enabling real-time tracking and communication beyond coastal reach.

Satellite IoT Connecting Ships at Sea

1
LEO Constellation
Small satellites collect vessel sensor bursts
2
Ground Station
Gateway decodes and forwards maritime data
3
Cloud Analytics
Fleet position, cargo, and safety alerts processed
4
Vessel & Port
Crew and operators receive real-time decisions

Low-orbit satellites relay vessel sensor data through ground stations to cloud platforms, delivering actionable insights to ships and ports.

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.5.3 · Previous

Pipeline Sensor Networks

All in space-based iot networks

1.5.5 · Next

Smart Utility IoT

Bring this into your sovereign programme.

All solutions Speak with engineering