Frequently asked questions

Herkeios turns the sensors you already have — or the ones you choose to add — into passive counter-UAS (C-UAS) detection. It fuses whatever's available (camera, RF, acoustic, Remote ID — radar is on the roadmap) into one real-time, actionable picture of your airspace.

You don't need proprietary sensor hardware — Herkeios works with cameras and RF/audio sensors you already own or can source independently. You do need a local server to run the edge processing software on-site (exact spec to be confirmed) and a device to run the dashboard, both on your local network with a fixed IP address.

No. Herkeios detects, tracks, and reports — it never acts on a drone directly. In the EU, mitigation of this kind is restricted to authorized state actors by law. What you do with a confirmed detection is your organization's decision.

Camera (via ONVIF/RTSP), RF, and acoustic today — radar is planned but not yet available. Results depend on real-world conditions, true of any detection system: the specific device's own capability, network conditions between your sensors and the local processing node, and environmental factors like weather, lighting, and site layout all play a part. Combining sensors raises confidence and reduces false positives, but doesn't eliminate that variability — we'd rather be upfront about it than oversell a single accuracy number.

Not yet. Radar is planned, not currently available — current sensor support covers camera (via ONVIF/RTSP), RF, and audio. We'll announce radar support on the News page once it ships.

Yes. Herkeios runs a continuously-trained detection model against your existing camera feed over standard ONVIF — no proprietary hardware required. Adding RF or acoustic later raises confidence further; radar support is on the roadmap.

Yes. RF and acoustic detection don't depend on a drone cooperating or broadcasting anything — that's exactly the gap sensor fusion is built to close.

Partially. Detection and edge processing run locally on-site and don't need an internet connection to detect and classify a drone. Connectivity is needed for the cloud-based reporting layer — incident logging, your dashboard, and report generation — not for core on-site detection.

Critical infrastructure operators, law enforcement, private and event security teams, and any organization that needs to know what's in its airspace.

It's fused into a confidence score, escalated as evidence builds, checked against your site's real zones, and logged — visible on a live command dashboard for your security team, whether or not it triggers an alert.

Every tracked object is logged, not just flagged threats — including your own authorized flights — so unusual use of your own fleet doesn't go unnoticed either.

You hold your own encryption keys — your data is encrypted before it ever leaves your site, and Herkeios cannot access or decrypt it. That means you're responsible for your own data under this architecture. Our support team can see operational health (uptime, sync status, error rates) to help keep the system running, but can't see your actual detection data, video, or reports without your explicit involvement. (This site itself has no analytics or tracking — see Legal for how contact-form submissions are handled.)

Our support team monitors system health directly — uptime, sync status, and performance — without needing access to your data. If a case genuinely requires looking at specific data content, you stay in control: you share the specific record needed directly through the dashboard. Herkeios never has standing access to your encrypted data.

Get in touch. Every site's sensor setup is different, so we start with a conversation about what you already have and what you're trying to protect.