Cities under coverage
5active programs
Urban AI for the Kingdom's next decade — NEOM, Diriyah, Qiddiya, ROSHN, and the heritage capitals. We build the data fabric, the operations centers, and the citizen-facing services that make a city feel intelligent, not just instrumented.
Six pressures we hear from giga-project CTOs, RCRC programme leads, and municipality CIOs on every first call.
NEOM, Diriyah, Qiddiya, and ROSHN are committing to operating models that don't exist yet. Software has to land before the buildings do — every quarter slips a city by a quarter.
Riyadh summers, pilgrim peaks, and giga-project commuting patterns push transit to its limits. Predictive routing, signal control, and parking guidance are not nice-to-haves — they are the throughput.
Net-zero ambitions land in the metering, the HVAC, the irrigation, and the waste pickup. Without an analytics fabric tying meters to operations, the targets remain slogans.
Every interaction with the city has to work in Arabic and English at parity. Dialect, code-switching, and accessibility for elderly Saudis and expatriate residents are first-class requirements.
Cities run on fused operating pictures, not 14 dashboards. Traffic, security, utilities, and citizen channels collapse into one C2 surface or the operators ignore the screens.
Sensor, video, mobility, and citizen-service data is sensitive under PDPL and the NDMO classification framework. The fabric has to stay in-Kingdom, accredited, and auditable end-to-end.
Six disciplines, sector-tuned around the giga-project operating model and the realities of running a Saudi municipality.
Traffic, parking, incident detection, and crowd flow on edge devices across thousands of streetlamp cameras. On-device inference; PDPL-compliant retention.
Bilingual conversational assistant for permits, complaints, services, and wayfinding — surfaced inside the existing city app, not a new one.
15-minute-horizon forecasts for transit load, signal optimisation, and event surge, feeding the operations center and the third-party mobility platforms.
In-Kingdom landing zone with edge POPs across the giga-project sites, engineered for sensor density and zero-downtime maintenance windows.
Managed detection-and-response tuned to the urban threat surface — ICS, CCTV, smart-meter, and citizen-app channels. NCA-aligned by default.
Common operating picture across traffic, security, utilities, and emergency response — designed for the operations director, not the dashboard vendor.
Two engagements that anchor the practice. Names redacted under MNDA — the operators know the work.
A fused-vision and signal-control fabric across 1,200 intersections producing 15-minute load forecasts and signal recommendations to the city's operations director. Wired into RCRC's operations program.
An agentic Arabic-first assistant inside the resident app, handling permits, complaints, wayfinding, and service requests. Plugs into the existing service catalog so we extend rather than replace.
Authorities, sovereign infrastructure, and the operating partners we integrate with across the giga-project landscape.
In-Kingdom by default. Sensor, video, and citizen data lands in sovereign cloud or operator-owned edge — never in a foreign region. We deploy under PDPL and the NDMO classification framework on day one, not as a retrofit.
No. We extend — by SDK, by API, and by event bus. Cities have already invested in dashboards, ITS, and resident apps; we add intelligence on top of those investments rather than asking the operator to switch tools.
A multi-year master plan, but quarterly capability releases. Each release is a single, useful operating model — congestion forecasting, citizen copilot, incident triage — that the city can adopt independently.
Computer vision runs at the edge. We extract counts, density, and incident signals — not identities. Faces are not retained by policy. Privacy posture is written, not implied, on every deployment.
We supply analytics and decisions; the operations center keeps its console. Integration is by event-bus, REST, and SDK, not by displacing the existing C2 vendor.
Onshore Saudi team, multi-year mission programs, quarterly steering with the operator's CTO and operations director. We staff a permanent cell at the city's operations facility during peak rollout windows.
Sixty-minute working session with our Smart City lead and a mobility engineer. Bring the corridor, the giga-project, or the citizen-service backlog. We'll come back with a one-page operating-model proposal you can take to the steering committee.