What this is
Sana connectors can run over a dedicated private network with a fixed, static outbound IP address - instead of the shared, dynamically-changing IPs used by default. This is especially useful for on-premise systems, such as Jira Data Center, where access is only granted to specifically whitelisted IP addresses.
Why this matters
Many IT and security teams require that any external system connecting to their internal tools comes from a known, unchanging IP address, so they can lock down firewall rules instead of opening access broadly. Previously, requests from Sana's connectors could originate from a range of IPs that changed over time. With this optional feature, requests from your connectors originate from a static IP address that's unique to your organization, so you can whitelist access to sensitive resources with confidence that requests will only come from your own Sana environment.
How it works
A dedicated private network with a static outbound IP is provisioned for your organization.
Once set up, all outbound requests from the connector - both when testing and when running in production - originate from this static IP.
You (or your IT team) can take this IP address and add it to your on-premise system's allowlist using so all requests from that connector will come from this address.
How to get started
There is no way to configure this in the product for workspace owners, reach out to your engagement manager if you are interested in this functionality.
FAQ
Q: Can I change or choose my VPC’s IP address?
A: No. IP addresses are assigned by Sana and are not changeable.