Static IPs for GitHub Actions without managing runners
Use dedicated Avrea static IPs to allowlist CI traffic. Choose one address or several across supported datacenters, while jobs run in ephemeral VMs.

Your deploy job has valid credentials, but the firewall rejects it because the runner's IP changed. Avrea now sends traffic to services protected by IP allow-lists through dedicated static IPv4 addresses, while your GitHub Actions jobs still run on clean ephemeral VMs.
Dynamic runner IPs do not belong in production allow-lists
Standard GitHub-hosted runners use dynamically assigned addresses from shared infrastructure. GitHub publishes the address ranges through its website but the list is large and is updated weekly, and GitHub does not recommend using it as an allow-list for internal resources.
That leaves a bad set of options: open the firewall to broad shared ranges, operate self-hosted runners behind your own NAT gateway, or rely on credentials alone.
CI should not force that choice. A build that deploys to production, downloads from a private package registry, calls a payment processor, or runs migrations against a protected database needs a predictable network identity. It should not need a permanent runner to get one.
Share static IPs across GitHub Actions jobs
Avrea’s Network egress settings let an organization reserve one or more static IPs in supported datacenters. Jobs share the addresses enabled by its routing policy. Organizations still on the legacy configuration keep a single address.
Add every routing-enabled address to your services’ allow-lists, or restrict the policy to a specific subset.
The address belongs to the organization, not to a VM or repository. A fresh VM still starts for every job and disappears when the job finishes. The next VM uses an address from the same routing policy. Static IPs do not keep a VM running between jobs; configured caches and persistent disks can still supply files to the new VM.
Existing Avrea customers do not need to change a workflow. If you are moving from standard GitHub-hosted runners, the Avrea migration remains a one-line label change.
Keep ephemeral runners without managing a NAT gateway
Self-hosting can produce a known egress IP. It also makes your team responsible for runner images, security updates, autoscaling, capacity, and cleanup. The NAT gateway is the easy part. The runner fleet behind it is the job that keeps growing.
Avrea keeps that work on our side. Your workflow gets a clean hosted VM and your network team gets a stable address. There is no long-lived machine to patch and no shared workspace to scrub between jobs.
Fintech teams can restrict payment and banking APIs to one source. Platform teams can expose a private package registry without accepting traffic from a cloud provider’s full runner range. Deployment jobs can reach protected production endpoints without placing the entire CI fleet inside the production network.
Static IP and egress policy solve different sides of the connection
A static source IP tells your service which runner traffic it may accept. An egress policy tells the runner which destinations it may contact. Used together, they put a boundary on both ends of the connection.
Your database firewall can allowlist Avrea’s static IPs. Avrea’s per-repository egress firewall limits outbound destinations; required platform connections remain allowed.
Reserve addresses and enable routing
Open Settings → Network egress. Reserve an IP, add it to your service allow-lists, then enable routing and select Dedicated static IPs. The network egress guide also covers the legacy single-IP switch.
Each reserved IP costs $100 per month, metered at $3.33 per started UTC day. Disabling routing retains the reservation and its charges; release the address to end them once jobs and network cleanup have drained.
Behind the setting, Avrea routes outbound IPv4 traffic to your destinations through an encrypted tunnel to an Avrea-managed router, which presents the selected reserved address. Avrea service traffic, including colocated cache traffic, stays on its direct path so the static route does not get in the way of build performance.
Enable static-IP egress in the Avrea console. Dedicated addresses, without a runner fleet to maintain.