Architecture & Hosting

Dr Migrate can be hosted two ways: fully managed by Dr Migrate (SaaS) or deployed into your own Azure tenant (Marketplace). The capabilities are identical; only how and where it runs differs.

SaaS (Cloud) Hosted

Fully managed instance in Dr Migrate's secure, ISO 27001-compliant cloud.

Marketplace (Customer Hosted)

Managed application deployed into your own Azure tenant.

Choosing a model¶

	Marketplace	SaaS Hosted
Deployed to	Your Azure tenant	Dr Migrate's secure cloud
Data residency	Stays in your tenant	Dedicated, air-gapped instance
Infrastructure	You manage VM, storage, Bastion	Nothing to manage
Best for	Strict data-residency / control	Fast turnaround, minimal setup

For the full side-by-side comparison and deployment detail, see Hosting Methods.

Deployment architecture¶

SaaS (DMC)¶

SaaS architecture using DMC for data collection — SaaS (Cloud) hosted. Data collected via the Dr Migrate Collector and uploaded to your dedicated Dr Migrate instance.

SaaS (Azure Migrate)¶

SaaS architecture using Azure Migrate for data collection — SaaS (Cloud) hosted. Data delivered from Azure Migrate in your tenant to your dedicated Dr Migrate instance via REST API.

Marketplace (DMC)¶

Marketplace deployment using DMC for data collection — Marketplace (customer-hosted). DMC collects data on-premises and the encrypted payload is uploaded directly to Dr Migrate in your Azure tenant.

Marketplace (Azure Migrate)¶

Marketplace deployment using Azure Migrate for data collection — Marketplace (customer-hosted). Azure Migrate appliances collect data and Dr Migrate reads it via REST API within your Azure tenant.

Deep architecture diagrams, managed resource group contents, identity/authentication flows and VM sizing guidance live on the Marketplace and SaaS architecture pages.