A drone-in-a-box is a security drone that does not need a pilot on site. The drone is stored, protected and charged inside a dock (also called a base station, nest or hangar). Software opens the dock, flies a pre-planned route or goes to the location of an alarm, sends live video to operators, and brings the drone back to land and recharge. For a security team it works like a mobile camera that can reach any part of a large perimeter in a few minutes, around the clock.
- Three parts: the drone, the dock that shelters and powers it, and the software that plans, flies, records and audits each mission.
- Two modes: scheduled patrols on fixed routes, and alarm-triggered response to a location reported by fences, cameras or intrusion sensors.
- It complements fixed CCTV and guards rather than replacing them: it is good at reaching and verifying, poor at staying on scene for hours.
- Architecture matters: some systems need the vendor's cloud to fly; local-first systems keep control on site.
- In the EU, automated flights out of the pilot's sight are not open-category operations. They need the specific category route with the national aviation authority (see EU drone regulations).
What is a drone-in-a-box, exactly?
The term describes a complete system, not just an aircraft. A consumer or enterprise drone needs a person to carry it out, change batteries and fly it. A drone-in-a-box removes those manual steps: the dock is installed permanently on the site, connected to power and a network, and the drone flies automated missions from it.
In security, drone-in-a-box systems are used on large or awkward sites where fixed cameras leave gaps and foot patrols are slow: logistics yards, construction sites, solar and wind farms, substations and other critical infrastructure. Security puts specific demands on it: fast launch, reliable video, clear records, and control over who can see and command the drone.
What are the components of a drone-in-a-box system?
The drone
A multirotor with a stabilised camera, a flight controller running autopilot software, GNSS positioning, and a radio link for telemetry, commands and video. Fail-safes such as return-to-launch when the link or battery is lost are essential, because nobody is standing next to it.
The dock or base station
A weatherproof enclosure that opens for take-off and landing, protects the drone between flights and keeps it ready. Look for an ingress protection (IP) rating and climate control suited to the site.
Charging vs battery swap
Docks keep the drone powered in one of two ways. Charging docks charge the battery in place: simpler, but the drone is grounded until it is charged again. Battery-swap docks use a robotic mechanism to exchange the empty battery for a charged one, so the drone can take off again quickly. For security, the difference shows up as gaps in coverage between flights.
Edge compute
A computer on site that receives video and telemetry, runs object detection, stores recordings and hosts the operator interface. In some systems this is a thin relay to the cloud; in others it runs the whole platform.
Software
Mission planning (routes, waypoints, schedules), geofencing and no-fly zones, live video and map, alarm handling, user roles, and an audit trail of every command and configuration change.
Connectivity
A local network between dock, edge node and operators, plus optional internet access for remote viewing. How the system behaves when the internet link drops is one of the most important questions to ask.
How does an autonomous patrol or alarm response work, step by step?
- Trigger. A schedule starts a patrol, or an alarm arrives from a perimeter sensor, camera analytics or an operator.
- Pre-flight checks. The system checks drone health, battery, GNSS, link quality and its configured flight restrictions before allowing take-off.
- Launch. The dock opens and the drone takes off to a set altitude.
- Mission. The drone follows the patrol waypoints or flies to the alarm location, staying inside its geofence.
- Live video and detection. Video streams to the operator console; on-site AI can flag people or vehicles so operators look at the right moment.
- Operator decision. An operator verifies the event, can hold position or redirect the drone within policy, and decides whether to call guards or police.
- Return and land. The drone returns to the dock automatically, or earlier if a fail-safe triggers.
- Recharge or swap. The dock charges or replaces the battery and closes.
- Record. Flight log, video, detections and operator actions are stored for review and evidence.
Scheduled patrol vs alarm-triggered response
Scheduled patrols fly fixed or randomised routes at set times. They show presence and find things nobody reported, such as an open gate or a damaged fence.
Alarm-triggered response is where a drone-in-a-box earns most of its value. Most sites already have perimeter protection: fence vibration sensors, buried cable, radar, PIR detectors or analytics on fixed cameras. These systems raise alarms but many are false (animals, wind, vegetation). A drone sent to the alarm location gives an operator eyes on the spot quickly, without sending a guard to check every alert. Integration usually works through dry-contact inputs, network events or an API from the alarm or video management system; check exactly which methods a vendor supports for your equipment.
Drone-in-a-box vs static CCTV vs guard patrols
Each approach has real strengths. Most security designs combine them.
| Drone-in-a-box | Static CCTV | Guard patrols | |
|---|---|---|---|
| Coverage | Any point on the site within its flight area; aerial view over obstacles | Fixed fields of view; blind spots between cameras | Wherever guards walk or drive, one place at a time |
| Response to an alarm | Automatic launch, typically minutes to reach the spot | Instant if a camera covers the spot, none if not | Depends on distance and staffing |
| Continuous watch | Limited by battery and flight rules; not designed to hover for hours | 24/7 on fixed areas | Limited by shifts |
| Physical intervention | None; it observes and records | None | Yes: can challenge, detain where lawful, fix a gate |
| Weather | Grounded by conditions beyond its limits | Mostly unaffected | Affected, but can still work |
| Regulation | Aviation rules (operator registration, authorisation for automated out-of-sight flight) plus privacy law | Privacy law | Labour and private security law |
| Records | Flight log, video and operator actions can be fully logged | Video only | Reports and body cameras where used |
A common pattern: cameras and sensors watch the perimeter, the drone verifies alarms and patrols gaps, guards respond to confirmed events.
Cloud-dependent vs local-first architectures
Drone-in-a-box platforms split into two broad designs.
Cloud-dependent systems run mission control, video handling or user login on the vendor's servers. The site needs a reliable internet link, video usually leaves the site, and an outage at the vendor or the internet provider can stop operations.
Local-first systems run the control plane, video, detection and audit on an edge node at the site. The drone keeps patrolling and responding when the internet is down; cloud features such as remote viewing or long-term storage are optional extensions. For critical sites and for operators who must keep footage under their own control, this difference often decides the purchase. The offline-first security drone guide covers it in depth.
How to choose a drone-in-a-box: buyer checklist
- Weather: the dock's IP rating, and the drone's stated wind, rain and temperature limits. Compare them with your site's climate records, not with brochure averages.
- Battery strategy: charging or battery swap, and the real turnaround time between flights.
- Offline operation: what still works with the internet disconnected? Ask for a demonstration with the WAN cable unplugged.
- Data location: where video, detections and logs are stored, who can access them, and how long they are kept.
- Access control and audit: user roles, how remote access is enabled, and whether every command and configuration change is logged and exportable.
- Link security: whether video, telemetry and control are encrypted and authenticated, and how a drone is paired with its station.
- Integration: how alarms from your existing perimeter sensors and video system reach the drone.
- Regulatory path: the operational authorisation route in your country, who holds it (you, the vendor or a service provider), and Remote ID support.
- Supply chain: where the critical components come from and how firmware is updated.
- Service: maintenance intervals, spare parts, and what happens when the drone or dock fails.
Is a drone-in-a-box legal in the EU?
Yes, but not as a plug-and-play device. Under Commission Implementing Regulation (EU) 2019/947, the open category requires the remote pilot to keep the drone in visual line of sight (VLOS) and below 120 metres. An automated drone patrolling a site from a dock, out of anyone's direct sight, falls outside those limits, so it operates in the specific category. That means an operational authorisation from the national aviation authority, based on a risk assessment such as SORA or a predefined risk assessment (PDRA), or a declaration where a standard scenario (STS) fits the operation. EASA also lists the Light UAS Operator Certificate (LUC) as a route for experienced operators.
Operators must be registered, and since 1 January 2024 drones operated in the specific category must have an active and up-to-date remote identification (Remote ID) system. In Czechia the competent authority is the Úřad pro civilní letectví (ÚCL). Video of people is also personal data under the GDPR. The EU drone regulations guide covers these steps in more detail.
This page is general information, not legal advice. Requirements and procedures vary between Member States; confirm your operation with your national aviation authority and data protection adviser.
Where Nestua fits
Nestua is a local-first security drone-in-a-box platform from Global Tech Distribution s.r.o. in the Czech Republic. Status: the software platform is functional in development builds; the drone and the base station hardware are still being built. There are no deployments yet, and demos are available on request.
The design: an ArduPilot-based drone, an IP65-rated base station with robotic battery swap for continuous patrol, and a local edge node that runs the full control plane. One edge node controls one drone; a fleet is several edge nodes linked through the optional, opt-in cloud.
- Operator cockpit: a browser app (installable as a PWA) with a live map showing drone position, heading and flight trail, dark map and satellite views, and mission and geofence overlays.
- Missions and commands: a mission editor to create waypoints and upload, start or stop patrols from the browser. Arm, take-off, land, go-to and RTL commands count as successful only after the drone's MAVLink acknowledgement, with retries and timeouts; critical commands need typed confirmation.
- Geofencing: polygon or circle geofences and no-fly zones, enforced by blocking the command or returning to launch, plus fail-safe RTL.
- Video: low-latency WebRTC video in the browser, with HLS/LL-HLS as an alternative; several video sources with a selector; local recording to a ring buffer with clip export. Uploading recordings off site is disabled by default.
- Edge AI: YOLO detection of the classes person and vehicle on the NPU of an NXP i.MX 8M Plus edge computer, entirely on site. AI rules map detections to actions (notify, record, hover, return to launch) that respect safety policy and geofences, are rate-limited and audited. It does not identify individuals.
- Encrypted radio link: Nestua's own digital link software carries H.264/H.265 video, telemetry and control with per-packet authenticated encryption (AES-256-GCM or ChaCha20-Poly1305) and hard mutual pairing.
- Governance: remote access disabled by default; a safety policy engine with re-authentication, local approval of remote commands, emergency-only mode, rate limits, time windows and drone-state gates; admin, operator and viewer roles.
- Operations: weather monitoring, watchdog-supervised services, a system health page, and an exportable event journal, command log and configuration change history.
- Hardware supply chain: critical components from European and US manufacturers, including Nestua's own H743 ArduPilot flight controller, designed and built in Europe.
If you are evaluating drone-in-a-box systems, request a demo of the platform.
Sources
- Commission Implementing Regulation (EU) 2019/947 on the rules and procedures for the operation of unmanned aircraft (Art. 4 open category, Art. 5 specific category, Art. 11 risk assessment, Art. 14 registration): eur-lex.europa.eu/eli/reg/2019/947/oj
- EASA, Specific category – civil drones (STS, PDRA, SORA, LUC): easa.europa.eu/en/domains/civil-drones-rpas/specific-category-civil-drones
- EASA, Remote identification will become mandatory for drones across Europe: easa.europa.eu/en/document-library/general-publications/remote-identification-will-become-mandatory-drones-across
- Úřad pro civilní letectví (ÚCL), Specifická kategorie: caa.gov.cz/provoz/bezpilotni-letadla/specificka-kategorie-specific/
- Regulation (EU) 2016/679 (GDPR): eur-lex.europa.eu/eli/reg/2016/679/oj