ICCC Platform for Saudi Vision 2030 — Mega-Projects, City Ops, Critical Infrastructure

Yes. The VMukti operator console, Visual Bot natural-language interface, and forensic search support Modern Standard Arabic and Saudi-dialect Arabic with a right-to-left UI. Place-name recognition is tuned for Saudi cities, MOI districts, and Hajj/Umrah landmarks; vehicle plate recognition reads Arabic-numeral and Latin-numeral KSA plate formats. Operators can switch between English and Arabic per session, and shift handovers carry over query history regardless of the language each operator chose.

Yes. VMukti deployments in Saudi Arabia are scoped against the Saudi Personal Data Protection Law (PDPL) and the SDAIA implementing regulations: legitimate-basis discipline, in-country processing on SAR1/SAR2 cloud regions (AWS Riyadh me-south-1, Microsoft Azure Saudi Arabia, Google Cloud Dammam), role-based access default, encryption at rest and in transit, and a retention schedule mapped to each lawful basis. The vendor attestation and data-flow map ship with the onboarding pack so a Saudi controller can include them in their SDAIA registration file.

Yes. The ICCC exposes a documented REST/event API and an MQTT bridge that integrate with existing Saudi traffic management platforms (Saher / Riyadh ITS), MOI command-and-control feeds, and major-event operations centres used for Hajj and Umrah. VMukti is deployed as an upgrade layer rather than a replacement: the existing camera estate, ANPR feeds, and incident queues continue to operate; the ICCC normalises them into a single pane of glass with Arabic-first operator UX and Visual Bot search.

Vision 2030 targets a doubled population in Riyadh, NEOM's greenfield smart-city build, the Red Sea Project, Diriyah regeneration, and a step-change in pilgrim throughput at Hajj and Umrah. Each of these programmes needs an ICCC layer that integrates legacy and greenfield cameras, scales to giga-project size, and complies with the Saudi PDPL. VMukti's contribution is the upgrade-layer ICCC plus an Arabic-first operator experience: deploy on a zone, prove operator efficiency, then expand to district and region. This Land → Expand pattern is how we are scoping Vision 2030 deployments today.

Yes. VMukti has run live operations at the scale Saudi giga-projects require: 23,000+ camera locations in a single national programme, 100,000+ concurrent streams in peak windows, and crowd-density analytics tuned for >1M-person events. Hajj-style deployments add three concerns the standard ICCC handles: pilgrim-flow density and stampede risk, multilingual signage and operator language mix, and surge capacity that quadruples in the 10-day operational window and reverts after. The cloud-edge hybrid topology means surge capacity is rented for the window, not capitalised for the year.

A typical Vision 2030 engagement starts with a single zone (a district, a transport corridor, or a pilot venue) where VMukti proves the four-layer cockpit on the customer's real camera estate. After acceptance, the deployment expands to the surrounding district (multi-zone aggregation, district-level Visual Bot, district KPI dashboards), and from district to region (regional-command tier, cross-district correlation, regional SOC integration). Pricing and licensing scale on the same model so the customer never repurchases what they have already deployed.