What is the difference between AIS and a full Maritime Domain Awareness platform?

AIS is a single, cooperative transponder-based data layer that vessels are required to operate. A Maritime Domain Awareness platform fuses AIS with SAR imagery, optical satellite passes, RF emission geolocation, vessel behaviour analytics, and shore-based radar to build a picture that includes non-cooperative and deliberately dark targets. AIS alone cannot detect vessels that have switched off their transponder or are broadcasting false identities.

Why can't a small island nation simply subscribe to a commercial MDA service?

Commercial services provide data at the discretion of a foreign company operating under a foreign government's export control regime. During a diplomatic crisis, natural disaster, or conflict, service can be throttled or terminated entirely. A sovereign constellation — even a modest one of 6–12 microsatellites — guarantees uninterrupted access and gives the nation the right to share, declassify, or withhold data on its own terms.

How many satellites does a minimum viable national MDA constellation require?

For a nation with a defined Exclusive Economic Zone (EEZ) rather than global ambitions, a constellation of 6–12 LEO nanosatellites carrying combined S-AIS receivers and a multispectral imager can provide 4–6 daily passes over the EEZ. Augmented with one or two SAR microsatellites — procured via a joint programme or commercial partnership — a credible 24-hour operational picture becomes achievable at a fraction of the cost of a traditional SIGINT satellite.

Does a sovereign MDA constellation replace the need for maritime patrol aircraft or offshore patrol vessels?

No — satellites provide persistent wide-area detection and cueing; they cannot physically intercept, board, or verify. The correct architecture is to use the satellite layer to triage the operational picture and direct kinetic assets (patrol vessels, aircraft) to highest-priority contacts. This substantially reduces fuel costs and response times compared to un-cued random patrol.

What role does RF geolocation play that AIS cannot provide?

RF geolocation — as demonstrated operationally by HawkEye 360 — detects and locates radio frequency emissions including radar, VHF communications, and satellite uplinks from vessels that have disabled their AIS transponder. This is the primary technical method for detecting 'dark vessels' engaged in ship-to-ship transfers, IUU fishing, or sanctions evasion, and it is only available from a constellation specifically designed to collect and geolocate RF signals.

How does a nation protect MDA satellite data from interception or spoofing on the ground?

IMO resolution MSC.428(98) mandates that cyber risk management be integrated into the Safety Management System for vessels, and the same discipline must extend to the shore-side ground segment. Best practice requires encrypted downlinks conforming to CCSDS standards, two-factor authentication on command-and-control interfaces, and air-gapped networks for the most sensitive fusion layers. Nations should treat the ground segment as critical national infrastructure with security standards equivalent to air traffic control systems.

Can MDA satellite data be shared with allies or regional partners without compromising sovereignty?

Yes, and this is actually a major strategic advantage of sovereign ownership. A nation that owns its constellation controls exactly which data products — raw, processed, or derived — it shares, with whom, under what classification, and for how long. Regional MDA networks such as the Information Fusion Centre in Singapore demonstrate that data-sharing agreements work well when each partner retains control of its own collection assets and contributes derived products rather than raw feeds.

What is the expected operational lifespan of a LEO MDA nanosatellite, and what does replacement cost?

Modern LEO nanosatellites (3U–16U form factors) have demonstrated operational lifespans of 3–5 years before orbital decay or component degradation forces decommission. A rolling replacement strategy — launching 2–3 satellites per year rather than a single large procurement — smooths capital expenditure, incorporates sensor upgrades, and maintains continuous coverage. Unit costs for an S-AIS nanosatellite now range from $500,000 to $3M depending on sensor payload, well within the capital budgets of mid-sized maritime nations.

4.1.3Live

Maritime Domain Awareness Platforms

Integrated software platforms that fuse vessel-tracking, environmental and intelligence data into a single operating picture for navy, coast guard and port authority users.

Coast guard officers on a patrol vessel looking at navigation screens on open ocean — A brown boat near shore represents the countless vessels now tracked through satellite maritime domain awareness systems worldwide.

Satellite Maritime Domain Awareness Data Flow

1
Satellite Constellation
SAR, AIS, optical sensors detect vessels
2
Ground Station
Raw AIS and imagery downlinked hourly
3
Fusion Platform
AI cross-matches AIS gaps, dark vessels
4
Maritime Authority
Operators receive real-time vessel alerts

Satellites detect and relay vessel data continuously, enabling authorities to identify illegal or untracked ships in near real-time.

The application

Maritime Domain Awareness (MDA) is the doctrinal term for "everything one needs to know about everything happening at sea." A modern MDA platform takes the raw data layers from §4.1.1 and §4.1.2 — AIS tracks, SAR detections, RF emitter geolocations, optical imagery — and fuses them with weather, currents, intelligence reports, port calls, ownership records and sanctions lists into a single shared operating picture. It serves navies, coast guards, port authorities, fisheries enforcement, customs and search-and-rescue coordinators.

The leading reference architectures are the European Maritime Safety Agency's Integrated Maritime Services (used by all 27 EU coastal states through the SafeSeaNet Ecosystem), the US Navy's SeaVision (the platform exported to India under the May 2025 HawkEye 360 FMS package), and a small number of national systems including India's IMAC (Information Management and Analysis Centre, established at Gurugram after the 26/11 Mumbai attacks). MDA platforms are software-heavy rather than satellite-heavy — but the data layers they consume are almost entirely space-derived. The sovereignty question for India, the GCC, Egypt, and AU member nations is whether the platform itself is hosted, controlled and tunable nationally, or whether it is a foreign-supplied black box where critical logic and tip-offs flow through someone else's hands.

What matters

MDA is the operating-picture layer; the value sits in fusion, alerting and curation, not in the underlying sensors.
EMSA's Integrated Maritime Services and the US-supplied SeaVision are the dominant operational reference platforms.
Sovereignty is mostly about deployment and tuning, not satellite ownership.
The buyer is normally a national maritime authority — single-customer per country, multi-year contracts.

References

Need for sovereignty

9/ 10

Critical.

The platform is the decision surface — every alert, every tip, every priority list flows through it. A foreign black box on this layer is a foreign hand on the tiller.
Even where the underlying sensors are commercial and shared, the MDA platform should be sovereignly hosted and tuned.
Data residency requirements (PDP Act in India, GCC sovereign-cloud rules) make foreign-cloud MDA legally awkward in many jurisdictions.

Solution architecture

What it'll take to build this

Payload: None — this is a software platform. Consumes the data layers from §4.1.1 and §4.1.2.
Bus class: N/A.
Orbit & constellation: N/A.
Ground segment: Sovereign cloud or on-premise deployment within national territory. Data feeds ingested from commercial GSaaS or sovereign ground.
Data pipeline: Multi-source ingest (AIS, SAR, RF, optical, weather, intelligence). Track fusion and de-duplication. Behaviour analytics and alerting layer. Role-based access control (navy / coast guard / fisheries). API for downstream consumers.
End-user delivery: Web dashboard for operators. Mobile app for field commanders. API for integration with national security systems.
Time-to-launch (aggressive): MVP with two data layers (AIS + SAR): 6–9 months. Full multi-source platform: 12–18 months. National-deployment-with-classification: 18–24 months.
Caveats & exceptions: This is the place to compete with Western and EU vendors on price, customisation and data residency — not on satellite hardware.

Related applications

4.1.2 · Previous

Dark Vessel Tracking

All in maritime intelligence

4.1.4 · Next

Vessel Behaviour Analytics

Bring this into your sovereign programme.

All solutions Speak with engineering