Private networking for Vercel Daemons

Hi, I wanted to ask if you plan on supporting inbound traffic to Vercel Daemons in the near future.

I'm building an eCommerce platform with a fully Effect.ts backend currently deployed on Railway, and I want to move it to Vercel. My API can run as Vercel Functions, but I also use Effect Cluster heavily (for entities, singletons, workflows and cron jobs), which needs long-running runners. Daemons fit that, but the cluster needs private networking:

Functions -> Daemon: service bindings that can target a Daemon.
Per-instance addressing: each Daemon instance reachable at its own private host:port, and able to discover that address at startup. Cluster runners register their own address and route messages to the specific instance that owns a shard.
Daemon <-> Daemon: instances able to reach each other privately, including during rollouts when old and new instances overlap.

I'd love to do this migration because I'm already heavily invested in the Vercel ecosystem for everything else, like Next.js for the dashboard and storefronts, Vercel Blob for storage and even my domains.

Hi, I wanted to ask if you plan on supporting inbound traffic to Vercel Daemons in the near future.

Functions -> Daemon: service bindings that can target a Daemon.
Per-instance addressing: each Daemon instance reachable at its own private host:port, and able to discover that address at startup. Cluster runners register their own address and route messages to the specific instance that owns a shard.
Daemon <-> Daemon: instances able to reach each other privately, including during rollouts when old and new instances overlap.