The engagement
I was responsible for implementing and maintaining the biometric liveness solution within Digital Dubai / UAE PASS, with ownership spanning technical integration, infrastructure, and coordination with the teams operating the wider platform.
The result travels back to the device the same way.
A focused capability
The scope centred on liveness and biometric verification within a much larger identity platform. Maintaining that capability meant working across application and server components, coordinating releases, and keeping implementation guidance clear for the teams integrating and supporting it.
My work included hands-on mobile SDK integration on iOS and
Android, deployment planning, testing, knowledge transfer, and ongoing technical support.
Engineering decisions
Paired nodes, separate environments. The server side ran as Docker containers, brought up with Docker Compose on paired, load-balanced application nodes: the
FaceTec Server SDK and its dashboard on each. A MongoDB cluster ran on its own database servers for high availability. QA and production were separate environments built the same way, so a release could be proven in one before it reached the other.
FaceTec device SDK
FaceTec Server SDK
FaceTec dashboard
FaceTec Server SDK
FaceTec dashboard
Automated with Python. I wrote the workflows and infrastructure automation around the service in Python, so routine operational work ran from scripts rather than by hand.
One capability, clear boundaries. The app, the user journey, and the identity decisions stayed with the platform. I owned the liveness capability inside it: the server, its dashboard, the deployments, and the guidance the mobile teams built against.
- The UAE PASS app and user journey
- Web and REST services
- Identity and account decisions
- Security and network requirements
- Liveness server and dashboard
- SDK integration with the mobile teams
- QA and production deployments
- Migration and deployment guides
Three calls for integrators. The service exposed a small, documented surface. A team integrating liveness needed three calls, and the guide covered each one.
- status
- is the service ready
- session token
- issued before a capture starts
- 3D liveness
- checks the capture, returns the result
Written down for the next team. I wrote the migration and deployment guides end to end, so the teams integrating and operating the service worked from one reference instead of from memory.
The major upgrade
In 2021 the liveness SDK moved to a new major version. The change reached every layer: renamed device APIs on iOS and Android, a new version of the server REST API, and a database schema migration. I planned the upgrade, wrote the procedure, and carried it through QA into production.
- 01 · DeviceSDK APIs renamed on iOS and Android
- 02 · ServerNew REST API version
- 03 · DataSchema migrated, backup first
- 04 · LicenceProduction licence configured
The order mattered more than any single step. The database was backed up before anything changed, the new version was proven in QA with the mobile teams, and only then did production move.
What I owned
- 01
Hands-on SDK integration with the mobile teams, on
iOS and
Android.
- 02
Infrastructure and deployment requirements for the liveness solution, across QA and production.
- 03
Workflows and infrastructure automation in
Python.
- 04
The major SDK upgrade: device API changes, the new server API version, the database migration, and the rollout.
- 05
Migration and deployment guides, testing support, and knowledge transfer.
- 06
Technical coordination across Digital Dubai stakeholders, delivery teams, and the biometric vendor, with ongoing maintenance.
Where it stands
I maintained the liveness capability from 2021 to 2024, working with government stakeholders, mobile engineering teams, infrastructure and security teams, and the biometric vendor to carry changes into the live service.
It was one capability inside a much larger platform. Owning it well meant owning the details: the application and server components, the releases, and guidance clear enough for other teams to integrate and support it.