Smart City Cockpit for UAE Municipalities — ICCC + VMS + EMS + Visual Bot

Yes. VMukti deploys into AWS UAE (me-central-1, Dubai) or Microsoft Azure UAE North (Dubai) / UAE Central (Abu Dhabi) for customers whose data residency policy mandates in-country processing and storage. The Decree-Law 45/2021 (UAE PDPL) data-flow map is included in the customer onboarding pack, and cross-border transfers are disabled unless the controller authorises them in writing with a documented adequacy basis or explicit consent.

Yes. Visual Bot, VMukti's natural-language interface for surveillance, accepts queries in Modern Standard Arabic and Gulf-dialect Arabic and renders the operator UI right-to-left. Common Arabic operator phrasings ("ابحث عن سيارة بيضاء", "أظهر التنبيهات في المنطقة 3") map to the same query graph as their English equivalents, with named-entity recognition tuned for UAE place names, MOI structures, and Arabic vehicle plates. English/Arabic toggle persists per operator profile.

VMukti exposes a REST/event API and a webhook plane that integrate with Dubai Smart Government services (Dubai Now, DubaiPolice, RTA traffic ops) and with TDRA-regulated identity flows (UAE Pass for operator SSO). Common integration patterns include: incident push from VMukti to the Dubai Now incident inbox; ANPR plate cross-check against RTA registration data; and TDRA-compliant retention reporting. For Abu Dhabi the equivalent integrations target the Tamm platform and ADP traffic operations.

Yes. VMukti is ONVIF Profile S/G/T compliant and onboards heterogeneous fleets — Hikvision, Dahua, Axis, Hanwha, Bosch, FLIR, and local Make-in-UAE OEMs — into a single pane of glass. Most UAE municipalities have multi-vendor histories, so the typical rollout pattern is to deploy VMukti as the upgrade layer on top of the existing camera estate, then phase camera replacements over 2–3 budget cycles rather than as a forklift project. This is the same "upgrade-layer, not rip-replace" architecture used in our Saudi Vision 2030 deployments.

A standard four-layer cockpit (ICCC + VMS + EMS + Visual Bot) for a UAE municipality lands inside 90 days when the camera estate already exists: weeks 1–2 for tenant provisioning, in-country cloud setup and identity federation; weeks 3–6 for camera onboarding, role design and operator training; weeks 7–10 for analytics tuning, integration with municipal services and SOC handover; weeks 11–13 for an operator-attended PoV and acceptance. New-build city deployments (NEOM-class) extend this by the time required for the camera estate itself to be physically installed.

Yes. VMukti deployments in the UAE are scoped against the UAE National Cybersecurity Strategy controls (network segmentation, MFA, audit logging, encryption at rest and in transit) and TDRA's IoT Regulatory Policy where the camera estate qualifies as an IoT deployment. ISO 27001:2022 is the underlying certification, supplemented by the deployment-specific risk register. For Critical Information Infrastructure (CII) workloads, the deployment topology is reviewed with the customer's appointed CISO ahead of go-live.