Skip to content
AEROTECT

Deployment models

You decide where your data sits and who can switch it off

Most detection systems talk to the vendor cloud. For a festival that is no obstacle; for a defence site it is a blocker. So the DRID also runs entirely on its own, on a server inside your network, with no connection to the outside.

Three models

From fully isolated to fully managed

The same units, the same software, three ways to put them in place. You choose on your security policy, not on what we technically force.

  • Defence and critical infrastructure

    Fully offline

    The units and the server sit in your network. There is no connection to the outside and none is needed.

    • Server runs on your own hardware or virtual machine
    • No outbound connections at all, suitable for an isolated network
    • No licence key and no activation server
    • Updates on your initiative, through a file you verify yourself
    • We have no access to the installation unless you open it yourself

    Defence sites, correctional facilities, power stations and any location where outbound traffic is not permitted.

  • Your own management

    On-premise with your own network

    Your server, your network, with a managed connection for updates and support whenever you open it.

    • Installed inside your own infrastructure or private cloud
    • Integration with your identity management, for example through SSO
    • Updates when your administrator approves them, never automatically
    • Remote support only within a window you open
    • Retention periods and export entirely under your control

    Organisations with their own IT department and an established policy for vendor software.

  • Fastest start

    AEROTECT platform, hosted

    We host the platform inside the European Union. For an event everything is ready within a day.

    • No server needed on your side, just a browser
    • Hosting and storage inside the EU
    • Temporary accounts for police or security, per deployment
    • Automatic updates and new Remote ID versions
    • Retention period set by you

    Events, temporary deployments and organisations without their own server management.

What offline means here

Four things we cannot do, and that is the point

Running offline is only worth something if the vendor has not left a back door in it. These are the commitments we can be held to.

  • No cloud dependency

    The units and the server work without an internet connection. There is no service at us or at a third party that has to be reachable for detection to work. If the internet drops, nothing about your picture changes.

  • No licence key

    The software asks for no activation and checks nothing against a key server. There is no expiry date that eventually halts the installation. What you have installed keeps working.

  • No remote shutdown

    We have no technical means to stop your installation, limit it or disable features. There is no kill switch, not even for ourselves. If there is a dispute over invoices or contracts, your system keeps running.

  • No telemetry leaving your network

    In the offline variant not a single record leaves your network. No usage statistics, no error reporting, no observations. We do not know what you detect and cannot retrieve it afterwards.

We record these points in the agreement on request, so your procurement department can refer to them formally.

Integration

Open interfaces, no closed SDK

Detection is rarely the end point. The observations have to reach the system your team already uses, whoever built it.

  • Open REST and JSON API

    All observations, zones, alerts and unit status are available through a documented REST API with JSON. No proprietary SDK, no binary protocol, no mandatory library. Any language that speaks HTTP can integrate.

  • SAPIENT

    The API also follows the SAPIENT standard for sensor integration. That lets the DRID run as a sensor inside an existing counter-UAS architecture alongside radar, camera and RF sensors, without an integrator building a translation layer.

  • Webhooks and alerts

    A zone breach can fire a webhook straight into your control room software or video management system. Alerts also go by SMS, email or push to the people you designate.

  • Export and history

    The full history exports as CSV or JSON, with timestamps and positions, for the debrief with the municipality or police and for your own analysis afterwards.

We send the interface description so your supplier can prepare the integration before anything is ordered.

Does it need to run fully offline for you?

Tell us how your network is set up and what your security policy requires. We will say exactly what is needed in hardware and management.

Contact usSee the standards