Gate Hardware Integration

Innovatrics provides the biometric software components of the e-gate — the physical gate, barriers, sensors, and mechanical parts come from the gate manufacturer or system integrator. This split is deliberate: the platform observes, identifies, and reports, while the actual open/close decision and actuation belong to the gate control system that owns the hardware.

Driving a gate from clearance events

The integration pattern is event-driven: the gate controller (or the integrator's middleware) subscribes to the Hub's /graphql endpoint and reacts to clearance outcomes. A identification.clearance.green event for the gate's unit means the traveler may pass; identification.clearance.red or identification.no_match means the gate stays closed and the case escalates to an officer. The unitId on every event ties it to the specific gate or corridor unit, so one Hub node can serve several lanes without ambiguity. See Consuming Events for working subscription examples.

Peripherals and project-specific devices

Gates often carry additional peripherals — document readers, fingerprint or iris sensors, indicator lights, intercoms. Known peripherals are supported through the standard delivery; unknown ones are integrated upon request and confirmed during project preparation. Raise peripheral requirements early in the project phase so compatibility is validated before hardware is procured.

What to agree with the gate vendor

Three things need to be settled between you, the gate vendor, and Innovatrics: where the biometric capture device sits on the gate (camera position and lighting drive recognition quality — see Choosing a camera), which system makes the final passage decision and on what timeout, and how fallback works when biometrics cannot decide (officer intervention, document-based 1:1 check). The Biometric E-Gates page describes the adaptive verification flow these decisions plug into.