server/priv/docs/en/guides/server/network.md
This page covers network-related configuration that may be needed when integrating Tuist with your infrastructure.
If your infrastructure restricts inbound traffic by IP address, you may need to allowlist the IP ranges used by Tuist. This is common when Tuist needs to communicate with services behind a firewall or VPN, such as self-hosted Git providers or artifact storage, or when your GitHub organization uses IP allow lists.
Tuist outbound network traffic that reaches customer infrastructure originates from a fixed, reserved set of stable IP addresses. Allowlist every address in the set: Tuist will only ever egress from within it, and the set is sized so we can grow capacity or fail over between addresses without you having to change your allowlist.
| IP address | CIDR notation |
|---|---|
| 116.202.0.10 | 116.202.0.10/32 |
| 116.202.4.195 | 116.202.4.195/32 |
<!-- MAINTAINERS: this table is the customer-facing contract for the reserved egress set. It must stay in lockstep with `ciliumEgressGateway.server.failoverController.egressIpAllowlist` in infra/helm/platform/values-tuist.yaml (the controller fails closed if the active Floating IP is outside that allowlist). When reserving additional Floating IPs in the tuist-workloads project, add their /32s to BOTH places *before* they are ever used as egress. -->[!TIP] Add all of the addresses above to your allowlist to ensure uninterrupted connectivity with Tuist services.