Vercel Connect now supports Secure Compute
By Steven Van ·
Connectors can send token and provider requests from a team's static Secure Compute IPs, for providers like Salesforce and Snowflake that use allowlists.
Vercel Connect can now route its provider requests through a Secure Compute network, so connectors can reach providers that restrict access by IP allowlist, such as Salesforce and Snowflake. The change was announced on 15 October 2026.
What the routing covers
With routing enabled, Connect's provider requests use the selected network's dedicated static IP addresses instead of Connect's shared IPs. Requests to obtain and refresh access tokens follow that route. The setting does not change how an app's own direct API calls are routed.
Credential management stays the same, so there is no need to store long-lived provider secrets in the app or build OAuth flows by hand.
Setting it up
A Secure Compute network must already exist for the team and have finished provisioning. Then, for a supported connector:
- Open the connector's Settings in the Vercel dashboard.
- Under Secure Compute Routing, choose a network from Secure Compute Network.
- If the provider uses an IP allowlist, add the network's displayed IP addresses to it in the provider's settings. Clicking an address copies it.
- Save the changes in Connect.
The setting applies to the connector and all projects that use it. Selecting None and saving restores direct egress without deleting the network.
Limits
- Routing is available for supported team-owned connectors. API key connectors don't support it.
- Requests for initial connector creation and all provider discovery requests bypass the selected network and connect directly to providers.
- If the selected network is unavailable, routed requests fail instead of falling back to Connect's shared IPs.