This guide covers deploying Quix platform in restricted network environments. If your network allows unrestricted outbound internet access, this guide is not for you.
Traditional network whitelisting for container registries like Docker Hub is impractical due to complex redirect chains across multiple CDN providers and domains. This guide presents two supported deployment approaches that work around this limitation.
Both deployment options share common network requirements for authentication, monitoring, developer services, and DNS. See for details on Common Network Requirements :
Best for: Organizations that want control over external resources accessed from their hosting environment, without adding significant maintenance burden to their team.
Approach: Use Quix-managed mirror registry that consolidates platform dependencies into a minimal set of whitelisted endpoints. Quix maintains the mirror and handles updates.
See: Whitelisted Deployment for complete details.
Best for: Air-gapped environments or organizations that require full control over all infrastructure with minimal external dependencies.
Approach: Mirror Quix container registry to your own Azure Container Registry. You own the mirror and handle synchronization via a DMZ machine. Minimal external access required from production environment.
See: Air-Gapped Deployment for complete details.