Why we normally run our models on a server at the site

We started with the airspace, and today we also work on wind farms and at industrial sites. Like airports, they are regulated, safety-critical environments where operators answer for what moves around them.

Before a detection system goes in at a site like these, the operator asks two questions. Where is the video processed, and where is the record of each event kept?

Both questions come before any talk of what the system detects. Their answers decide how the system fits into the site's network and into its security procedures.

Where is the video processed?

Detection, classification, and storage run on a server with NVIDIA GPUs, normally at the site, with no cloud service. The system can run on a closed network.

So the operator can answer the first question with a place: a machine that normally stands on the site's premises. A closed network is an option for sites whose security rules call for one.

Besides the server, the site hosts the cameras. We work with pan-tilt-zoom daylight and thermal cameras, so the watch continues after dark.

Detection is passive: the cameras transmit no radio signal to find a target, unlike a radar, and detection needs no spectrum license.

Back to contents

Where is the record kept?

The record is kept on the same server that processes the video, so the second question has the same answer as the first. Every figure in a report traces back to a stored event.

Back to contents

Who checks what the models find?

We build neural networks that classify each moving object from its appearance and its movement. Each site starts on a pretrained model, which we retrain on the site's own annotated footage.

Biologists in our data analysis team validate samples of the detections and review the reports that go to customers. That check has a limit: it covers samples of the detections, not every one.

Back to contents

Wouldn't a cloud service be simpler to run?

In one respect it would. Where the server sits at the site, it is one more machine for the site to house, power, and connect to the cameras. A cloud service would take that machine off the site's hands, and someone else would keep it running.

In return for that machine, processing and storage normally stay at the site, with no cloud service, and a closed network remains possible. Each figure in a report traces back to an event stored on that server. Whether the trade suits a site is for the operator to decide.

The limit of this answer sits in the word “normally”, which describes the usual arrangement and leaves room for other cases. The answers to the two questions hold for that arrangement.

Back to contents

Who builds the system?

We are an Italian deep-tech company, founded in 2017, and we design and build the system in Rimini. Our method began in flight safety, at a fighter wing of the Italian Air Force.

THE EDGE COMPANY has been a member of NVIDIA Inception since 2019. The company holds a US patent for a method of detecting moving objects, invented by Fabio Masci. The patent was granted in January 2025.

Back to contents

What do we do at the site?

Our part at each site starts before the system arrives. We run a site survey, and then we supervise the installation.

Local firms do the civil works to our specifications. We then commission each system and, once it is in service, support it remotely.

Back to contents

What stays with the operator?

Connected deterrents fire under the operator's rules, and the decision stays with the operator. That keeps accountability where it already sits. We build human-centric artificial intelligence that supports the operator in that role and does not take the operator's place.

You can test this arrangement against your own network and security procedures before anything is installed. Start with the two questions an operator asks first: where the video is processed, and where the record is kept.

We can go through them with you at a site survey, together with the people who run your network and security. To arrange one, write to us from the contacts page.

Back to contents