render-private-services
Configures Render private services—internal-only apps that accept traffic exclusively from other Render services over the private network. Use when the user needs an internal API, microservice, gRPC server, sidecar, or any service that should not be publicly accessible. Also use when choosing between a private service and a background worker. Trigger terms: private service, pserv, internal service, internal API, microservice, gRPC, not public, private network service.
Install
With your agent
Install OMGSkills skill "render-oss/render-plugin-claude-code:skills/render-private-services" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/render-oss/render-plugin-claude-code /tmp/render-plugin-claude-code && ln -s /tmp/render-plugin-claude-code/skills/render-private-services ~/.claude/skills/render-private-servicesFrom README
Render Private Services Private services are identical to web services except they have no public URL. They are reachable only by other Render services on the same private network (same region + workspace). Use them for internal APIs, microservices, gRPC servers, sidecar processes, and anything that should never face the internet. When to Use Building an internal API or microservice behind a public gateway Running a gRPC, TCP, or other non-HTTP server that only your services call Deploying infrastructure components (Elasticsearch, ClickHouse, RabbitMQ) Choosing between a private service and a background worker For public-facing HTTP services, use render-web-services. For services that don't receive any traffic, use render-background-workers. Before configuring or troubleshooting private connectivity, read references/private-networking.md. Before attaching or changing a persistent disk, read references/persistent-disks.md.
More from this repo
render-background-workers
Sets up and configures background workers on Render for queue-based job processing.
render-blueprints
Authors and validates render.yaml Blueprints for Render infrastructure.
render-cli
Installs and uses the Render CLI for deploys, logs, SSH, psql, Blueprint validation, and automation.