On-Premises Identity Verification
What is on-premises identity verification?
How does on-premises identity verification work?
Why do organizations choose on-premises deployment?
How is on-premises different from private cloud?
How can Regula help with on-premises identity verification?
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.