Global deployment scenerios

Strivacity supports three global deployment scenarios. The scenario you choose depends on where your customer-facing applications are hosted and how you want your customers to be routed to your applications for registration or login.

All three global deployment scenarios support data residency and data sovereignty requirements for the country or countries that you choose to deploy to. PII is stored and processed only in the country where you choose for it to reside, ensuring compliance with national data protection laws.

The three global deployment options are:

1. Same-country hosting model

In this scenario, the Strivacity instance and customer-facing website/application are hosted in the same country.

This is the most straightforward model for meeting data residency requirements. In this setup, both the customer-facing website/application and Strivacity (including the Identity Store) are hosted within the same country.

2. Localized application hosting model

In this scenario, the Strivacity instance is hosted in the country/countries where data residency needs to be met.

In this approach, Strivacity (including the Identity Store) is deployed in each country where data residency regulations must be met. The customer-facing website/application is typically also implemented regionally to support this model. A global website acts as a routing layer, directing users to the correct regional instance of Strivacity based on location or user selection.

3. Automated regional routing model

In this scenario, the Strivacity instance automatically routes customers to the correct country based on a global catalog to meet data residency requirements

In this setup, Strivacity intelligently routes authentication requests to the appropriate regional Strivacity instance based on the customer's location—without requiring the customer to manually select a region.