MOBILE-ID · TRUSTED LTANS

Deployment Model Comparison

Compare control, operations, security and exit arrangements across SaaS and on-premises deployment.

Compare control and responsibility

Criterion	SaaS · managed service	On-Premise · customer infrastructure
Infrastructure and operations	Mobile-ID within service scope	Customer-operated; Mobile-ID support by contract
Data residency	Agree regions for content, evidence and copies	Customer data centers and policy
Tenants and authorization	Tenant isolation and record-group permissions	Configured enterprise identity integration
Storage and keys	Provider/BYOS per profile; agree key control	Customer controls storage/keys or delegates narrowly
CA / TSA / HSM	Approved sources with versioned configuration	Local or remote subject to network policy
Network and transfer	Profile-defined TLS/mTLS; fetch allow-list	Agree internal/DMZ networking, proxies and support access
Capacity and throughput	Discovery and PoC-based parameters	Measure against actual infrastructure, TSA and storage
Backup and recovery	Agree RTO/RPO, drills and evidence reconciliation	Customer-operated; accept key and renewal-schedule recovery
Upgrades and patches	Service release and notification schedule	Customer-controlled change windows
Support and 24/7	Under contracted plan and schedule	Agree support tiers and remote access
Service exit	Package export, verification and recipient receipt	Handover configuration, documentation and continued-operation rights

Scope a SaaS service by storage configuration, trust sources, support and metering units.

Assign network, storage, keys, backup and upgrade responsibilities on customer infrastructure.

Define usage units, infrastructure and third-party costs, reconciliation and data-export terms.