01Command layer for unmanned systems

One operator. Any unmanned fleet.

DroneCommand™ is the command layer for heterogeneous unmanned systems: sovereign, post-quantum, European by design.

  • National / EU / NATO SECRET cleared
  • ISO 9001
  • ISO 27001 (TÜV SÜD)
  • NATO DIANA selected
  • NSPA registered supplier
  • NCI Agency member
  • European supply chain
LIVE SIMULATION| Unclassified dataThis is a live, unclassified simulation for demonstration purposes.
DroneCommand™ · Operator picture · simulationLIVE · T+00:00 · 6

Keyboard: Space run/hold · 1 2 4 speed · + − zoom · F follow · 0 fit · ↑ ↓ select agent · T read telemetry

02The problem

Fleets grew. Control did not.

Mixed fleets are already the norm. The software to command them is still sold one airframe at a time.

01

One fleet, five ground stations.

Each manufacturer ships its own control software. Operators switch screens instead of making decisions.

02

Vendor lock-in dressed as a platform.

Closed ecosystems force you to buy the airframe in order to get the software.

03

Foreign clouds, yesterday's cryptography.

Mission data leaves your jurisdiction, encrypted against a threat model that expires with the arrival of cryptographically relevant quantum computing.

03The agent abstraction

Every asset is an agent.

Aerial, ground and static assets are described by one command model. The operator sees capabilities and tasks, not manufacturers and protocols.

AERIAL AGENTGROUND AGENTSENSOR AGENTHARDWARE ABSTRACTION LAYER · ONE COMMAND MODEL · ONE APIONE OPERATOR PICTURE
AERIAL

An aerial drone is an agent.

Fixed-wing or multirotor, any supported manufacturer. It publishes state, accepts tasks and reports results through the same command model as every other asset.

GROUND

A ground vehicle is an agent.

Different physics, identical interface. Routes, waypoints and task handover are expressed once and resolved per asset class by the abstraction layer.

SENSOR

A static sensor is an agent.

Fixed installations contribute to the same situational picture and can trigger tasking for mobile assets without a separate console.

04Architecture

Hardware-agnostic is not a slogan. It is the architecture.

A hardware abstraction layer sits between the command layer and the vehicle. It is built on open standards and open-autopilot platforms, so the command layer never depends on an individual manufacturer's stack. Adding a manufacturer is an integration task, not a migration.

2–4 WEEKS

to integrate a new airframe type

Supported asset categories and integration status
Asset categoryIntegration status
Multirotor · open autopilotSupported
Fixed-wing · open autopilotSupported
VTOL · open autopilotSupported
Unmanned ground vehiclesSupported
Static sensor nodesSupported
Docking and housing infrastructureIntegration on request
Proprietary manufacturer stacksAssessed case by case

The full compatibility matrix is available on request.

05Delivery models

Software layer, or the whole system.

DroneCommand™ is hardware-agnostic by design. Deploy it over the fleet you already operate, or take it as an integrated system with airframes, ground station and communications supplied and validated by us. The command layer is identical either way. You are never locked into our hardware, and never locked out of it.

DroneCommand™ Software

Licensed per connected agent, any manufacturer. You supply the platforms; we supply integration for supported types and hardware abstraction development for new ones.

DroneCommand™ Integrated

MOST REQUESTED

The command layer plus validated hardware: open-autopilot airframes, edge compute, datalink, ground control, and docking infrastructure where relevant. Delivered configured, tested and documented as a single system.

DroneCommand™ Programme

Certification support, sovereign on-premise and air-gapped deployment, lifecycle support under a defence or critical-infrastructure programme.

Airframes are selected, integrated and validated by Decent Cybersecurity from open-autopilot platforms. Choosing the integrated system does not change the licensing model or the interfaces: the same abstraction layer, the same API.

06Sovereignty

Sovereign post-quantum AI.

The models that support the operator run where the mission runs, on the edge and on your infrastructure, not in a foreign cloud. Every link they touch is protected with post-quantum cryptography developed in-house. European code, European hosting, European legal jurisdiction.

SOVEREIGN

On-premise, at the edge, or fully air-gapped. No dependency on non-European AI infrastructure, no telemetry leaving your network, no vendor subject to extraterritorial data obligations. Models are deployed and operated under our control.

POST-QUANTUM

Command, telemetry and agent traffic secured with NIST-selected post-quantum algorithms (ML-KEM, ML-DSA). Crypto-agile: algorithms can be replaced without touching the flight stack.

AI THAT NEVER FLIES THE AIRCRAFT

Autonomy assists perception, classification and planning. Flight control is independent by architecture. If the AI stops, the aircraft still flies, returns and lands.

Definition

Sovereign means: European jurisdiction, your hosting, an auditable supply chain, and no foreign remote access.

Comparison between a typical non-European platform and DroneCommand™
Typical non-European platformDroneCommand™
Hardware choiceTied to the vendor's airframesAny supported manufacturer, or ours
Data jurisdictionForeign cloud, extraterritorial reachEuropean hosting, your infrastructure
CryptographyClassical algorithms onlyPost-quantum, crypto-agile
07Human control

Autonomy with a documented limit.

Authority is expressed in three tiers. Every tier is configurable, logged and auditable, and the boundary between them is enforced in the command layer rather than in policy documents.

  1. TIER 1 · AUTONOMOUSLEVEL 1 / 3

    Routine actions

    Navigation, station-keeping, sensor sweeps, data relay and return-to-base run without operator input.

  2. TIER 2 · SUPERVISEDLEVEL 2 / 3

    Confirmed actions

    Task reassignment, area changes and classification acceptance are proposed by the system and executed only on operator confirmation.

  3. TIER 3 · HUMAN AUTHORITYLEVEL 3 / 3

    Irreversible actions

    Any action that cannot be undone requires explicit, logged human authorisation. No exceptions and no automatic escalation.

"Deciding that an object is hostile is always a human decision."
What we deliberately do not build
  • No weapons integration.
  • No autonomous engagement.
  • No electronic warfare.

This is a procurement and compliance advantage. A system without engagement functions carries a narrower risk classification under the EU AI Act and a shorter path through internal review.

08Resilience

What happens when the link drops.

Degraded modes are designed, not discovered. Each failure removes capability without removing control.

Loss of datalink

The agent continues its authorised task, then executes a pre-agreed return or hold profile.

Loss of GNSS

Navigation falls back to onboard estimation and returns along the last known safe corridor.

Loss of backend connectivity

Tasking and logging continue at the edge and reconcile when the link returns.

Loss of AI compute

Autonomy assistance degrades to manual and rule-based operation. Flight control is unaffected.

Loss of the operator

Agents complete or safely terminate the current task and hold under the standing authorisation policy.

Frequently asked

Procurement questions, answered plainly.

Licensing is per connected agent, independent of manufacturer. The same licence applies whether you bring your own platforms or take the integrated system. Request pricing for a written model.

09Contact

Bring your fleet. Or let us bring the whole system.

Briefings are delivered under NDA. Technical deep-dives with our engineering team are available for qualified programmes.

Request access to technical documentation →

Enquiries

business@decentcybersecurity.eu

Include your organisation, country and area of interest. We respond to qualified enquiries and arrange briefings under NDA.

Briefings under NDARequest a briefing