05 / Periodic demand
Serve a large, occasionally active user population
Plan a licence budget without per-user charges and prepare operating capacity for recurring peaks in customer activity.
Explore portals with periodic demandScenarios / Own Your Identity Platform
Build business applications and SaaS services on an identity platform you own. Choose where it runs, connect existing identities and shape the experience your users need.
01 / B2B SaaS
Let customers combine local accounts with their own identity providers. Build tenant configuration into your onboarding tools and keep a common integration in your application.
Explore B2B customer onboarding
02 / Business applications
Connect business applications to a maintained identity platform. Combine enterprise federation and local accounts in one deployment, with control over integration and branding.
Explore business application identity03 / Deployment control
Deploy on premises, in a private cloud or with your chosen public-cloud provider. Keep control of identity data and plan hosting changes on a supported Kubernetes foundation.
Explore deployment controlDeployment choices for the same ProAuth platform, with your choice of infrastructure provider.
04 / Local availability
Run identity on site for local sign-in. Offline operation requires all services used by the configured sign-in path to remain locally available.
Explore local and offline sign-inOperation and delivery
05 / Periodic demand
Plan a licence budget without per-user charges and prepare operating capacity for recurring peaks in customer activity.
Explore portals with periodic demand06 / Redistribution licence
Include identity in software deployed in customer environments. Support local accounts or enterprise sign-in through a product integration that fits your installation process.
Explore identity that ships with your productIdentity requirements also change within an existing application. Explore the path to stronger token protection or passkey sign-in.
Use ProAuth BFF and .NET packages to introduce server-side token handling and sender-constrained API validation with clear integration steps.
Plan passkey sign-in for ProAuth user stores, including supported devices, enrolment, domain continuity and account recovery.
ProAuth customer projects inform these implementation patterns. Explore how teams make identity part of their product and operating model.
Deployment tooling configures ProAuth, while the product uses its APIs for user administration.
Explore this implementation pattern: Identity inside the product experienceA customer-built wizard collects identity requirements and applies tenant configuration through the Management API.
Explore this implementation pattern: Customer choices built into onboardingOffline sign-in requires the configured identity sources and all required services to remain locally available.
Explore this implementation pattern: Local sign-in under local control