Skip to main content
Workspaces normally reach the Internet from changing sandbox addresses. With a static egress IP, requests from your workspaces to the destinations you choose leave 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

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

Choose destinations

Only the destinations listed under Routed destinations use the static IP. An empty list uses it for nothing. List one per line:
  • an exact hostname, such as aws-0-us-east-1.pooler.supabase.com
  • an IPv4 address, such as 203.0.113.7
  • an IPv4 CIDR range, such as 203.0.113.0/24
Everything else leaves directly from the sandbox. Workspaces resolve hostnames themselves and re-resolve them every minute, so wildcards are not supported and a hostname needs an IPv4 address. For Supabase, use the connection pooler host, since direct database hosts are IPv6-only by default. Workspaces pick up edits when they are created or next wake. Profiles created before destinations existed start with an empty list, so their new workspaces use ordinary egress until an admin adds destinations.

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. Only the listed destinations take the tunnel; everything else, DNS included, leaves directly. If the tunnel stops, requests to those destinations leave from a sandbox address, which your allowlist rejects.

Dedicated IP

By default, the static IP is shared with other Replicas organizations that use static egress. Contact us for an IP used only by your organization. With a dedicated IP, an admin can turn on Route all traffic so every request from your workspaces uses it, not only the routed destinations. Traffic through a dedicated IP is billed at $0.15 / GB.

Scope

A profile applies to every workspace in an organization.

What to expect

  • Requests to listed destinations take a small detour through Oregon, so their 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, workspaces stop using the static IP the next time they wake.
  • 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.
  • Workspaces created before destinations existed routed all traffic, with direct traffic denied at the sandbox provider. They keep routing all of it until they are recreated, and lose Internet access if the profile is turned off.
  • 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.