Language

On-Premises Identity Verification

What is on-premises identity verification?

On-premises identity verification is a deployment model in which document and biometric verification software runs within infrastructure controlled by the organization using it. In the strict sense, this infrastructure is located in the organization’s own facilities or private data center. Some vendors use “on-premises” more broadly for self-hosted software that can also run in a customer-controlled cloud environment.
The organization controls the processing environment, access policies, storage, and data-governance rules. It may operate the system itself or use an approved service provider for specific maintenance and support tasks. The main distinction from a vendor-hosted service is that the customer controls the environment in which identity data is processed and stored.

How does on-premises identity verification work?

A mobile application, website, kiosk, or document reader captures an identity document, facial image, or other required evidence. The data is sent to verification components running within the organization’s environment. These components may extract document fields, examine authenticity features, compare facial images, perform liveness checks, and return the results to the organization’s application.
The organization determines how these results enter its onboarding, account recovery, reverification, or case-review processes. It can configure access rights, storage, retention periods, logging, and integrations with internal systems according to its policies and regulatory requirements.
An on-premises installation still requires regular maintenance. Document templates, software components, security certificates, and fraud-detection controls may need updating as documents and attack methods change. The organization must also protect capture channels, servers, databases, backups, cryptographic keys, and administrative access.

Why do organizations choose on-premises deployment?

The main reason is direct control over sensitive data and the systems that process it. An organization may need to meet internal security policies, control data residency, restrict third-party access, or integrate identity verification with existing infrastructure and security systems.
On-premises deployment can also support multiple workflows through a shared verification capability. These may include customer onboarding, account recovery, in-person verification, employee screening, and access to government or regulated services. Organizations processing a high volume of checks may prefer to operate this capability within their own infrastructure.

How is on-premises different from private cloud?

An on-premises system typically runs on infrastructure located in an organization’s own facilities or private data center. A private-cloud system runs on dedicated cloud infrastructure assigned to one customer. That environment may be located in the customer’s cloud account or operated by a provider.
Both models can give the customer substantial control over data location, network configuration, computing resources, and access policies. The main differences concern the underlying infrastructure, use of cloud services, scalability, and allocation of management responsibilities.
Organizations should examine the actual architecture rather than relying only on the deployment label. They need to establish where data is processed and stored, what access the vendor retains, how updates are delivered, who manages dependent infrastructure, and whether any integration transfers identity information outside the controlled environment.

How can Regula help with on-premises identity verification?

Regula IDV Platform, Regula Document Reader SDK, and Regula Face SDK can be deployed in a customer-controlled environment.
Regula Document Reader SDK performs identity-document data extraction and authenticity checks. It can process information from the visual zone, machine-readable zone, barcodes, and NFC/RFID chips where supported. Regula Face SDK provides face matching and liveness detection to help establish that the applicant is present and matches a trusted portrait.
Regula IDV Platform coordinates document and biometric verification through configurable workflows. Organizations can configure its storage, access controls, integrations, and retention settings according to their infrastructure and data-governance requirements.
Regula’s software can also run in customer-controlled cloud or hybrid infrastructure.

FAQ

Why might an organization choose on-premises identity verification instead of cloud?

On-premises deployment provides closer control over sensitive identity and biometric data, system configuration, network access, and data retention. It may also simplify integration with internal systems and help organizations satisfy strict security or data-location policies. However, these benefits come with greater responsibility for infrastructure, maintenance, scaling, monitoring, backups, and disaster recovery.

Is it possible to deploy identity verification within a customer-controlled cloud environment?

Yes, provided the identity verification vendor supports this deployment model. The software may run in a dedicated environment within the customer’s AWS, Microsoft Azure, Google Cloud, or other cloud account. This gives the customer greater control over data location and access policies, while retaining the scalability and infrastructure services available in the cloud. Regula is one of such providers.

Is it possible to migrate from cloud identity verification to an on-premises deployment?

Yes, but the complexity depends on the solution and its deployment options. Migration is easier when the provider offers equivalent cloud and on-premises software, compatible APIs, documented data-export capabilities, and support for transferring workflows and records. Organizations should review data portability, contractual exit terms, infrastructure requirements, migration support, and implementation costs.

When do data-residency rules influence the choice of deployment?

Data-residency requirements may determine where identity documents, biometric data, verification results, logs, and backups can be processed or stored. Organizations must also consider whether support personnel or subprocessors can access the data from another jurisdiction. On-premises or customer-controlled deployments may provide greater control when standard cloud regions do not meet these requirements. The final decision should reflect applicable law, contractual obligations, internal policy, and the solution’s actual data flows.

On our website, we use cookies to collect technical information. In particular, we process the IP address of your location to personalize the content of the site

Cookie Policy rules