This deployment option is designed for organizations with strict network security policies that allow selective internet connectivity through whitelist/allowlist rules.
Key Benefit: Consolidates all Quix platform dependencies into a single mirror registry, eliminating the need to whitelist multiple public registries and their complex CDN redirect chains (particularly Docker Hub).
quixmirror.azurecr.io (HTTPS/443)
Purpose: Quix-managed container registry mirror containing all platform and vendor images, plus Helm charts. Eliminates the need to whitelist multiple public registries and their redirect chains.
Inbound IP addresses
These are the IP addresses where Anthropic services receive incoming connections.
IPv4
160.79.104.0/23IPv6
2607:6bc0::/48Outbound IP addresses
These are the stable IP addresses that Anthropic uses for outbound requests (for example, when making MCP tool calls to external servers).
IPv4
160.79.104.0/21Per https://platform.claude.com/docs/en/api/ip-addresses
Note: Technically only the QuixAI pods need to access these IPs, so network policy may be helpful, but DevSessions requiring it in the future would complicate that. If anyone should ask.
For authentication, monitoring, developer services, and DNS requirements shared across all Quix deployments, see Common Network Requirements.
For questions about whitelisted deployments, contact Quix support.