On-Premise Identity Verification
Deploy Identixia's biometric and document SDKs entirely inside your own infrastructure — private cloud, on-device, or offline where supported — without a mandatory dependency on a third-party cloud API.

Where verification happens is a design decision, not an afterthought
Many identity verification vendors process data on their own cloud servers by default. Identixia is built the other way: the SDKs run inside your infrastructure, and staying there is the default deployment path, not an enterprise add-on.
Data control
Your organization decides where verification data is processed and stored, rather than routing it through a vendor's cloud by default.
Data residency
Keeping processing inside infrastructure you already control supports data residency requirements tied to a specific region or facility.
Privacy by architecture
Biometric and identity data doesn't need to leave your environment to be verified, reducing the number of parties that ever see it.
Four ways to deploy, same SDKs
Private cloud / VPC
Run the SDKs inside your own cloud account or virtual private cloud, under your own network and access controls.
On-device
Where supported, verification runs directly on the end-user device, with data never required to leave it.
Offline / air-gapped
Where supported, SDKs operate without an active internet connection, suited to disconnected or highly restricted environments.
Server / container
Deploy on your own servers or as containers within your existing orchestration (Docker-based deployment), alongside systems you already run.
Fits inside the infrastructure you already run
Because the SDKs are deployed as software inside your environment rather than accessed as a hosted API, they integrate with your existing network segmentation, identity and access management, and logging — without introducing a new external dependency into your verification path.

Designed to support your compliance work, not replace it
On-premise deployment is an architecture choice that can help your organization meet data residency, sovereignty, or sector-specific infrastructure requirements — the specific regulatory obligations that apply to your organization, and whether they're satisfied, are determined by your own legal and compliance review. See Security & Privacy for how we describe claim strength around standards and compliance.
One deployment model, applied consistently
On-premise deployment isn't specific to one product — it applies the same way across the full catalog.
Face Recognition
View SDK →Face Liveness
View SDK →ID Document Recognition
View SDK →Document Liveness
View SDK →On-premise means on-premise — including relative to us
Deployed on-premise, Identixia's SDKs don't require a call to Identixia's own servers to function. Your infrastructure runs the verification logic; ours doesn't need to be in the loop.

Frequently asked questions
Talk through your deployment architecture
Our solutions engineering team can walk through private cloud, on-device, and offline options for your environment.