Vercel Daemons can now call services with bindings
Vercel Daemons can now call services in their deployment through service bindings. A daemon declares a binding that names the target service and the environment variable that receives the service's URL, and the daemon calls that URL like any other HTTP endpoint while Vercel handles internal routing, authentication, and TLS and the service stays private.
Why it matters
Daemons can reach other services in the same deployment without exposing those services publicly. Bindings are one-way, since services cannot bind to daemons, and each daemon instance keeps calling the deployment that started it, even after a promotion or rollback.
Who should care
Developers running background workers or long-running processes on Vercel, and teams deploying multi-service applications on Vercel.
What you can do
If you run a Vercel Daemon that needs to call an internal service, declare a service binding on the daemon and read the target service's URL from the environment variable you named, instead of exposing the service publicly.