Every CityIntegrator module runs on one platform: one data model, one licence server, one operations console. That is the single most consequential design decision in the product, and it is what makes phased city deployments viable.
The shared data model
Sites, lanes, devices, vehicles and people are defined once. When a parking deployment is later extended with traffic enforcement, the second module inherits the site topology and vehicle history rather than building its own. This is why "add a module" is a licensing decision rather than a re-platforming project.
Architecture
- Edge — cameras, sensors, controllers and the recognition/analytics engines that process streams close to them.
- Platform — the server layer that stores events, evaluates rules and exposes the API.
- Applications — parking, enforcement, access control, attendance and the dashboard, all reading the same event store.
- Integration — REST, signed webhooks and MQTT outward to the systems a city already runs.
Deployment options
On-premises and private cloud are both supported. Government and defence sites typically run fully on-premises with no external dependency; commercial sites often run a hybrid with edge processing local and management centralised.
Interfaces
Cameras connect over ONVIF, RTSP or vendor SDKs. Outbound integration is REST and signed webhooks, with MQTT for IoT estates. Directory integration uses Active Directory or LDAP. Verified integrations per product are listed on each product page.
Sizing
We do not publish generic throughput figures, because they are meaningless without the stream list, the models enabled and the hardware. Your integrator sizes each deployment from the actual site survey.