Sauron
Sauron is a security service delivered as software. It connects to the cameras, sensors and other surveillance hardware you already run, passes what they produce to our cloud for AI-assisted analysis, and returns flagged events to your operators. It also acts on what it finds rather than only reporting it, releasing a door or closing a window through the smart hardware on your sites, with a person approving anything consequential. Records held centrally are encrypted, separated and accountable.
Cameras, sensors and gateways on the way in, and smart locks, doors, windows and barriers on the way out. If it is on the network and it exposes a way to talk to it, Sauron can be pointed at it. There is no requirement to replace any of it. Sauron models sites, devices and events rather than a single camera type, so a mix of vendors and vintages is described once and analysed consistently. Each device is registered with its own credential.
AI-assisted detection and dwell-time tracking across device views, with matching against an enrolled gallery of staff and authorised visitors. Optical fault detection identifies tampering, obstruction and glare, and separates gradual drift from sudden change.
An incident engine groups related events instead of presenting a flat alert feed. An investigation workspace follows one question across multiple events and sites. Structured search covers events, incidents, investigations and device faults.
A finding can raise an alert, open an incident, or drive connected hardware directly. Match a face against an enrolled gallery and release the smart lock on a controlled door. Close a window or drop a barrier when a site goes to a higher posture. Flag a camera that has been moved or obscured. Nothing consequential happens on its own: an action that carries weight waits until someone with the authority to release it does so, and access is granted by role, so an operator, a duty manager and an auditor each see what their work requires and no more. Execution against smart locks, access-control platforms and other building hardware is in development.
A dropped link does not lose you anything. Detections are written to disk on your side before any attempt to send them, held there while the connection is down, and delivered in order once it returns. A retry after a lost response is treated as a replay rather than a second detection, so nothing is counted twice.
An analysed detection becomes an event, and an event that matches what you have asked us to watch for is raised as an incident in the dashboard your operators already work from, with the footage and the sequence that produced it attached. We agree with you which event types warrant escalation and which are recorded without raising an alert, and who receives them. Reporting covers event and incident volume, response times, device availability, the most common event types, and which sites generate the most recurring problems.
Recognising a face is a serious thing to do on someone else’s behalf. We designed the handling of that data before the features that use it, and we hold ourselves to it in every deployment.
Encrypted at rest
Biometric records and evidence are encrypted at rest with AES-256-GCM, and TLS protects data in transit. This applies to every deployment as standard.
Keys that rotate
Every encrypted record is tagged with the key that sealed it, so keys can be retired and data re-encrypted without downtime or a maintenance window.
Separated by tenant
Your records are held apart from those of every other organisation at the structural level, rather than by a query condition that could be misapplied.
Access is recorded
A biometric record can be opened only by a role permitted to do so, and each access is written to the audit log with the user and the time it occurred.
Sauron installs as software on your side. It connects to the devices you already run, reads what they produce, and passes it to the Sauron cloud. The analysis happens there, which is what keeps the demand off your own hardware and lets the models improve without anyone visiting a site. The results are returned to the software on your side, so your operators work in one place and see finished events rather than raw feeds. The same link carries instructions back out, so the software that reads your hardware can also drive it.
Depending on the size of the deployment we may install a physical server on site. That call is made with you rather than applied as a rule, and it comes down to device count, how much you are putting through it, how long you need to retain, and what your network will carry. Where an on-site server is in place it can also carry the analysis itself, which is what allows a fully local deployment for sites that cannot be networked outward, and keeps the round trip to a connected lock or barrier inside the building.
What returns is an operational picture rather than more video to watch: what happened, where, when, and how confident the system is, correlated into incidents across every site you run. Biometric records and the evidence attached to them sit under the controls described above.
We work with organisations accountable for what their systems recorded. That includes industrial plants and utilities, commercial property and retail, logistics and transport, healthcare and education campuses, and government facilities. The requirements differ in detail, but each needs the same thing: a defensible account of what was observed and what was done about it.
We are happy to walk through how Sauron would apply to your sites: what it would watch, what you would want it to act on, and how we would deploy it.