ITKIT
Airport and road gates · 17 / 20
iGates
Automated passport e-gates with officer exceptions
From the problem to how we solve it
October 2026
Interactive prototype · synthetic data only
The problem
Every traveller waits for a desk.
1
At peak hours every traveller waits for a desk officer.
2
Gate logic sits in vendor firmware the authority cannot inspect or change.
3
When a gate is unsure, nobody records who decided and why.
Peak-hour queues · Everyone waits · Even routine travellers · An e-gate lane
ITKIT · iGates · Prototype screens, synthetic data
The problem
Our answer
.NET · Angular · Elsa · Kafka · on-prem
Each passage runs as an Elsa workflow: read the passport, match the face, apply the border authority’s rules, then open the gate or hand the traveller to an officer. Proposed for delivery under a build–operate–transfer contract.
How it works · 1 of 6
Lane 3
Place your passport
At an iGates lane, the traveller places the passport. The chip is read and its signature checked.
ITKIT · iGates · Prototype screens, synthetic data
How it works
How it works · 2 of 6
Document checks
Passive authentication · chip authentication
Every check follows ICAO Doc 9303, and the result is Passed only if every step passes.
ITKIT · iGates · Prototype screens, synthetic data
How it works
How it works · 3 of 6
Face
Face match · liveness
The face is matched with the chip photo and a liveness check guards against masks. Then the image is deleted.
ITKIT · iGates · Prototype screens, synthetic data
How it works
How it works · 4 of 6
Elsa workflow
One Elsa workflow per passage
Behind the lane, each passage is an Elsa workflow the authority can review, test and approve.
ITKIT · iGates · Prototype screens, synthetic data
How it works
How it works · 5 of 6
Pass or refer
Pass, or see an officer
Routine travellers pass in about ten seconds. Anything unsure goes to an officer.
ITKIT · iGates · Prototype screens, synthetic data
How it works
How it works · 6 of 6
Officer decides
The officer decides, with a reason
The officer decides and gives a reason, recorded under her name. The gate never refuses entry.
ITKIT · iGates · Prototype screens, synthetic data
How it works
What it includes
14 screens and workflows in the prototype
Lane: place passport
Arriving travellers with an e-passport
Lane: look at the camera
Travellers in the lane after the passport step
Lane: please see an officer
Travellers the gate could not clear
Officer exception console
Border officers at the arrivals desks
Elsa workflow designer
ITKIT platform engineers and border-authority reviewers
Rules and thresholds
Border-authority approvers and ITKIT engineers
Document check trace
Border supervisors, ITKIT operators and auditors
Biometric performance and PAD
Border-authority approvers, auditors and ITKIT engineers
ITKIT · iGates · Prototype screens, synthetic data
What it includes
Built to standards
International standards it is built to
| Standard | What it covers in iGates |
|---|---|
| ICAO Doc 9303 (8th ed., 2021), Parts 11–12 | Passive authentication |
| ICAO Doc 9303 Part 11 | Chip and active authentication (anti-cloning) |
| ICAO PKD and Doc 9303 Part 12 | Trust store, master lists and CRLs |
| Frontex Best Practice Technical Guidelines for ABC Systems (2015), 4.4 | Overall document result |
| Frontex ABC guidelines (2015), section 5 | Face verification error rates |
| ISO/IEC 30107-3:2023 | Presentation attack detection testing |
| ISO/IEC 19794-5:2011 and ISO/IEC 39794-5:2019 | Face image data format |
| Frontex ABC guidelines (2015), sections 3 and 5.3 | Operator monitoring and manual fallback |
We align with these standards; certification is issued by accredited bodies, not by ITKIT.
ITKIT · iGates · Prototype screens, synthetic data
What it includes
Connects to
What iGates works with
Border control eligibility system
Watch lists (through the border authority)
ICAO PKD mirror
OneID (officer single sign-on)
Airport operations
iBoard (exit record at the aircraft door)
ITKIT · iGates · Prototype screens, synthetic data
What it includes
Safeguards
What iGates will never do
The gate never refuses entry; an officer decides.
Not a border control or watch-list system.
Face images are compared in memory and discarded.
Build–operate–transfer is a proposal; no contract is claimed.
ITKIT · iGates · Prototype screens, synthetic data
Delivery
How delivery works
Start small, prove it, then scale and hand over
6–10 weeks
Assess
Map what already exists and decide, system by system: reuse, integrate, modernise or build.
4–6 months
Pilot
iGates at one authority, with real users and a measured outcome, on national infrastructure.
12–24 months
Scale
Roll out by region and service, sharing identity, integration and audit.
Agreed per contract
Operate and transfer
We run it with your team, train them, then hand over operations, code escrow and keys.
ITKIT · iGates · Prototype screens, synthetic data
Durations are typical ranges, fixed per contract
Next step
Ask for a working session on the iGates workflow and the document-check trace.
Built on .NET, Angular, Elsa, Kafka and PostgreSQL, on-prem. Proposed under build–operate–transfer. Ask us for a working session.
1 · Demo
A guided session on the iGates prototype
2 · Assess
6–10 weeks to map what exists and fix the pilot scope
3 · Pilot
4–6 months with real users and a measured result
ITKIT · [contact name, email and phone]
Thank you