render-private-services

Configures Render private services for internal-only APIs, microservices, and gRPC servers.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/DingJun1028/esggo-kv --skill render-private-services-dingjun1028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: render-private-services
Source: https://github.com/DingJun1028/esggo-kv/tree/main/.agents/skills/render-private-services
Command: npx skills add https://github.com/DingJun1028/esggo-kv --skill render-private-services-dingjun1028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying internal APIs, microservices, or gRPC servers that must never face the public internet requires correct private networking configuration, which is easy to get wrong. This Skill guides the setup of Render private services so internal workloads are reachable only by other services on the same private network. ## Core Features & Use Cases - Private Service Configuration: Defines type: pserv services in Render Blueprints with build commands, start commands, regions, and plans. - Service-to-Service Wiring: Connects services using fromService with host, port, or hostport properties so a public gateway can reach internal services. - Protocol Flexibility: Supports HTTP, gRPC, TCP, WebSocket, and custom binary protocols on any non-restricted port. - Use Case: A team deploys a public gateway web service plus internal user-service and billing-service microservices; the gateway receives USER_SERVICE_URL and BILLING_SERVICE_URL via fromService wiring and calls them over the private network. ## Quick Start Ask the assistant to create a Render Blueprint for an internal API private service wired to a public gateway using fromService hostport references.

Frequently Asked Questions about render-private-services

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an internal API on Render without a public URL?▼

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 at `<service-name>:<port>` by other services in the same region and workspace.

What is the difference between a Render private service and a background worker?▼

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.

How do I connect a web service to a Render private service?▼

Use `fromService` in the consumer's env vars with the private service name, `type: pserv`, and `property: hostport`. Render injects the internal `host:port` address, which your code prefixes with the protocol, such as `http://`.

Can Render private services run gRPC or non-HTTP protocols?▼

Yes, private services support any protocol including gRPC, TCP, WebSocket, and custom binary protocols on any non-restricted port. Bind your server to 0.0.0.0 and share the hostport with consumers; no TLS is needed on the encrypted private network.

Why is my Render private service unreachable from other services?▼

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