The AirWatch Content Gateway supports deploying a basic endpoint model or a relay-endpoint model. Use the deployment model that best fits your needs.

Both SaaS and on-premises AirWatch environments support the basic and relay-endpoint deployment models. The AirWatch Content Gateway must have a publicly accessible endpoint for devices to connect to when making a request. Basic deployment models have a single instance of AirWatch Content Gateway configured with a public DNS. Alternatively, for the relay-endpoint deployment model, the public DNS is mapped to the relay server in the DMZ. This server communicates with your API and AWCM servers. For SaaS deployments, AirWatch hosts the API and AWCM components in the cloud. For an on-premises environment, the AWCM component is typically installed in the DMZ with the API.