Use case
Drone detection for defence and government
At a defence site the question is rarely whether you want detection, but under what conditions you let a system in. Where does the data sit, who can switch it off, and what happens if the supplier is gone tomorrow.
Why people fly above a site like this
- Reconnaissance of positions, vehicles and supply routes.
- Recording of exercises and movements by parties without permission to do so.
- Systematic interest that only becomes visible when you lay months of observations side by side.
What a deployment looks like
- Number of units
- Depends on the size of the site. We give a figure based on your site plan and the available mounting points.
- Mounting
- Existing masts, roofs or a temporary setup during an exercise.
- Deployment model
- Fully offline on your own hardware. No cloud dependency, no licence key, no remote shutdown, no telemetry leaving your network.
- Alerts
- Through the SAPIENT-compliant API into your fusion node, alongside REST and webhooks.
Where the limit sits
The DRID is a passive receiver. It detects and identifies; it does not intervene. Intervention is reserved for authorised services with approved means. Anyone looking for an effector is looking for something other than this.
Your situation not among them?
Describe your site and what you want to know. We will say honestly whether Remote ID detection is the right tool for it.