Vercel Connect Adds Secure Compute for IP-Allowlisted Providers

What changes for connectors

Until now, Connect's provider requests came from shared IP addresses. That is a problem for providers that only accept traffic from approved addresses. According to Vercel, Secure Compute routing solves this by sending those requests through the dedicated static IP addresses of a chosen Secure Compute network.

The routing covers the requests Connect makes to obtain and refresh access tokens. Vercel says your app's direct API routing is unchanged by this setting, so only Connect's own provider traffic takes the new path.

Credential management also stays the same. Vercel states that you don't need to store long-lived provider secrets in your app or build OAuth flows yourself.

How to enable it

Vercel describes the setup as a short sequence in the dashboard. It applies to a supported connector and to all projects that use it.

• Open your connector's Settings in the Vercel dashboard.
• Under Secure Compute Routing, choose an existing network.
• If your provider uses an IP allowlist, add the selected network's displayed IP addresses to it in the provider's settings.
• Save your changes in Connect.

The connector's settings show the selected Secure Compute network and its dedicated IP addresses, which are the ones to add to the provider's allowlist.

Limits and failure behavior

Not every request follows the Secure Compute route. Vercel notes that requests for initial connector creation and all provider discovery requests bypass the selected network and connect directly to providers.

There is also no fallback. If the selected network is unavailable, routed requests fail instead of falling back to Connect's shared IPs. Teams that rely on the feature should keep this in mind, since a network outage would stop token requests rather than silently switching to shared addresses that the provider may not allow.

Vercel points to its Secure Compute routing documentation for configuration details.

What it means for users

For teams whose providers enforce IP allowlists, the update removes a barrier to using Connect with services such as Salesforce and Snowflake. They can allowlist a fixed set of addresses tied to their own Secure Compute network rather than a shared pool, while keeping Connect's existing approach to credentials.