render-private-services

Create a private service by setting `type: pserv` in your Render Blueprint. Private services have no public URL or onrender.com subdomain and are reachable only by other Render services in the same region and workspace via `<service-name>:<port>`.

A private service binds to a port and receives traffic from other services on the private network, while a background worker receives no traffic and typically pulls work from a queue. If your process listens on a port, use a private service; if it only consumes jobs, use a worker.

Yes, private services support any protocol including gRPC, TCP, WebSocket, and custom binary protocols. Bind your server to 0.0.0.0 on any non-restricted port and let consumers connect via the service's internal hostport.

Reference the private service in your Blueprint using `fromService` with `type: pserv` and a property of `host`, `port`, or `hostport`. Render injects the internal address as an environment variable, which your code prefixes with the protocol, such as `http://`.

Common causes include binding to 127.0.0.1 instead of 0.0.0.0, not binding to any port, or the services being in different regions or workspaces. Private networking only works between services in the same region and workspace.