Components
The Smart Corridor platform consists of the Smart Corridor & eGate Hub — the central system and the only externally visible surface — and four internal source systems that feed it. All of these ship and deploy together as one bundle. This section documents each component individually.
The Hub
The Smart Corridor & eGate Hub aggregates events from all source systems, normalizes them into a unified event model, and exposes them externally. It is a multi-service repository containing the GraphQL API (live subscriptions and data queries), the DbWorker Service (event persistence and retention), and a planned REST API.
Source systems
| Component | Role | Connection |
|---|---|---|
| VPP | Face detection, recognition, and watchlist matching | Via VPP Adapter |
| CIGS | Groups face detections into anonymous identities | Via CIGS Adapter |
| CBS | Zone behavioral events | Direct to message broker |
| MCT | Physical movement tracking (planned) | Via CBS |
The VPP Adapter and CIGS Adapter live in the Hub repository and are responsible only for translation and routing — they contain no business logic. CBS acts as both source system and its own adapter, publishing directly to the broker.
Camera inputs
The Cameras feeding VPP are the physical entry point of the recognition chain. Smart Corridors supports two source types — server-side RTSP processing with classic IP cameras, and on-edge processing with smart cameras or AI boxes. See the Cameras pages for how each source type works and for guidance on choosing hardware.
Operational interface
The bundle also ships two UI clients built on the Hub's GraphQL API — the Officer Monitoring App and the Traveler Display. They are part of the node deployment and require nothing beyond reachability of the /graphql endpoint.