These addresses are stable and apply across all supported code hosts (GitHub,
GitLab, Azure DevOps, and Bitbucket). If your allowlist is configured, add all
three so a failover between them does not interrupt Gitar.
Connect Repositories
Network Access
Firewall and IP allowlisting requirements for connecting Gitar to your code host
If your code host enforces an IP allowlist — whether it is self-hosted behind a
firewall or a cloud instance with allowlisting enabled (for example, GitHub or
GitLab organization-level IP restrictions) — you must permit traffic from
Gitar’s public IP addresses.
These are the external-facing NAT Gateway IPs that Gitar uses for all outbound
requests (e.g., cloning repositories, pushing changes, and calling your code
host’s API):
Add all three IP addresses to your firewall rules or your code host’s network
allowlist to ensure uninterrupted connectivity.