--- title: "Deployment models" slug: "oas-pdg-deployment-models" updated: 2025-07-31T10:33:36Z published: 2025-07-31T10:59:48Z canonical: "docs.onespan.com/oas-pdg-deployment-models" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Deployment models A OneSpan Authentication Server installation can be used for the following tasks: - Authentication - Signature validation - Auditing - Co-ordinating the distribution of authenticators (provisioning) - Administration of data, configuration, and authentication settings - Reporting In larger deployments, single OneSpan Authentication Server instances may be assigned specific tasks—for example, one instance to handle authentication requests, another one to handle provisioning and administration, and a third one for auditing and reporting tasks. A number of options are available to scale OneSpan Authentication Server to the required level of operability, availability, and performance. The deployment model that applies best to your situation depends on these basic factors: - Number of users in the system. - Amount of authentication traffic. - Number of sites that need authentication. - Required system availability. How important is it that authentication requests are being processed immediately? This guide outlines some basic deployment models (see [Table: Deployment models](/sec/docs/oas-pdg-deployment-models#Tab_DeploymentModels)).
Table: Deployment models
Deployment modelNumber of usersAuthentications/secondNumber of sitesSystem availability required
Basic< 50< 501Normal
Advanced50– 20,000< 501Normal
High-Availability100– 50,000> 501High
Maximum-Availability< 2,000,000> 1001Critical
WAN50–2,000,000< 50MultipleHigh
Network HSM50–2,000,000< 501Normal
Internal HSM50–2,000,000> 501Normal