The basic endpoint deployment model of AirWatch Content Gateway is a single instance of the product installed on a server with a publicly available DNS.

Basic AirWatch Content Gateway is typically installed in the internal network behind a load balancer in the DMZ that forwards traffic on the configured ports to the AirWatch Content Gateway, which then connects directly to your internal content repositories. All deployment configurations support load balancing and reverse proxy.

The basic endpoint Content Gateway server communicates with API and Devices Services. Device Services connects the end user device to the correct Content Gateway.

If the basic endpoint is installed in the DMZ, the proper network changes must be made to allow the AirWatch Content Gateway to access various internal resources over the necessary ports. Installing this component behind a load balancer in the DMZ minimizes the number of network changes to implement the AirWatch Content Gateway and provides a layer of security because the public DNS is not pointed directly to the server that hosts the AirWatch Content Gateway.