Use Cases
Three deployment shapes cover most projects: gates that verify and physically control passage, corridors that identify people without stopping them, and the combination of both. All three run on the same platform and publish through the same integration surface — the difference is what stands in the traveler's way.
Automated Border Crossing
A land border, airport, or seaport replaces part of its manual booths with biometric e-gates. Travelers approach the gate, are captured and liveness-checked automatically, and are verified 1:N against central biometric databases or watchlists — with 1:1 verification against the passport photograph or a digital credential as the fallback. Most travelers clear on facial identification alone; the gate escalates to additional modalities only when confidence or policy demands it.
Who is involved
The border authority operates the deployment and owns the traveler data; a gate manufacturer or system integrator supplies the physical gates and integrates the Innovatrics biometric components; officers monitor passages and handle escalations from a central console. Innovatrics delivers the biometric software: capture, liveness, matching, and the event stream that drives the gate logic.
How the pieces map
Each gate (or group of gates) runs as a unit of a Smart Corridor node. The gate controller consumes clearance events from the Hub's /graphql endpoint (see Gate Hardware Integration); officer monitoring runs on the bundled Operational Interface. Central watchlists are provisioned from the Border Control Platform or the authority's own systems.
Why this shape
The gate remains the legal control point — the decision to open belongs to the border authority's rules, not to the biometric layer. That separation lets the authority tune security policy (thresholds, escalation, fallback) without touching gate hardware, and lets the integrator swap or extend hardware without re-integrating biometrics.
Seamless Transit Corridor
An airport wants arriving or transferring passengers to be identified without stopping — no booth, no gate, no document presentation. Cameras along a walking corridor capture faces at walking pace, match them 1:N against pre-enrolled travelers, and publish the outcome before the passenger reaches the end of the passage. Throughput is the design goal: the corridor processes a continuous flow of people rather than a queue.
Who is involved
The airport operator or border authority runs the corridor; passengers pre-enroll through a registration channel (for example at check-in, a kiosk, or a mobile app); officers watch a live feed of identifications, unknown persons, and avoidance behavior on the Officer Monitoring App, including the flights feed that tracks per-flight processing progress. Travelers get live guidance from the Traveler Display.
How the pieces map
The corridor is one or more units of a Smart Corridor node (TYPE=CORRIDOR): multiple cameras feed VPP, CIGS groups detections into one anonymous identity per traveler, and CBS adds zone events — entries, exits, counts, occupancy violations, and identification avoidance. Downstream systems subscribe to the event stream and route passengers accordingly.
Why this shape
Because identification is passive, the traveler experience is the corridor itself — no interaction to learn, nothing to present. The trade-off is that the corridor observes and reports rather than physically blocking anyone; it pairs naturally with a decision point downstream, which is exactly the hybrid layout below.
Hybrid Corridor + Gate
The two form factors combine: a corridor identifies travelers while they walk, and an e-gate at the end of the passage acts on the result. Travelers identified with high confidence in the approach corridor reach a gate that is already prepared to open; travelers the corridor could not identify are diverted to the gate's own capture-and-verify flow or to a manual booth. The corridor does the work early so the control point stops almost nobody.
Who is involved
The same actors as in the individual scenarios — border authority, gate vendor or integrator, officers — but the value shifts to the operator of a high-traffic checkpoint who needs both legal control (a physical barrier) and throughput (no queue forming at that barrier). This is the typical shape for busy airport immigration halls.
How the pieces map
Corridor and gate are units of the same Smart Corridor node — both form factors share the same platform and event model, differing only in unit configuration (TYPE=CORRIDOR vs TYPE=EGATE). The gate logic correlates corridor identification events with the person arriving at the gate. One officer console covers both.
Why this shape
Identification takes time — capturing a good frame, matching, escalating if needed. Doing it during the walk converts dead time into processing time, so gate dwell drops toward zero for cleared travelers while unknown or flagged persons still meet a hard control point. It also degrades gracefully: if the corridor is bypassed or crowded, the gate simply falls back to standalone verification.