Recording instead of intervening
Traditional systems capture what happened. You find the useful footage after the incident, not during it.
The damage is done before anyone looks.
VICAMOS sees what is happening on your site, understands the situation, responds according to your rules and documents every event. Without needing someone sitting at the other end of the line.
Pilots start at a single camera. No monitoring-centre lock-in.
The cameras got better. The operating model behind them did not: camera, monitoring centre, human, phone call, manual response.
Traditional systems capture what happened. You find the useful footage after the incident, not during it.
The damage is done before anyone looks.
Someone in the monitoring centre has to detect, understand, decide and react. Each of those four steps costs time.
Cost per alert, delay per alert, uncertainty per alert.
With managed security services the provider runs the workflow. You request footage instead of having it.
You are a customer of your own security system.
Tower, mast, solar array, battery bank. Often not because the site demands it, but because the camera system does.
Weeks of lead time for an area that needs one camera.
Live view here, alerts there, an incident report by email, hardware with a third party. A clean history exists nowhere.
Nobody can say what happened on site yesterday.
A security system generates enormous amounts of footage and almost no usable management information.
Hours of recording, nothing you can act on.
Both systems see the same incident. The difference starts in the second that follows: one files a video and waits for a person to open it. The other works out what is happening, intervenes, and writes the record itself.
Some providers do run a staffed control room with a full video wall, live feeds around the clock. Attention simply does not scale: two people cannot watch every tile, every corner and every frame at once. After an hour of a wall full of yards where nothing happens, the eye stops finding the one tile that matters — and every false alarm trains attention further away from it. Whether anyone responds comes down to whether someone was looking at the right image at the right moment. The report gets written afterwards, by hand.
The response depends on someone looking at the right moment.
VICAMOS analyses every frame on the camera itself — on every camera at once, as precisely in the twelfth hour as in the first. It identifies who or what is moving there and checks it against the rules you set for that zone at that time of day. If it does not fit, the response starts immediately: an announcement over the speaker, lighting, an alert to your on-call staff. Escalation goes only as far as you have approved. What is left at the end is a finished incident record nobody had to type.
The response starts the moment the event does.
None of this is technology for its own sake. It moves the moment something happens from “after the incident” to “during the incident” — and takes the paperwork off your desk.
Four steps that run without anyone intervening. You set the rules for them, not us.
Not: call us if you need footage.
Instead: log in and look.
Log in from any browser. Every site, every camera, one picture.
Authorised employees carry the entire security system in their pocket.
Management, site managers, security staff, employees, contractors. Each with their own access.
One camera or five hundred. One facility or a whole portfolio. One interface.
Every morning VICAMOS generates an automatic security summary of the previous day. You wake up knowing what happened.
One document you can file, forward and present.
Sent automatically to the distribution lists you define.
Every report stays searchable inside the system.
Not just security. A verifiable record of what happened on your site.
The difference is not the camera. It is what happens after detection, and who decides it.
| Traditional video security | VICAMOS |
|---|---|
| 01Records incidents | Responds to incidents |
| 02Motion alerts | Context-aware AI events |
| 03Monitoring-centre centric | Customer centric |
| 04A human checks every alert | Automation handles the routine case |
| 05Manual escalation | Configurable escalation ladder |
| 06Separate live monitoring | Complete browser dashboard |
| 07Limited mobile access | Complete mobile access |
| 08Manual incident reports | Automatic event documentation |
| 09Hours of footage | Daily security summary |
| 10Vendor-side configuration | Customer-side policies |
| 11Closed system | Integrations and an open API |
| 12Compliance as process | Compliance in the software |
No megapixel table. The camera is the prerequisite for the product, not the product itself.
Mounted where the situation occurs, rather than on a mast beside it.
Analysis happens on the camera, not first in a data centre.
Detection at the hours when most incidents actually happen.
Direct address on site instead of silent recording only.
Visible deterrence as its own rung of the response ladder.
Object classes separated directly on the device.
Access to live and recorded footage without open ports on site.
Zones, rules and software are maintained from the cockpit.
Failures, offline time and recording status report themselves.
No oversized tower where a compact camera will do. Infrastructure because the site needs it, not because the camera system requires it.
An event is a record. It belongs where your processes already run.
Retrieve events, cameras, sites and incidents programmatically.
Deliver every event in real time to a system of your choice.
Wire existing intrusion detection in as a trigger or a receiver.
Reconcile detected behaviour against authorised entry.
If you use a security provider, they stay in the loop.
Push alerts into ticketing, messaging and management tools.
VICAMOS is a platform, not another isolated camera app.
Not a GDPR badge in the footer, but concrete controls the software actually enforces.
Neighbouring properties, public paths, windows and sensitive areas are permanently masked.
Configurable per recording and event type, rather than one blanket rule for everything.
For every camera and monitored area, why it exists is documented.
Not everyone with the app needs access to every camera.
Who signed in, viewed footage, exported it or changed the rules.
The retention period is enforced by software, not by a calendar reminder.
German federal data protection law ties video surveillance to a defined purpose and to necessity, requires that surveillance be made known, and requires deletion once footage is no longer necessary. Those three points are configuration in VICAMOS rather than process.
The application guideline for video surveillance systems in security applications. We align the design and documentation of installations with this standard.
TODO(cert) — certifying body, certificate number and scope will be named here once they exist.
We do not write "TÜV compliant". Specific certificates will be named with the certifying body, number and scope once they exist. This section describes the controls the software provides today.
VICAMOS is not a construction camera. Construction sites are one of many deployments.
A changing risk profile, high material value, no fixed infrastructure.
Large areas with clearly separated restricted and operating zones.
Few entrances, high inventory value, defined operating hours.
Constant vehicle traffic in which the one wrong vehicle has to stand out.
Concentrated value on a small footprint, often with nobody present.
Remote, sprawling and economically attractive to steal from.
Multiple tenants, different access rights, shared areas.
No use, no witnesses, high downstream cost from vandalism.
Publicly accessible, with strict requirements around privacy zones.
Set up in hours rather than weeks, removed without a deconstruction project.
You are not buying eight security products and making them work together.
Hardware with AI processing directly on the device.
Browser-based command centre for every site and camera.
Access for authorised employees on iOS and Android.
Detection and context-aware analysis of events.
Warning, deterrence and escalation according to your rules.
Automatic daily report as PDF, email and archive.
API, webhooks and connections to existing systems.
Privacy zones, retention, permissions and audit logs.
Provisioning, installation, monitoring and maintenance.
Provisioning, installation, monitoring and maintenance are part of it. Pricing is agreed in the pilot conversation, based on site, camera count and response levels.
Request a pilotIf your question is missing, ask it in the pilot conversation. We would rather answer specifically than generally.
One pilot site, real events, your rules. After that you decide on measurements rather than on a brochure.
Pilots start at a single camera. No monitoring-centre lock-in.