The camera is connected as a source
A workshop camera is added to the account as a video source, an archive video — as a file. Sources are combined into groups: “Workshop 3”, “Warehouse”, “Gates”.
The NeuroVision video analytics system works with the video from your cameras and with archive recordings: it helps to flag events by your rules, count visitors and find faces from your lists. You get an alert and a report, not hours of footage. Which scenarios to switch on — manufacturing, a shop or site security — we decide together in a pilot on your recordings. Faces are matched only against lists of people who have given consent; the other scenarios work without establishing identity.
NeuroVision video analytics
A person makes the decision on an event; faces are matched against lists of people who have given consent
We connect your cameras and archive recordings as sources. We choose the camera requirements for the task and check them in the pilot.
An ordinary video surveillance system writes an archive, and it is opened when something has already happened. AI video analytics processes the video straight away and flags what matters by your rules — for example, a person in a restricted area or a crowd at the tills. The log holds a frame and a time, not eight hours of footage. We confirm the set of rules in the pilot.
Video analytics does not punish and does not open the gate by itself. It sends the event to an occupational safety engineer, a shop manager or a security guard, and the person decides what to do. You discuss the rules, zones and thresholds with us and change them as you go.
A video analytics platform with five scenarios. They are switched on one by one — for the task and for the cameras already installed at the site.
An example — a metal structures workshop where a hard hat and a high-visibility vest are mandatory in the overhead crane zone.
The employer is obliged not only to issue protective equipment but also to organise control over its correct use. Occupational safety with video analytics means PPE control by camera in every shift, not only on a scheduled walk-round. Below are the scenarios we discuss in the pilot; we confirm the set of functions for your site.
Crane, assembly and loading zones. A person in the frame without a hard hat — an event for the area foreman, with a frame and a time.
Forklift routes, warehouses, in-plant transport paths. A missing vest is visible on the camera from a distance.
Paint shops, food production, laboratories. Control of mask and goggle wearing where the occupational safety instruction requires it.
A person under a load, next to a running machine or behind a barrier. Entering the zone is flagged regardless of whether the person wears a hard hat.
A rule is tied to a shift: a hard hat and vest are mandatory during working hours, and at night there should be nobody in the workshop.
Violations by zone, shift and PPE type: where to move a sign, put up a barrier or hold an unscheduled briefing.
Traffic and conversion
The number of visitors by hour and day. You can see when the shop is full but there are no sales, and when staff are short. The comparison with the number of receipts — from the data of your till system.
Queues at the tills
The system can count people in the till area and send an event when the queue is longer than the set limit: the manager opens another till before the customers leave.
Zones and time at a display
How many people came up to a promo stand and how long they spent at it. Gender and age group — in anonymised form, for the report on the shop's audience.
Staff areas and the stockroom
A stranger behind the counter or in the stockroom after closing, an open back door — an event for the shop security.
Customer analytics in a shop from the cameras that already hang above the entrance and the tills. People are counted, not recognised: the report holds numbers and times, without faces. We refine the metrics in the pilot.
Visitor counting does not match faces against a database and does not recognise regular customers. Recognising customers by face is a separate scenario: only against a list of those who have given consent (the “What data each function processes” block).
Video analytics for site security takes the routine off the guards: watching an empty perimeter and scrolling through the archive after an incident. We refine the scenarios below in the pilot.
A person crossed the fence line, entered a zone after closing or lingered at the server room door. The guards receive an event with a frame, not a sensor signal without a picture.
Suitable for:
for warehouses, industrial sites, car parks
Events at the entrance: a vehicle at the gate outside working hours, movement at the checkpoint. Reading vehicle licence plates and an entry log are discussed for the project — which formats are needed and whether the product has them.
Suitable for:
for checkpoints, logistics centres, car parks
A face in the frame matched a person from your list — the guards receive an alert and decide for themselves what to do. The lists are only those you have compiled, with a lawful basis for each person.
Suitable for:
for sites with their own security service
If a camera is installed at the checkpoint, video analytics is complemented by face-based access control: the passage opens for employees from the access list who have given consent. More on the page on Face-recognition access control.
Suitable for:
for business centres, factories, warehouses
Not all video analytics is biometrics. Personal data becomes biometric when a face is used to establish who is in front of the camera (Part 1 of Art. 11 of 152‑FZ). Most scenarios do not do this — and a conversation with a lawyer is easier to start from this table.
Does not recognise everyone
A face is matched only against your lists. A person who is not on the lists remains a “face with no match” for the system — nobody establishes their name.
Does not search for people on the internet
There is no search across social networks and open sources, and there will not be. The source is only your cameras, your archive and your lists.
Does not punish for violations
An event is a reason for the foreman to come over and talk, not an automatic fine. Disciplinary decisions are taken by the employer under the Labour Code; video analytics only shows the frame.
Does not keep working time records by camera
We do not offer clock-in and clock-out marks from video surveillance cameras without the employee’s participation. For time tracking there is a separate scenario with the employee’s consent — time and attendance by face.
Video analytics is useful as long as employees, customers and lawyers trust it. That is why the system has boundaries that cannot be configured away.
Access to events, the archive and face images is separated by roles: the occupational safety engineer sees their zones, the guards — their cameras. How to protect biometrics in your own systems — in the article “How to ensure the protection of personal and biometric data in KYC processes”.
Three groups of rules matter for video analytics at work and in a sales area: the Labour Code on occupational safety and video recording, 152‑FZ on personal data and the restrictions of 572‑FZ for face recognition. Below is a summary of the rules as of October 2026: a guide for a conversation with a lawyer, not a legal opinion.
Where there are more cameras than people able to watch them.
NeuroVision provides the analytics and the API. Cameras, the video server and installation are yours or your integrator's. We choose the camera requirements for the task and check them in the pilot: they differ for overview scenarios and for face recognition.
Cameras already installed, with a video stream over the network, are suitable; we check compatibility and the minimum requirements in the pilot. Face recognition needs a camera that sees the face large and frontally — the face size and the turn angle can be limited in the source settings.
The analytics works alongside your video surveillance system. How exactly to receive video and return events — to the account, via the API or to your system — we determine at connection; changing the video surveillance system is usually not necessary.
Recordings from past days are uploaded as files — they are used to search for events and check how the analytics works even before live cameras are connected.
Connection on site is done by your integrator or a NeuroVision partner: they know the cameras and the site network, and we provide the API and help to configure the rules. For partners and integrators
We start with a pilot: we connect a few cameras or an archive, configure the rules and look at the events together. What of this is available via the API, we clarify for your project.
A 1 month test, support under the contract, payment per check.
Video analytics can be bought for a task: the price depends on the number of cameras, the scenarios and the connection scheme. You can start with a free pilot.
A few cameras or an archive, one or two scenarios, setting up zones and rules, reviewing events together with your service.
on request
Matching faces in video and in the archive against lists of people who have given consent, alerts on a match and access roles.
on request
We determine the number of cameras, the scenarios and the connection scheme together after the pilot. The terms are tailored to your site.
Cameras, the video server and installation are not included in the price. Prices for online document and face checks are in the price matrix; it does not include video analytics — we calculate the cost for the project.
Terms you will meet in the project, in the contract with the integrator and in a conversation with the occupational safety service.
The project «Development of a multimodal system using artificial intelligence "Neuromed" for managing the diagnostic processes of a clinic on the basis of the "Neurovision" computer vision platform» is supported by the Innovation Promotion Foundation within the federal project «Domestic Solutions»
The Neurovision computer vision platform is registered with Rospatent (certificate No. 2023661508) and included in the Russian Software Registry (entry No. 19972 of 13.11.2023)
The right to use the Platform is granted under a licence agreement concluded by Neurovision with its customers
Tell us what the tasks are and how many cameras, whether you have a video surveillance system and an archive — we will propose scenarios and a pilot on your recordings.
Can't put your request into words? Book a call and our team will contact you at a convenient time
Book a callThe company is included in the register of IT companies and the register of personal data operators of the Russian Ministry of Digital Development.
Address: Moscow, Presnenskaya Embankment 12 — Moscow City business centre, Federation Tower. Nearest metro stations: Delovoy Tsentr and Mezhdunarodnaya.
Materials on face recognition, algorithm accuracy and protection against deepfakes — in our blog.
Video surveillance records video, video analytics analyses it. A neural network works with the video from cameras and the archive and flags events by your rules, and matches faces against lists. The operator does not need to watch all the screens — they receive an alert and a frame.
Most often not, but it depends on the task. We work with the video from your cameras and with archive recordings; we check compatibility and requirements in the pilot. Face recognition needs a camera that sees the face large — we choose it for the location.
Zones where a hard hat, vest or goggles are mandatory are marked on the frame, and a rule is set. If the violation lasts for the set time, the responsible person receives the event with a frame and a time. The system does not determine who broke the rule. We clarify the capabilities for each type of PPE in the pilot.
No. Visitor counting by video analytics is anonymised: the report holds numbers, queues and time in zones, gender and age group — without faces and without matching against a database.
This is a scenario we discuss for the project: write which entrances and plate formats you need — we will answer what is available now and what can be checked in the pilot. How long to keep the entry log is determined by your local regulation.
Yes, but only against your lists of people who have given written consent — employees, guests, loyalty programme customers. The source can be a camera, a photo or an archive video. The system cannot recognise everyone and will not; your lawyer checks a scheme with face recognition before launch.
Yes, this is a separate scenario — access control with face recognition: a camera at the checkpoint, access lists, consent and a card for those who have refused biometrics. More on the page face-recognition access control.
To monitor the safety of work operations the employer may use remote video recording (Art. 214.2 of the Labour Code of the Russian Federation); the purposes and procedure are set out in a local regulation, and employees are made familiar with it against signature. If faces are matched against a list, however, that is biometrics and written consent is needed (Art. 11 of 152‑FZ).
We do not offer time tracking by video surveillance cameras without the employee's participation. There is a separate scenario for that — time and attendance by face at a terminal, with the employee's consent.
The first month of a pilot on your cameras or archive is free. After that we calculate the cost for the project: by the number of cameras and scenarios. Cameras, the video server and installation are separate, with you or your integrator.