Network
Network addresses to allow
Each Saible region has fixed addresses in both directions. Allow the ones for your organisation's region. The addresses are IPv4. Last read from Saible's infrastructure on 22 October 2026.
Your network to Saible
People who use the console, your gateways and your scripts connect to Saible on TCP port 443 (HTTPS). Port 80 answers only with a redirect to HTTPS. Allow the host names where your firewall or proxy can. Where it can only allow addresses, use the fixed inbound addresses. The host names resolve to those addresses.
Saible to your systems
Every connection Saible opens to a system you connect, such as a Snowflake account with a network policy or a self-hosted Git server, comes from the fixed outbound addresses of your organisation's region. The port is the one that system listens on, usually 443.
| Region | Host names (TCP 443) | Inbound addresses (TCP 443 and 80) | Outbound addresses |
|---|---|---|---|
| United States (Ohio) us-east-2 |
|
|
|
| EU (Stockholm) eu-north-1 |
|
|
|
Notes
- The outbound addresses are Elastic IP addresses reserved for the region. Saible updates this page before an address changes.
- A Dedicated instance has its own addresses. Saible gives them to you when the instance is handed over.
- Your gateway runs in your network and calls your AI providers directly. Those connections are yours to allow; the installation guide lists them.
- Private connectivity over AWS PrivateLink is available on request.
Where your data is kept: regions and locations.