Static Egress IP

Workspaces normally reach the Internet from changing sandbox addresses. With a static egress IP, every outbound request from your workspaces leaves from one permanent address instead, so your systems can allowlist it.

​

How it works

An encrypted tunnel carries the workspace’s traffic to a dedicated exit in us-west-2. Your systems see the exit’s address, not the sandbox’s. Direct outbound traffic is denied at the sandbox provider, with the exit as the only permitted destination. If the tunnel stops, Internet access stops, and nothing falls back to an unallowlisted address. Everything is covered without per-tool configuration: HTTPS, DNS, git, the GitHub CLI, npm, Bun, pip, apt, Chrome, and Docker containers.

​

Scope

A profile applies to a whole organization: every workspace in it uses the exit.

​

What to expect

• Requests take a small detour through Oregon, so latency increases slightly.
• Each organization gets its own credential, revocable independently. Rotating it does not change the address or port, so your allowlist entry stays valid.
• If the profile is turned off, existing workspaces lose Internet access and have to be recreated, the same way enabling is not retroactive.
• The credential is held in the workspace’s memory rather than written to its disk, so a filesystem snapshot cannot contain it.
• A resumed workspace is handed the current credential, so a rotated or revoked one cannot come back with it.
• Egress rules are set when a workspace is created. Enabling or changing a profile applies to new workspaces; existing ones keep the rules they were created with and must be recreated.
• Warm pools are rebuilt when a profile changes, so the first workspace afterwards starts cold.
• Traffic through the exit is rate limited as an abuse backstop. The limits sit well above normal use, since installs and browsers open connections in bursts, but an extreme volume of connections can be dropped.