2. Customer Managed API Connect on-premises or on any cloud You have the flexibility to deploy on any cloud infastructure by using these tools: GLYPH<129> Kubernetes GLYPH<129> Red Hat OpenShift (with the option to us e the consolidated administrative user  interface provided by the IBM Cloud Pak for Integration) GLYPH<129> VMware (also Kubernetes inside)  GLYPH<SM590000> Security Gateway placed between the firewalls, as shown in the next figure GLYPH<SM590000> API gateway, both as internal and external gateway GLYPH<SM590000> Providing connectivity and mediation services in the internal network, close to the systems  of record  Figure 5-2 shows DataPower usage patterns. The table at the following site provides a convenient comparison of these different options: https://www.ibm.com/support/knowledgecenter/en/SSMNED_2018/com.ibm.apic.overview.d oc/rapic_overview_apic_formats.html The Integration Security component helps provide security, control, integration, and optimized  access to a full range of mobile, web, application programming interface (API),  service-oriented architecture (SOA), B2B, and cloud workloads. As noted above, it is used as  the API Gateway component within API Lifecycle, but it has much broader capabilities than  just API exposure as we discuss in this section. The Integration Security capabilities are also  sold separately as IBM DataPower Gateway. It is available in physical, virtual, cloud, Linux,  and Docker form factors. The Integration Security capabilities are extensively used in the industry and its usage can be  broadly categorized into the following patterns: 5.4 Integration security: IBM DataPower Gateway 152  Accelerating Modernization with Agile Integration