Choose where IDSENTRA runs based on security, continuity, sites, and hardware—not a one-size-fits-all hosting assumption.

Choose the architecture that fits the customer's sites, devices and security boundaries.

Evaluate hosted, customer-controlled and hybrid patterns against local hardware, connectivity, resilience, support, retention and enterprise integration requirements.

1. Protected hosted environments

   Use a hosted customer environment with organization-specific users, operational records, configuration, integrations, and security controls.

2. Customer-controlled deployment

   Keep designated services and protected workflows within customer-controlled infrastructure when security, connectivity, or operating requirements call for local deployment.

3. Hybrid patterns

   Combine protected cloud services with customer-controlled components and local hardware where the operating model requires both.

4. Multi-site operations

   Maintain organization and location context across properties, stores, venues, entrances, departments, and temporary sites.

5. Mobile and temporary operations

   Extend supported identity workflows to festivals, pop-up checkpoints, mobile teams, and environments without permanent front-desk infrastructure.

6. Continuity and recovery

   Plan critical identity workflows around connectivity changes, degraded operation, backup, recovery, and local operational requirements.

7. Connected hardware

   Combine mobile scanning, compatible verification devices, and protected local connectivity with the selected deployment model.