Vengeea deploys on-premises AI video analytics at critical facilities across Turkey (Istanbul, Ankara, Izmir and industrial regions) — intrusion, weapon, fire, leak and LPR detection on existing IP cameras. KVKK-aligned by architecture.
Vengeea runs on the customer's infrastructure inside Turkey, which sidesteps cross-border transfer requirements under KVKK. Biometric processing (face recognition) sits under KVKK's Article 6 special-category rules; Vengeea's configurable retention, role-based access and audit logs support the express-consent and DPIA expectations of the Turkish Data Protection Authority (KVKK).
Modules run in parallel on the same appliance and the same cameras. Below are the four most-requested in Turkey deployments.
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.
Yes. Vengeea is deployed at critical facilities across Turkey under the on-premises model. Video stays inside the customer's own network, aligned with KVKK's requirements on cross-border transfer of personal and biometric data.
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. 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.
Yes. Vengeea's per-site appliance model fits industrial-zone and port deployments where multi-site aggregation is optional and network isolation is expected.
1–3 day integration. No hardware replacement. On-prem by default.
