ST-2026-167 · Runtimes & developer platforms
Vercel Service Bindings enter beta for private service calls
Vercel introduced Service Bindings in beta on 1 July 2026 for secure service-to-service calls within the same deployment, with Vercel handling internal routing, authentication and TLS.
Previous state
Vercel multi-service applications relied on public exposure or separately managed service-to-service routing and trust configuration.
Current state
A declared Service Binding injects an internal URL and Vercel handles internal rewrite, routing, authentication and TLS for the bound service call.
Affected users
Who needs to care
Vercel multi-service deployments that need one service to call another without exposing the target through a public route.
Required response
What to do
Evaluate Service Bindings for internal service calls and account for Service Requests and Fast Origin Transfer billing dimensions.
Evidence boundary
What the source does not prove
The feature is beta; a service is reachable only when exposed publicly or privately through a binding, and the announcement does not make every service private by default.
Lifecycle history
Dated event sequence
- Service Bindings beta announced
Vercel introduced managed internal routing, authentication and TLS for same-deployment service calls.
Evidence ledger
First-party sources
- 01Vercel — Secure internal communication between services (beta)
Official Vercel changelog · 2026-07-01
Open official source ↗