Identity, verified in under two seconds.

OurVision AI replaces manual ID checks with touchless biometric verification, so passengers move through checkpoints, and the systems behind them seamlessly work.

<2s
to verify identity
6–10s
average walk-through time
0
documents to carry
256-bit
encryption at rest

Built for the two sides of every border

The same platform, configured differently for the authority granting entry and the carrier moving passengers toward it.

For border & immigration authorities

Sovereign control over enrollment, matching, and retention policy
Configurable risk rules and referral workflows per jurisdiction
A single console for biometric, watchlist, and document checks

For airlines & carriers

Open APIs into existing check-in, boarding, and DCS systems
Shared identity data across check-in, security, and the gate
Lower gate dwell time without adding station hardware
Real-world deployment

Built for real terminals, not demos.

The same Vision-Box hardware platform we integrate with runs in terminals worldwide today — from the Caribbean to Dubai, Helsinki, Los Angeles, and beyond. Motorized barriers, multi-camera capture, and a live handshake with the gate — designed to run at the pace an airport actually moves, not the pace of a controlled showroom.

1B+
verifications annually
6–10s
walk-through time
100+
global solutions deployed
Technology partners

Built alongside proven hardware partners

We integrate rather than reinvent — the e-gates and self-service hardware shown above are supplied and supported by our technology partners.

Products
Traveler Verification Service

One look. That's the whole check-in.

A secure gallery of encrypted reference photos is staged the moment someone books or checks in. At the gate, a live camera captures their face, converts it to a biometric template, and matches it in the cloud — no image ever needs to be stored.

No phones, tickets, or physical documents required
Privacy-by-design — tokenized templates, not stored photos
Cloud-based matching, minimal hardware on site
Passenger being verified at a border control booth
Face detected
Liveness · Pass
Pose · Frontal
Match · 99.2%
Live capture
Officer console feed
Live capture
Live capture
Passport photo
Passport photo
99.2%
Match confidence
Passenger
Name
A. Russell
Nationality · DOB
Bahamas · 14 Mar 1991
Document
Passport · Type P
Flight
Flight no. · Seat
BA212 · 14C
Authorization & risk
eTA status
Approved
Watchlist check
Clear
Passport issuing country
Bahamas
Country risk rating
Low
Refer
Admit
eTA & Digital Embarkation

The paperwork is done before they arrive.

Pre-travel vetting and digital arrival forms replace the visa stamp and the paper card. Passport details and security data are screened against watchlists days in advance, and the same enrollment quietly pre-stages the traveler's face for their walk-through.

Automated watchlist screening and fee processing
Digital customs, health, and lodging declarations
Modular API — toggle fields and rules per jurisdiction
Try demo
eTA
Arrival card
Travel document
Passport no.
••• •••4471
Nationality
Bahamas
Trip details
Flight no.
BA212
Purpose of visit
Tourism
Length of stay
8 days
Customs declaration
Goods to declare
No
Currency over limit
No
Watchlist screening passed
Digital Travel Credential

A passport that lives on the phone it belongs to.

Cryptographically signed data is extracted directly from the ePassport chip and bound to the traveler's device, signed by the issuing government's own certificate authority. It's authenticable by any compliant border gate — no call back to our servers required.

ICAO Type 1-compliant, PKI-backed credential
Sent ahead for zero-stop clearance on arrival
Issuance, vetting, and verification — one continuum
TYPE 1 · eMRTD
A. RUSSELL
Bahamas · Passport ••••4471
IssuedCSCA · BHS
Expires04 / 2031
Chip read via NFCDG1 + DG2 extracted
PKI signature validChained to issuing CSCA
Sent aheadReady for zero-stop clearance

From booking to walking through

Every stage of the journey feeds the next, so nothing is checked twice.

1

Book & enroll

Passport or ID details are captured once, at booking or check-in.

2

Pre-screen

eTA and digital arrival data are vetted before departure.

3

Arrive

The traveler's face is already staged in a secure, temporary gallery.

4

Walk through

A live camera matches, the gate opens, the data purges itself.

How data actually moves through the platform

Five components, from booking to the officer's decision. Click any component below for what it does and what data it touches.

System data flow
Pre-arrival Border control Sovereign infrastructure
check-in data API / PNR data credential + risk result arrival: biometric capture decision + audit Traveler & device Enrollment · DTC wallet Airline & check-in Booking · DCS · PNR Pre-arrival services eTA · Embarkation · DTC issuance Border booth TVS match · officer console Data store Sovereign · audited
← Scroll to see all components →
Overview

Five components, one continuum

Each stage feeds the next: a booking becomes a screened eTA, a screened eTA becomes an issued credential, and an issued credential is what the officer's console confirms on arrival. Click any card to see what it does and what data passes through it.

Privacy by design, audited by others

Faces are tokenized on capture. Nothing raw is kept longer than the trip requires.

SOC 2 Type II ISO/IEC 27001 GDPR CCPA ICAO-compliant AES-256 at rest TLS 1.3 in transit
Data residency & sovereignty

Your data stays inside your jurisdiction — by default, not by request.

OurVision AI operates as a processor on behalf of the government or carrier that deploys us. The infrastructure, the access rules, and the retention clock all belong to them — not to us. See the full system architecture for how data actually moves.

01

Hosted inside the deploying jurisdiction

Biometric templates, credentials, and case records are stored in infrastructure located in — or contractually designated by — the government that deploys the system, not in a default OurVision AI region.

02

No cross-border transfer without authorization

Data does not move between jurisdictions, or to a regional or shared service, without the deploying authority's explicit, documented sign-off.

03

Government-controlled access, always

Access to enrollment, matching, and case data is governed by the customer's own access policy. OurVision AI support access is logged and requires the customer's approval, not our own discretion.

04

Retention set by the customer, not by us

Retention and deletion schedules follow the deploying government's law and policy. Transient traveler data — a live capture, a match score — purges automatically once its purpose is served.

05

On-premises or sovereign-cloud where required

Where law or policy requires infrastructure to stay on government-owned or government-designated hardware, the platform is built to deploy that way rather than assuming a single hosting model.

Ready to see it running end to end?

We'll walk you through the platform on your own timeline and data.

info@ourvision.ai