Site-specific
Model the actual boundary, targets and constraints.
Scenario-led
Compare threat behaviours, tactics and asset mixes.
Auditable
Trace assumptions, model versions and simulation runs.
Decision support
Evidence for planning, not operational C2.
C-UAS planning is a site-specific problem.
A defensive configuration that works at one site can fail at another because of buildings, terrain, legal constraints, public proximity, permitted asset locations and response procedures.
CUAS Planner helps authorised defence, security and critical infrastructure teams test those factors together before they commit budget, change tactics or focus live trials.
What it helps you decide
The product is strongest when the buyer already knows they need C-UAS planning, but needs a defensible way to compare options.
Layout
Where should assets go?
Compare defensive placements against local geometry, line-of-sight constraints and protected targets.
Mix
Which capability mix is credible?
Sandbox different sensors, effectors and tactics against realistic Class 1 UAS threat assumptions.
Risk
What happens after interdiction?
Extend analysis beyond detection to engagement outcomes, residual penetration and ground-risk consequences.
A repeatable planning workflow
Each study can move from site definition to scenario generation, simulation campaigns and traceable outputs.
Define the site
Capture site boundary, protected areas, unsecured regions and candidate deployment zones.
2
Configure threats
Set UAS capability groups, behaviours and attack assumptions relevant to the site.
3
Select defences
Choose sensor, effector and response options to test or optimise.
4
Run campaigns
Explore many scenarios instead of relying on one live demonstration or desk study.
5
Compare outputs
Review outcomes, uncertainty and the assumptions behind each recommendation.