→ All demonstrators Demonstrator 01 · Physical security

Argus — the eye on the site,
with a memory.

Argus watches a set of cameras and turns them into something you can question. It detects a passage, describes it, files it, and keeps the history searchable in plain language. When the call matters, a human confirms or corrects — and the system remembers the correction.

Argus interface: the viewer, the list of passages with confidence scores, two active alerts, and the agent's notebook.
Argus on our own gate, 17 November 2026 — 106 passages in 24 hours, 62 since midnight, two alerts across three cameras.
Inside Argus

Three screens, one watchman.

Detection is a component. What makes it a watchman is the layer above — the one that knows your car, dismisses the cat, and writes the night down.

Argus cameras: live streams from three cameras, with the surveillance assistant ready for a question in plain words.
Cameras — live streams, and the assistant ready for a question.
Argus real-time feed: the detection log with the agent's verdict — a car recognised as the owner's parked vehicle and dismissed.
Real time — the agent learns the owner's parked car and stops flagging it.
Argus notebook: the watcher's dated journal of passages, verdicts and reports.
The watcher's notebook — every passage, every verdict, written down and searchable.
What it does

Watch, describe, remember.

Detection is the easy part; it has been commoditised for a decade. What is missing on real sites is the layer above: someone who knows what a passage means, who can be asked a question on Monday about what happened on Saturday night, and who does not start the week with an empty memory.

Argus is that layer. The detection engine stays replaceable — it is a component, not the product.

CamerasYour existing IP cameras. No proprietary recorder, no vendor account, no stream leaving the site.
DetectionObjects, zones, trajectories and timings — computed locally, with the model you choose.
JudgementThresholds and site rules turn a detection into a level: information, attention, alert.
LanguageAn agent answers “the vans of the last three days”, opens the images, and writes the summary.
MemoryWhat was seen, concluded and decided is written into a dated journal — reusable tomorrow.
HumanFalse positive, confirmed, ignored: your verdict is stored and overrides the machine's.
The trace

Every passage leaves a file you can audit.

A detection is not a thumbnail and a timestamp. It carries its camera, its type, its confidence, its duration, the zones it crossed, and the identity of the model that produced it. When a question is asked six weeks later, the answer is a document.

Row of passage thumbnails: person, then several cars and trucks, with times.
The passage strip — person, cars, trucks, in chronological order. The image is evidence; the file is the argument.

Ask in words

“Show me the cars of the last 24 hours.” The passages appear in the viewer; you look at the images and judge. No query language, no export to a spreadsheet.

Explainable by design

Confidence, zones crossed, track, model version: the reasons behind an alert are visible, so an alert can be defended — or dismissed.

Human in the loop

Argus proposes; it does not convict. A false positive declared by a human is remembered and suppresses the noise next time.

On-site by default

Streams, images and history stay on the local machine. The site keeps working when the internet does not.

Dated journal

Each shift, each alert, each unusual night can be written into a report you can read in the morning — or hand to a client.

One console, other eyes

The same interface already hosts energy supervision. Security and infrastructure answer in the same place, in four languages.

Installation

What we need from your site.

CamerasIP cameras already in place, or specified with you. Standard protocols, no proprietary recorder.
NetworkA local network and one machine — a small industrial PC is usually enough.
ZonesAn hour on site to draw what matters: the gate, the yard, the shed, the blind spots.
RulesWhen to stay silent, when to write, when to call someone. Written down, then implemented.
PeopleOne named owner of the system, and the phone number that should ring at night.
Field notes

What a real site teaches.

Our own gate produces about thirty passages on a calm day: cars on the road, the post, a truck turning around. The useful signal is a handful of them. A system that rings for all thirty is a system that will be muted in a week.

That is why the product is not “more detections”. It is thresholds, zones, memory and a human verdict — the difference between a camera and a watchman.

Privacy is a design constraint, not a disclaimer. Retention is configured per camera, images stay local, and the agent can be told what it must never describe.
Who it is for

Sites where nobody is watching.

Remote property

Houses, farms and land that are empty most of the week, with no staff to look at a screen.

Yards & warehouses

Deliveries, comings and goings, night movements — the question is not “who”, it is “what happened”.

Worksites

Equipment, intrusions, out-of-hours presence, and a record to hand over when a claim is made.

Small industry

Access control at the gate, plus a written trace that a client or an insurer will accept.

See it against your own gate.

A pilot runs on your cameras, with your zones and your rules, for four to six weeks. You keep the history at the end.