render-private-services

Configure private services on Render without public URLs.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/renderinc/render-codex-plugin --skill render-private-services
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-private-services
Source: https://github.com/renderinc/render-codex-plugin/tree/main/skills/render-private-services
Command: npx skills add https://github.com/renderinc/render-codex-plugin --skill render-private-services

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Private services are internal-only apps that have no public URL and are reachable only by other Render services on the same private network. Use when you need internal APIs, microservices, gRPC servers, sidecars, or any component that should not face the internet.

Core Features & Use Cases

  • No public URL: private services communicate over the private network, keeping traffic inside your Render workspace.
  • Port-based communication: services listen on configured ports and can be wired with fromService for internal dependencies.
  • Lifecycle parity: same build/deploy lifecycle as web services, with support for disks, scaling, and Docker runtimes.

Quick Start

Define a private service in your Blueprint with type: pserv, then deploy to the same private network.

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 microservice on Render without exposing a public URL?

To deploy an internal microservice without a public URL, use a private service. It runs on Render's private network, keeping traffic inside your workspace and accessible only to other Render services.

Can I run a gRPC server on Render's private network?

Yes, you can run a gRPC server on Render's private network by deploying it as a private service. It listens on configured ports and communicates internally without public internet exposure.

What's the best way to secure internal APIs on Render from public internet access?

The best way to secure internal APIs is deploying them as private services. They have no public URL and are reachable only by other services on the same private Render network.

Does a private service on Render support the same lifecycle and scaling as a web service?

Yes, a private service supports the same build and deploy lifecycle as web services. It includes support for disks, scaling, Docker runtimes, and port-based communication wiring.

How do I configure private network routing for internal dependencies in a Render Blueprint?

Configure private network routing by defining a service with type: pserv in your Blueprint. Use fromService to wire internal dependencies and deploy to the same private network.