Vengeea deploys on-premises AI video analytics at critical facilities across the EU/EEA — intrusion, weapon, face, fire/smoke and license-plate detection running live on the IP cameras already installed at each site, with theft and liquid-leak modules in active development. Video and biometric processing stay inside the member state where the site sits; there's no cross-border transfer to justify because the data never crosses a border in the first place.
Vengeea runs on the customer's own infrastructure, so inference happens on-site and video or biometric templates never leave the facility to be processed abroad — which is what sidesteps SCC and transfer-impact-assessment requirements entirely, rather than satisfying them after the fact. That matters most for face recognition: under GDPR Article 9, biometric identifiers are special-category data, and an on-device match against a locally-held watchlist is a materially different risk profile than shipping facial templates to a third-country cloud. Retention, deletion and role-based access are configured per deployment to fit the AI Act's classification of the specific use case — the customer stays controller and the DPO stays in the loop throughout, not brought in after a vendor contract is already signed.
All modules run in parallel on the same appliance, reading the same RTSP streams the site's cameras already output — no additional hardware, no camera swap, no separate biometric pipeline to secure. Below are the four modules requested most often across EU/EEA deployments, each live and generally available today.
AI intrusion detection — restricted-zone entry, line-crossing, after-hours access on existing IP cameras.
AI weapon detection — firearm and edged-weapon detection in live video.
AI face analytics — watchlist matching against an on-prem face database.
AI fire and smoke detection — early-stage smoke and open-flame detection in halls and outdoor areas.
Ports, industrial and chemical plants, energy and utility substations, transport hubs, healthcare-adjacent facilities and public-sector critical infrastructure across the EU/EEA — sectors where a security or compliance director has to be able to show a regulator, an auditor or an insurer exactly where surveillance data lives, and "it never left the site" is the simplest answer available.
Yes. Vengeea is deployed at critical facilities in multiple EU member states under the on-premises model, running on the existing IP cameras already installed at each site. Because inference happens on the customer's own server, video and biometric data stay inside the customer's own facility, which sidesteps SCC / transfer-impact-assessment requirements — there's no international data flow to justify in the first place.
Yes. Because processing happens on the customer's infrastructure, Vengeea is deployed as a data-processor with no cross-border transfer by default — the compliance question a cloud biometric vendor forces onto every deployment (which country the data lands in, which SCCs apply, which sub-processors are in the chain) simply doesn't arise. Retention, deletion, access logs and role-based access are configurable per site to fit the customer's DPIA.
Face-recognition is deployed as a watchlist-matching module against an on-prem face database, with configurable retention and role-based access to fit the specific use case's classification under the AI Act. Non-biometric modules — intrusion, weapon, fire/smoke and LPR are live today, with theft, liquid-leak and aggression detection in active development — sit outside the biometric-identification scope entirely and can be deployed alongside face recognition or on their own.
Yes. Vengeea deploys via a network of security integrators across the EU/EEA, each familiar with the member state's specific data-protection authority and its expectations for video and biometric processing. Contact sales for the nearest partner for your country and industry.
1–3 day integration. No hardware replacement. On-prem by default.
