Skip to main content
This feature is currently in private preview and is not intended for production use. In private preview, it has the following limitations:
  • It is only available in the us-was-1 region.
  • It is only available for sandboxes.
  • Egress gateway assignment is only possible at sandbox creation time.
  • Egress gateway removal is only possible by deleting the corresponding sandbox. For more information, contact us on Discord or request access.
Dedicated egress gateways enable customers to exclusively attach IP addresses to sandboxes within their workspace. This makes it possible to whitelist outbound traffic from Blaxel’s systems for use in downstream providers and eliminates the need for workarounds such as self-hosted proxy servers or VPNs. A single egress IP address supports up to 32,000 sandboxes. It is also possible to group IP addresses into pools to automatically load-balance outbound traffic for high-demand workloads. Sandboxes that do not have a dedicated egress gateway will use the shared public IP addresses instead.

​
Order an egress gateway

Egress gateway configuration takes place from the Blaxel Console.
  • Navigate to Network > Egress gateways.
  • Click the Order IP button in the top right corner. List IPs
  • Select the quantity and egress gateway region. Order IPs
Provisioning is automated and typically completes within a few minutes.

​
Assign an egress gateway to a sandbox

Once provisioning is complete, you can attach the assigned egress gateway when creating one or more sandboxes. All outbound traffic from the attached sandboxes will then originate from this unique address. You can assign an egress gateway to a sandbox at creation time via the Blaxel Console.

​
Blaxel Console

When creating a new sandbox via the Blaxel Console, use the Egress IP drop-down to assign an available egress gateway to that sandbox. Only egress gateways in the same region as the new sandbox are shown for assignment. Assign IP
Last modified on April 10, 2026