E-Gate Integration
E-gate integration for any airport, any gate.
ECGate is the software layer between your e-gates and your airport systems. Keep the gates you have, connect them to your AODB, DCS and biometric engine, and run them from one place.
The integration problem at most airports
Gates come from one manufacturer, the biometric engine from another, and the departure control system from a third. Each speaks its own protocol. Without a layer in between, every new gate, engine or airline system means another custom project.
ECGate is that layer. It is vendor-agnostic and configured for each airport, so the gates you already own work with the systems you already run.
- Boarding gates, pre-security and terminal entry gates
- Gates from any manufacturer, old or new
- Any biometric engine, including NEC, Paravision and Aware
- AODB and DCS connections
- Live passenger counts from every connected gate
How it connects
From gate controller to airport system
ECGate translates the industrial protocols gate hardware uses into the modern interfaces airport software expects, in both directions.
Gate side
Modbus, CANbus, serial and manufacturer SDKs. Flap control, sensor events and scanner input from each lane.
Airport side
REST, SOAP, WebSockets and TCP/IP to your AODB, DCS, airline systems and biometric engine.
Validation in between
Every boarding pass is checked against live flight data and its passage history before the gate opens, so a reused pass is stopped at the lane.
Rollout
How an e-gate integration project runs
1. Survey
We document your gate hardware, protocols, biometric engine and the airport systems the gates need to reach.
2. Connect
We configure ECGate connectors for your gates and systems. No gate hardware replacement.
3. Test
Lane-by-lane testing with real boarding passes, rejected passes and failure scenarios before go-live.
4. Operate
Go live with monitoring and 24/7 support, then add gates, checkpoints or modules as you grow.
50+
Gates deployed across partner airports
1M+
Passengers processed on our platform
3s
To clear each passenger through a biometric gate
73%
Of travellers prefer biometrics over documents
E-gate integration questions
Do we need to replace our existing e-gates?
No. ECGate is hardware-agnostic and connects to the gates you already have, whichever company made them.
Which biometric engines do you support?
We have integrated NEC NeoFace, Paravision, Luxand, Aware, DeepFace and proprietary engines. See Biometric Identity.
Can it connect to our AODB and DCS?
Yes. ECGate connects through REST, SOAP, WebSockets or TCP/IP, with custom connectors where a system needs one.
Is it built to aviation standards?
ECGate is built to IATA and ICAO standards, with encrypted connections, token-based authentication and role-based access.
The platform