Skip to main content
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. Static egress is available to organizations on paid Team and Enterprise plans. Organizations on other plans or trials can use it when Replicas enables access for them.

​
Manage static egress

Any organization member can open Settings → Organization → Security to turn static egress on. After provisioning finishes, the same section shows the IP address to add to your allowlist. Members can also turn the profile off there.

​
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 new workspaces across a whole organization. Existing workspaces keep the egress rules they were created with, so recreate a workspace after turning static egress on if it must use the permanent address.

​
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 static-egress workspaces fail closed without Internet access and have to be recreated. New workspaces use ordinary egress.
  • 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. Older unrestricted workspaces continue waking with ordinary egress; recreate one only if it must adopt the static exit. Changing a profile applies to new workspaces, while existing static-egress workspaces keep their original provider rules.
  • 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.