Network requirements
Documentation Index
Fetch the complete documentation index at: https://docs.sourcery.ai/llms.txt
Use this file to discover all available pages before exploring further.
Sourcery reaches your Git host from two static IP addresses. If your host or network restricts traffic by IP, allow these addresses.
Egress IP addresses
Section titled “Egress IP addresses”Sourcery makes outbound requests from:
34.142.124.12934.147.223.148
Traffic model
Section titled “Traffic model”A connection has two directions:
- Inbound to Sourcery – your Git host sends webhooks to Sourcery over HTTPS when pull requests and comments change.
- Outbound from Sourcery – Sourcery calls your Git host’s API to read diffs and post reviews. These calls come from the egress IPs above.
For a self-hosted Git server (GitHub Enterprise Server or self-hosted GitLab), the outbound direction is the one that needs firewall changes: your server must accept API traffic from Sourcery’s egress IPs. See the GHES quickstart and the self-hosted GitLab quickstart. If you also run self-hosted Sourcery, these egress rules apply to that deployment too.
IP-restricted GitHub.com
Section titled “IP-restricted GitHub.com”GitHub organizations can restrict access to allowlisted IP addresses. If yours does, add Sourcery’s egress IPs to the organization’s IP allowlist so Sourcery can reach your repositories. This is configured in GitHub’s organization settings.