Maritime domain awareness
One picture of your waters, orbit to harbour
What it is
Maritime domain awareness (MDA) is the effective understanding of everything in a nation's waters that could affect its security, economy or environment: a single picture assembled from orbital surveillance, satellite fisheries intelligence and protected port infrastructure. It is what turns an exclusive economic zone from a line on a map into something governed.
How it is employed
MDA is built in layers: satellites detect and track vessels across the EEZ and beyond, satellite-data fisheries analytics flag unregulated fishing across the grounds, and hardened port systems keep the infrastructure that receives the picture trustworthy. Detections cue patrol assets, turning scarce hulls into a response force.
Why it matters now
Illegal fishing drains coastal economies across Africa and the Indian Ocean, smuggling and grey-zone activity exploit unwatched waters, and nations relying on shared coalition feeds see their own EEZ through someone else's priorities. The waters a state cannot see, it does not control.
Procurement & integration
MDA is procured as an architecture with a growth path, from data services toward sovereign sensing, scoped to the waters, ports and threats that matter. Unstrat represents the orbital, fisheries-analytics and cyber layers through one accountable channel, with training that builds the national watch floor.
Sourcing routes compared
| Consideration | Major-power prime | Independent principal via Unstrat |
|---|---|---|
| Whose priorities | Coalition feeds serve coalition priorities first | The picture is tasked on your waters and accountable to your flag |
| Coverage depth | Raw vessel feeds miss fisheries intelligence and the port estate | Orbit, fisheries analytics and port infrastructure in one architecture |
| Political conditions | Disclosure rules, re-export restrictions and upgrade approvals held by a foreign government | Independent, non-aligned origin, accountable to the buyer's flag |
| Accountability | Multiple contractors and a foreign prime's release schedule | One accountable team from first briefing through delivery and in-region sustainment |
Comparison is qualitative. Detailed specifications are shared under briefing once the export-control position for your market is confirmed.
Delivered by
Related capabilities
View all →Questions buyers ask
What is maritime domain awareness?
Maritime domain awareness is the effective understanding of everything in a nation's waters that could affect its security, economy or environment, assembled into a single picture from orbital surveillance, satellite fisheries intelligence and protected port infrastructure. It is what turns an exclusive economic zone from a line on a map into something governed.
What are the layers of a maritime domain awareness architecture?
It is built in layers: satellites detect and track vessels across the EEZ and beyond, satellite-data fisheries analytics flag unregulated fishing across the grounds, and hardened port systems keep the infrastructure that receives the picture trustworthy. Detections cue patrol assets, turning scarce hulls into a response force.
See: Ocean surveillance satellites capabilityFish detection capability
Why build sovereign maritime domain awareness instead of relying on shared feeds?
Nations relying on shared coalition feeds see their own EEZ through someone else's priorities, and raw vessel feeds miss both fisheries intelligence and the port estate. A picture tasked on your waters and accountable to your flag governs the whole domain, from orbit to harbour, rather than the parts a feed happens to cover.
Maritime domain awareness architecture with a growth path from data services to sovereign sensing
MDA is procured as an architecture with a growth path, scoped to the waters, ports and threats that matter. We represent the orbital, fisheries-analytics and cyber layers through one accountable channel, with training that builds the national watch floor, so the capability grows from data services toward sovereign sensing rather than deeper subscription.
See: Maritime domain awareness solutionSovereign ground segment against a data service
One maritime picture covering orbit, fisheries and the port estate rather than three procurements
Raw vessel feeds miss fisheries intelligence and the port estate, so coverage depth is the argument for an architecture rather than a single feed. We combine orbital surveillance, fisheries analytics and port infrastructure protection in one architecture through one accountable channel, so the nation is not stitching three separate procurements into a picture.
MDA that turns limited patrol assets into a response force
Detections from the orbital layer cue patrol vessels and aircraft, so scarce hulls respond to known contacts instead of searching empty water. The whole point of the architecture is that the picture makes a small force effective across a large EEZ by directing it, not by growing it.
Maritime domain awareness for illegal-fishing and grey-zone threats across an EEZ
Illegal fishing drains coastal economies and grey-zone activity exploits unwatched waters, and both are addressed by the same layered picture: orbital sensing surfaces vessels, fisheries analytics flag unregulated fishing, and the port layer keeps the receiving infrastructure trustworthy. The threat the architecture answers is the water a state cannot see, because what it cannot see it does not control.
Who runs the national watch floor once an MDA architecture is delivered
National staff do. Training that builds the watch floor is part of the procurement, because an architecture that only a foreign team can operate is not sovereign awareness. We deliver the layers and the training through one accountable channel so the picture is compiled and acted on inside national control.
We depend on coalition maritime feeds today. How does a sovereign MDA architecture change what our waters mean?
Coalition feeds serve coalition priorities first, so your EEZ waits behind someone else's queue. An MDA picture tasked on your waters and accountable to your flag removes that queue and adds the fisheries and port layers a raw feed leaves out. Structured as an architecture with a growth path, each stage moves toward national ownership rather than deeper dependency.
See: Maritime domain awareness solutionOcean surveillance satellites capability
How do the surveillance, fisheries and cyber layers of MDA actually reinforce each other?
Orbital sensing detects and tracks vessels, fisheries analytics turn that activity into enforcement and stock intelligence, and hardened port systems keep the infrastructure receiving the picture trustworthy. Built together, detections cue patrols and the picture stays reliable; procured separately, the gaps between layers are where illegal activity and cyber risk hide.
See: Maritime cybersecurity capabilityFish detection capability
Can a nation build maritime domain awareness in stages, and how is the growth path structured?
Yes. MDA is procured as an architecture with a growth path from data services toward sovereign sensing, scoped to the waters, ports and threats that matter. We represent the layers through one accountable channel and build the national watch floor through training, so the capability can start as a service and grow into national ownership.
See: Sovereign ground segment against a data serviceHow we deliver programmes
How does MDA relate to broader intelligence, surveillance and reconnaissance across the force?
Maritime domain awareness is the maritime application of the same ISR discipline: sensing tasked on national priorities, fused into a picture, and used to cue a response. Treating it as part of the force's wider ISR posture keeps the maritime watch floor connected to the national picture rather than isolated in one agency.
What figures does the site publish for an MDA architecture, and what should a nation specify?
This reference page describes the architecture and its procurement model rather than coverage, revisit or detection figures, so any number quoted without a defined scope is guesswork. Specify the waters, ports and threats that matter and the response assets to be cued, then scope the layers to them. We build the model around that requirement rather than a fixed product.
See: Maritime domain awareness capabilityThe evidence we stand behind
If we start MDA as a data service, how do we avoid locking ourselves into perpetual subscription?
By writing the growth path into the architecture from the start, so the service stage builds toward sovereign sensing and a national ground segment rather than an open-ended feed. The reason MDA is scoped as an architecture with a growth path is precisely to keep each stage moving toward ownership instead of deeper dependency.
See: Sovereign ground segment against a data serviceOcean surveillance satellites capability
How do we make sure the port systems that receive our maritime picture are not the weak point?
The picture is only as trustworthy as the infrastructure carrying it, which is why hardened port and network systems are a layer of the architecture rather than an afterthought. Maritime cybersecurity keeps the receiving estate reliable, so the awareness that cues patrols cannot itself be turned into an attack surface. We deliver the sensing and cyber layers through one channel.
See: Maritime cybersecurity capabilityMaritime domain awareness solution