ISR: intelligence, surveillance & reconnaissance
Collection tasked on your questions, not a partner's
What it is
Intelligence, surveillance and reconnaissance (ISR) is the coordinated collection, processing and delivery of information to commanders: persistent overhead observation, wide-area sensing and the secure links that carry the picture. It is the capability that turns raw sensing into decisions.
How it is employed
ISR is layered by altitude and persistence: satellites provide wide-area, repeat-visit coverage while field-built unmanned aircraft hold named areas of interest for hours. The layers cue one another, and the product flows to the commander over secure datalinks.
Why it matters now
Forces that depend on coalition-provided ISR inherit coalition priorities and data-sharing obligations: they see their own territory through someone else's tasking. Borders, coastlines and infrastructure in many states are too long to hold with patrols alone; a sovereign ISR layer is the affordable alternative to mass.
Procurement & integration
ISR is procured as an architecture, not a platform: sensor mix, persistence, datalink security and the analyst pipeline are designed together. Unstrat represents the airborne and orbital layers through one channel, with training and in-region sustainment structured into the programme from the start.
Sourcing routes compared
| Consideration | Major-power prime | Independent principal via Unstrat |
|---|---|---|
| Tasking control | Coalition feeds serve coalition priorities first | Collection tasked on the buyer's priorities alone |
| Data custody | Product shared under coalition arrangements | The picture belongs to the force that collects it |
| 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 sovereign ISR?
ISR is the coordinated collection, processing and delivery of information to commanders: persistent overhead observation, wide-area sensing and the secure links that carry the picture. Sovereign ISR means that chain is tasked on your own questions rather than a partner's, so collection is not filtered through another government's priorities. It is the capability that turns raw sensing into decisions.
Why is coalition-provided ISR a dependency?
Forces that depend on coalition-provided ISR inherit coalition priorities and data-sharing obligations, so they see their own territory through someone else's tasking. A sovereign layer keeps both the tasking queue and the product under national control. It is the affordable alternative to holding long borders and coastlines with patrols alone.
What does an ISR architecture include?
It is procured as an architecture rather than a platform: sensor mix, persistence, datalink security and the analyst pipeline are designed together. We represent the airborne and orbital layers through one channel, with training and in-region sustainment built in from the start. The layers cue one another so scarce assets act as a response force rather than a search force.
How is ISR layered between satellites and unmanned aircraft?
It is layered by altitude and persistence: satellites give wide-area, repeat-visit coverage while field-built unmanned aircraft hold named areas of interest for hours. The layers cue one another and the product flows to the commander over secure datalinks. We represent both the orbital and airborne layers through one channel.
Which products deliver the ISR capability in the portfolio?
ISR draws on field-built unmanned aircraft plus observation and ocean-surveillance satellites, tied together by secure links and an analyst pipeline. The capability page maps those products because ISR is an architecture assembled from them rather than a single box. Which mix a buyer needs depends on the areas and persistence required.
See: Modular aerial platform kitsOcean-surveillance satellites
How does ISR support border and maritime surveillance without mass?
Borders, coastlines and infrastructure in many states are too long to hold with patrols alone, and a sovereign ISR layer is the affordable alternative to mass. Overhead collection cues the scarce hulls and aircraft, turning them into a response force rather than a search force. The picture belongs to the force that collects it.
See: Maritime domain awarenessBorder and territorial surveillance
Who owns the ISR product on the independent route?
The picture belongs to the force that collects it, rather than being shared under coalition arrangements. Data custody and tasking control are the two rows where the independent route differs most from coalition feeds. That ownership is the practical meaning of sovereign ISR.
How does secure datalink custody affect an ISR architecture?
The picture only stays sovereign if the links that carry it do, so datalink security is designed into the architecture rather than added later. We represent the airborne and orbital layers through one channel so the links are planned with the sensors. That keeps the product flowing to the commander without a foreign party in the path.
We rely on allied ISR feeds and see our own region on their schedule. How would a sovereign ISR layer change that?
It moves the tasking queue under your control, so collection answers your priorities first rather than waiting behind a coalition's. The architecture pairs repeat-visit satellite coverage with unmanned aircraft that dwell over named areas, and the product stays with the force that collects it. That removes both the release lag and the data-sharing obligation that come with borrowed feeds.
See: Tasking control and data custodySovereign ISR as a solution
How should an ISR programme be structured so the analyst pipeline and datalink security are not left out?
Design the architecture whole: sensor mix, persistence, datalink security and the analyst pipeline together, not as separate buys. We represent the airborne and orbital layers through one channel and structure training and in-region sustainment into the programme from the start. The measure is what your analysts and operators can do without the delivery team present.
See: ISR procured as an architectureHow we deliver and sustain
How does ISR connect to strike and counter-drone capabilities across the portfolio?
ISR is the find-and-fix layer that attack drones and loitering munitions depend on, and its sensing feeds the counter-drone air picture as well. That is why the capability sits alongside strike and counter-UAS references rather than in isolation. Collection cues the effectors; without it the strike decision is blind.
What growth path does ISR offer a state starting from a modest budget?
A state can begin with the airborne layer and assured tasking on satellites, then grow toward dedicated and sovereign collection as ambition and budget allow. Because we represent both layers through one channel, each stage builds toward ownership rather than deeper subscription. The satellite intelligence and observation-satellite references set out the orbital half of that path.
What performance figures does the ISR capability page publish, and where do specifics live?
The ISR page is an architecture reference: it covers doctrine, threat context, procurement and the tasking-and-custody comparison, not sensor performance numbers. Resolution, revisit rate and endurance are properties of the specific satellites and aircraft, held in their catalogue entries to what we can stand behind. We do not fabricate architecture-level figures, so where a number is not published we say so and scope it under enquiry.
See: Observation satellitesRequest an ISR architecture briefing
How does a sovereign ISR layer support holding a long maritime boundary without a large fleet?
Ocean-surveillance satellites give wide-area coverage that no single vessel can survey from the water, and their detections cue the scarce hulls and aircraft as a response force rather than a search force. The airborne layer then dwells over the areas of interest the satellites flag. That is the affordable alternative to mass, and it is why ISR maps to the ocean-surveillance product alongside the observation satellites.
What does the ISR capability reference not cover, and where should a buyer look for those specifics?
The ISR page is an architecture reference, so it does not carry sensor resolution, revisit rate or endurance figures, which are properties of the specific satellites and aircraft. Those live in the relevant catalogue entries, held to what we can stand behind, with gaps marked rather than filled. We do not invent architecture-level performance numbers, so where a figure is not published we say so and scope it under enquiry.
See: Modular aerial platform kits against a named systemSovereign ISR as a solution