Counter-UAS
DroneBane
A three-tier counter-UAS product family covering the full kill chain — detection, engagement, and authorized kinetic response. Built around a single insight: most facilities can't afford a $100,000 sensor array, and most warfighters can't carry one. The phone in your pocket is the first sensor; the same architecture scales to a 16-point interlock weapons release running in ATAK.
Product family
Three tiers, one architecture
Each tier shares core sensor abstractions, telemetry models, and the same backend. The difference between Watch and Mobile is not what they detect — it's what they're authorized to do about it.
DroneBane Watch
Detect ProductionForce protection, base security, critical infrastructure
A passive airspace awareness app that turns the phone in every operator's pocket into a Remote ID receiver. BLE + WiFi scan, multi-sensor fusion, zone management, FAA-format incident reporting. Built for the security director, the watch officer, and the FOB perimeter team.
DroneBane Pro
Engage RoadmapCritical infrastructure, base defense, force protection
Everything in Watch plus full MAVLink C2, sensor fusion hub, autonomous patrol, and fleet management. Connects any ArduPilot/PX4 flight controller via USB OTG to a compact radio modem. Drop-in interface for any RF/radar/acoustic/EO-IR sensor that speaks REST or MQTT. The bridge between detection and kinetic response.
DroneBane Mobile
Authorize TRL 3DoD / IC / coalition counter-UAS units
C2 designed for kinetic counter-UAS interceptors, fully integrated as a native ATAK plugin. Full F2T2EA kill chain with 16-point safety interlocks, multi-level authorization, on-device DRL guidance, and audit-grade engagement logging. Anduril Lattice integration prepped for COP interoperability. Design aligned with DoD Directive 3000.09.
Kill chain
F2T2EA — Find, Fix, Track, Target, Engage, Assess
DroneBane Mobile implements the full military kill chain as a phase-gated state machine. Phases progress only forward (or abort to STANDBY). AUTHORIZE and ENGAGE require explicit Weapons-level human authorization — they cannot proceed automatically under any condition.
System idle, no active engagement
Target detected by sensors
Target being actively tracked
Target classification in progress
Awaiting human engagement authorization
Active weapon engagement
Battle Damage Assessment
Defense in depth
16-point safety interlock system
All sixteen interlocks must pass before weapon release is authorized. They cover the weapon system, target validation, operator authorization, vehicle state, and the operational envelope. Source code refuses to instantiate the interlock checker with checks disabled — the only way to bypass an interlock is in unit tests, gated by a separate constructor.
- WEAPON_ARMED
- VEHICLE_ARMED
- IN_FLIGHT
- TARGET_LOCK
- TARGET_HOSTILE
- RANGE
- AUTHORIZATION
- NO_FRIENDLIES
- AMMO
- LINK
- WATCHDOG
- BATTERY
- GPS
- STABILIZED
- GEOFENCE
- ALTITUDE
Engagement envelope: 2m AGL minimum altitude (must be airborne), 5–120m AGL engagement window, 5–500m effective weapons range, >15% battery, 3D GPS fix with ≥4 satellites, <15°/s angular rate, >20% link quality, watchdog fed within 5s.
Failsafe
Priority-coordinated failsafes
Six failsafe types under one coordinator. Higher-priority failsafes preempt lower-priority ones — there's never a race condition where two failsafes both try to execute. Critical failsafes retry up to three times. Every trigger and action is audit-logged for after-action review.
P1 P0 P2 P3 P4 P5 Autonomy
On-device DRL intercept guidance
A trained deep reinforcement learning policy runs on-device on a companion computer (Raspberry Pi 5 or Jetson Orin Nano) at 3 Hz via ONNX Runtime. The 34-dimensional observation vector includes zero-effort-miss, time-to-go, closing velocity, off-boresight angle, and predicted kill probability.
A three-stage fallback chain ensures graceful degradation: DRL policy → classical proportional navigation → return-to-launch / hover. Human override is available at all stages via the RC transmitter. Multi-target priority queuing supports P1/P2/P3 prioritization with a strict single-engagement safety constraint.
Guidance pipeline
Interoperability
Anduril Lattice integration prepped
DroneBane Mobile ships with a complete Anduril Lattice client integration: entity publisher, entity stream subscriber, task agent listener, and tracker — verified live against the Anduril sandbox environment. Drone detections publish as Lattice Track entities, interceptor telemetry as Asset entities, geofences as Geo entities, and kill-chain transitions as task agent events. The DUSTY SHIELD scenario simulator runs a complete C-UAS engagement (FOB exclusion zone → hostile detection → IFF identification → engagement authorization → BDA → RTL) entirely through Lattice's COP.
Whatever common operating picture a unit is running — TAK, Lattice, both — DroneBane appears as a friendly track and accepts task agents from the same screen the operator already uses for everything else. Zero context switching between situational awareness and weapons control.
Compliance
Security engineering targets
The features below are implemented in source but no formal security assessment, third-party audit, or accreditation has been completed. FIPS-validated cryptographic module (not product-level validation), certificate-pinned mutual TLS, encrypted engagement chain-of-custody, multi-tier RBAC, and audit trails. Design aligned with DoD Directive 3000.09.
FIPS 140-2 validated cryptographic module (Bouncy Castle BC-FJA, CMVP #3514) — product-level FIPS validation not yet initiated
SQLCipher AES-256 encrypted engagement chain-of-custody database
Mutual TLS, certificate pinning, hardware-backed Android KeyStore enrollment
JSON-Lines audit log with command tracking, operator ID, ack status, BDA outcome
4-tier RBAC: Observer / Pilot / Weapons / Commander
DoD Directive 3000.09 alignment (autonomy in weapon systems)
Development status
TRL 3
DroneBane Mobile is in active development and lab testing. Bench power-on through first hover is complete. Every C2 command — ARM, DISARM, six flight modes, takeoff, land, RTL, guided waypoints, manual control at 20 Hz — has been verified on live hardware with command acknowledgment confirmed across all modes. 53 of 55 SITL test cases pass.
Bench power-on, initial firmware, manual flight, MAVLink integration, ATAK plugin install, first hover
CompleteCompanion computer integration — Pi 5 MAVLink routing, sensor fusion finalization
NextMulti-radio hardware abstraction (RFD900x, mLRS, SiK), full C2 delivery
PlannedIntercept geometry — bearing-to-target, pursuit guidance, lead computation
PlannedAutonomous intercept with TX override, full DRL autonomy stack air-validated
PlannedMulti-drone fleet operations validation, environmental testing, ATO documentation
Operational prototypeWant to put DroneBane on your perimeter?
Watch is available upon request. Pro and Mobile are licensed by application — defense / IC / coalition only for the Mobile tier.