Vengeea deploys on-premises AI video analytics across the Netherlands (including Amsterdam, Rotterdam, and the Randstad) — intrusion, weapon, face, fire/smoke and license-plate detection running live on existing IP cameras, with theft and liquid-leak modules in active development. Because processing happens on the customer's own server, footage never leaves the site, which is the architectural basis for a GDPR and Uitvoeringswet AVG posture the AP recognizes without extra paperwork.
Vengeea runs on the customer's own infrastructure inside the Netherlands, so video and any biometric face-match templates are processed and stored on-site rather than routed abroad. That sidesteps cross-border transfer safeguards under GDPR entirely — there's no SCC to sign, no third-country adequacy question to raise — rather than satisfying them after the fact. It also matters under GDPR Article 9: biometric identifiers are special-category data, and matching against an on-prem watchlist is a lower-risk posture than a cloud face-recognition vendor for the DPIA the Autoriteit Persoonsgegevens (AP) will expect to see. Retention, deletion and role-based access are configurable per site, so the compliance director can document exactly where the data lives.
All modules run in parallel on the same appliance, reading the same RTSP streams the site's cameras already output — no additional hardware, no separate biometric system to secure. Below are the four modules Dutch port and logistics operators request most, each live and generally available today.
AI intrusion detection — restricted-zone entry, line-crossing, after-hours access on existing IP cameras.
License plate recognition (LPR) — whitelist / blacklist alerts at gates and gantries.
AI fire and smoke detection — early-stage smoke and open-flame detection in halls and outdoor areas.
AI face analytics — watchlist matching against an on-prem face database.
Port of Rotterdam and Amsterdam-region terminals, logistics distribution centres, industrial and chemical parks (Chemelot, Botlek), data centres, and public-sector critical infrastructure — high-throughput sites where a compliance director needs a straightforward answer to "where does the video go" for every camera on the perimeter.
Yes. Vengeea is deployed at critical facilities across the Netherlands under the on-premises model, running on the existing IP cameras already installed at each site with no hardware replacement. Because inference happens on the customer's own server, video stays inside the customer's own network rather than a vendor cloud, which aligns with GDPR and the Uitvoeringswet AVG without a cross-border-transfer question to answer.
Yes. Because face-match templates are processed and stored on the customer's own server, they never transit outside the customer's network — a materially lower-risk posture than a cloud biometric vendor under GDPR Article 9, which treats biometric identifiers as special-category data. Configurable retention, deletion and role-based access support the DPIA and controls the AP expects for biometric deployments; face recognition itself is deployed as a restricted, watchlist-based module against an on-prem face database.
Any camera that already outputs an RTSP or ONVIF stream — including brands common in Dutch deployments like Axis, Hikvision, Dahua, Bosch, Milesight and Hanwha. There's no camera replacement or firmware change; integration is typically complete in 1-3 days from kickoff.
Yes. Vengeea deploys at ports and terminal operators at Rotterdam scale. Cluster sizing is done per-site with the Vengeea calculator, and because each site's appliance processes its own camera feeds locally, adding terminals doesn't multiply the amount of video routed off-site. Multi-site aggregation is optional and encrypted end-to-end.
1–3 day integration. No hardware replacement. On-prem by default.
