Vengeea deploys on-premises AI video analytics at critical facilities across Turkey (Istanbul, Ankara, Izmir and industrial regions) — 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 fits KVKK's data-localisation leanings by architecture rather than by policy.
Vengeea runs on the customer's own infrastructure inside Turkey, so video and any biometric face-match templates are processed and stored on-site rather than sent abroad — which sidesteps cross-border transfer requirements under KVKK entirely, rather than satisfying them through a transfer mechanism after the fact. That matters most for face recognition: biometric processing sits under KVKK's Article 6 special-category rules, and matching against an on-prem watchlist keeps the deployment out of the cross-border-transfer conversation that a cloud biometric vendor would force. Configurable retention, role-based access and audit logs support the express-consent and DPIA expectations the Turkish Data Protection Authority (KVKK Kurumu) looks for.
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 pipeline that would require its own data-localisation review. Below are the four modules Turkish port and industrial operators request most.
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 weapon detection — firearm and edged-weapon detection in live video.
AI fire and smoke detection — early-stage smoke and open-flame detection in halls and outdoor areas.
Ports (Aliağa, Ambarlı, Mersin), oil and gas terminals, industrial zones (OIZs), logistics distribution centres, retail chains, and public-sector critical infrastructure — sectors where a security or compliance director has to answer to KVKK's data-localisation expectations for every camera on the perimeter, not just the ones facing the public.
Yes. Vengeea is deployed at critical facilities across Turkey 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 stays inside the customer's own network, which aligns with KVKK's requirements on cross-border transfer of personal and biometric data without the transfer question arising in the first place.
Yes. Vengeea acts as data-processor with the customer as controller (veri sorumlusu). Because processing happens on-premises, there is no cross-border transfer of personal data by default — which matters given KVKK's data-localisation leanings and the extra scrutiny cross-border transfer of biometric data draws under the law. Retention, deletion and access logs are configured per site to fit the customer's KVKK obligations.
Any camera that outputs RTSP or ONVIF — Hikvision, Dahua, Axis, Bosch, Uniview, Milesight and Hanwha are all supported without hardware changes. Integration is typically complete in 1-3 days from kickoff.
Yes. Vengeea's per-site appliance model fits OIZ and port deployments where each tenant or terminal expects network isolation and processes its own camera feeds locally, rather than backhauling video to a shared or foreign data center. Multi-site aggregation is optional.
1–3 day integration. No hardware replacement. On-prem by default.
