Smart Corridor Services
These manuals describe each corridor service in detail. For first steps, see Getting Started; for tasks that span several services, see the guides.
A Smart Corridor stack is Face Matcher plus the corridor services built on top of it: the Smart Corridor & eGate Hub — the central system and the corridor's external surface — and the source systems that feed it. All of them ship and start together from one deployment package. 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 through one GraphQL endpoint. It contains the GraphQL API (live subscriptions and data queries), the DbWorker Service (event persistence and retention), the two source-system adapters, and a planned REST API.
Source systems
| Component | Role | Connection |
|---|---|---|
| Face Matcher | 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 across cameras (optional overlay) | Via CBS |
The VPP Adapter and CIGS Adapter are Hub components 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. Face Matcher is a separately documented product: the corridor vendors it and depends on it through its integration list only.
Camera inputs
Cameras feed Face Matcher, not the corridor services, and are the physical entry point of the recognition chain. Both server-side RTSP processing with classic IP cameras and edge streams from smart cameras or AI boxes are supported — see Cameras and Choosing a camera. The corridor's part is only the camera-to-unit mapping described in Add Cameras.
Operational interface
The stack also ships the corridor dashboard on port 8095, built on the Hub's GraphQL API — the Officer Monitoring App and the Traveler Display. They require nothing beyond reachability of the /graphql endpoint.