Face and palm authentication engines run inside GATE, and GATE runs in smart cities, smart schools and payments.
Explore GATE Talk to UsBelow are the sites where authentication is actually used; above are the engines that perform it. GATE sits between them and joins the two sides under a single specification. A site system integrates with GATE once, and when the engine changes the site integration stays as it is.
The terminals and the site systems are yours. GATE's scope runs to the spoof check and the match; payment approval, door control and membership handling are picked up by your systems.
Not laboratory figures — deployments in operation and accredited test results.
The screens differ and the names differ from site to site, but at the moment identity is confirmed, the same GATE is running.
Behind the control-room screen, GATE is what pins down who the person is.
It runs a 1:N match against the enrolled list and returns only the result to the control system. Your cameras and control screens stay as they are; only the matching engine moves into the server.
GATE is the authentication server that face-recognition attendance terminals call.
A student stands in front of the terminal, GATE matches against the enrolled list and returns whether it is them; the attendance record and the notification are handled by the school system. Feature data for matching is kept in place of the original photograph.
Behind stored-value face payment and the POS, GATE is what confirms identity.
After a one-time enrolment, a face carries the customer through to payment with no card and no phone. GATE's part ends at confirming identity; deducting the balance and approving the payment are picked up by the payment system.
Three products and one platform. Pick only what you need and layer it onto the environment you already run. Wherever authentication is required, all of them meet GATE.
Combine conditions — face, body, clothing colour, carried items — to trace a person back through recorded video. Layered onto existing CCTV, no camera replacement.
Cuts footage by roughly 85% right beside the camera, so retention policy days survive a 4K upgrade. One box covers four channels.
An all-in-one terminal that carries a face all the way to payment — no card, no phone. Backed by a reference deployment running face payments at commercial scale.
Five packages assembled by industry. Each starts from what actually happens on that site, not from a product list.
“An incident just came in. How many hours does finding that person take you today?”
“The person on the other side of the screen — what exactly makes you certain it is them?”
“The person in that entry log — was it actually them?”
“You called the roll. Does that record match who was actually in the room?”
“The network bill comes every month, and there is neither room nor staff for a server room.”
The same face recognition engine that drives VCA and POS, exposed directly as an API. The call is identical whether you deploy on-premises, at the edge or in the cloud. The integration specification is published as a documented commercial REST API, so your development team or SI partner can build from the documentation alone, and an issued key lets you call it in a test environment first.
Open the Developer Docs →# 1:N face match — request example (multipart) POST /api/v1/feature/face/identify Authorization: Bearer <accessToken> X-Api-Key: <project API key> Content-Type: multipart/form-data # matchingFeatureImage=<face image> # Response { "success": true, "data": { "matchType": "IDENTIFY", "featureId": "abc123-def456", "similarity": 97.00, "checkLiveness": true, "transactionUuid": "550e8400-..." } }
1:1 verification, face enrolment and match-history lookup are provided under the same specification. When fingerprint and iris engines join GATE, the call shown here stays as it is.
The size of the population to be authenticated, whether you install on your own servers or in the cloud, and your target deployment date. Send those three and we will reply with a configuration and a verification method.
Talk to Us