Organisations operating across dispersed geographies increasingly need to expose and consume APIs at the network edge without surrendering control over where traffic travels or where sensitive payloads are processed. For mining and resources operators, this tension is acute, because remote sites, processing plants, and port facilities often run latency-sensitive systems that cannot tolerate a round trip to a distant cloud region for every request. The Azure API Management self-hosted gateway addresses this problem directly by placing the API runtime close to the workloads that depend on it while keeping policy, versioning, and observability under a single centralised control plane. This model allows an organisation to reconcile sovereign and operational constraints with the governance benefits of a managed platform.
The purpose of this article is to explain how the self-hosted gateway works, why it suits hybrid and in-country integration scenarios, and what technical and governance factors decision makers should weigh before adopting it. It is written for architects and technology leaders who need practical detail rather than marketing framing. The discussion assumes a Microsoft-native environment and treats the self-hosted gateway as one component within a broader Azure integration estate.
Azure API Management is conventionally understood as a managed gateway hosted within a Microsoft data centre region, but the platform also offers a containerised gateway that customers deploy on infrastructure they control. This self-hosted gateway is distributed as a Linux-based container image and is typically run on Kubernetes, whether that cluster sits in an on-premises data centre, at a remote mine site, or in another cloud. The critical architectural property is the separation of concerns: the gateway executes API policies and forwards traffic locally, while the management, configuration, and analytics functions remain in Azure. As a result, the request and response payloads that traverse the gateway never need to leave the site or the country in which the gateway is deployed.
This separation delivers meaningful sovereignty and latency outcomes. Because the data plane runs at the edge, API calls between local systems are mediated on site, which reduces round-trip time for latency-sensitive control and telemetry systems common in resources operations. The gateway periodically retrieves its configuration from the Azure control plane and reports metrics and logs back, so administrators continue to manage products, policies, and subscriptions from one place. Should connectivity to Azure be interrupted, the gateway continues to operate using a locally cached configuration, which matters greatly for remote locations with intermittent satellite or microwave links.
Mining and resources environments present a distinctive set of integration requirements that the self-hosted gateway is well positioned to serve. A remote processing facility may run supervisory control systems, condition-monitoring platforms, and local analytics that must exchange data through well-governed APIs even when the wide area network to the corporate cloud is degraded. Deploying a gateway on a local cluster means that authentication, rate limiting, request transformation, and payload validation all happen close to the equipment rather than depending on a distant endpoint. This keeps operational systems responsive and reduces the blast radius of a connectivity failure.
Sovereignty and data residency considerations reinforce the case for local mediation. Where an organisation must demonstrate that particular categories of data remain within Australian jurisdiction or within a defined physical boundary, keeping the data plane on infrastructure the organisation controls provides a clear and auditable answer. The centralised control plane still enforces consistent security policy across every site, so a change to an authentication requirement or a threat-mitigation rule can be applied uniformly without visiting each location. Teams responsible for governance should map their data classification and residency obligations to the specific traffic flows the gateway will handle, then document how the deployment satisfies those obligations.
Adopting the self-hosted gateway requires an API Management instance on a tier that supports the capability, and it introduces operational responsibilities that the fully managed gateway does not. The organisation owns the host platform, which usually means running and patching a Kubernetes cluster, managing container image updates, and monitoring the health of the gateway pods. Azure Arc can bring these clusters under a consistent management and policy framework, allowing the same governance tooling to reach infrastructure that sits outside Azure. Planning should account for image lifecycle, certificate management for transport security, and the resourcing needed to keep edge platforms current.
Resilience and observability deserve deliberate design rather than default acceptance. Because the gateway depends on periodic communication with Azure for configuration and telemetry, architects should test behaviour under prolonged disconnection and confirm that the local configuration cache and its retention meet the availability targets of the systems it serves. Metrics and logs should flow to a central location for security monitoring, and the deployment should be sized so that a single node failure does not remove local API mediation entirely. When these controls are established early, the self-hosted gateway becomes a dependable bridge between edge operations and centralised governance, giving organisations local performance and sovereign control without fragmenting their integration platform.

Level 7, 12 St Georges Tce
Perth WA 6000
[email protected]
Ph 1300 NOVATA

In the spirit of reconciliation Novata Solutions acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their Elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today. This land always was, and always will be Aboriginal Land.

Novata Solutions is committed to embracing diversity and eliminating all forms of discrimination through education. We welcomes all people and is respectful of individual identities.