Render private networking

Render’s private network lets services talk to each other without exposing traffic on the public internet. Use this skill when users need internal connectivity, discovery across scaled instances, or correct URL/port behavior for Blueprints and the Dashboard.

When to Use This Skill

• Designing or debugging service-to-service traffic on Render
• Questions about internal hostnames, internal URLs, or Connect > Internal in the Dashboard
• Service discovery across multiple instances (custom load balancing, mesh-style setups)
• Port limits, reserved ports, or multi-port web services (public vs private)
• Free-tier web services and who can send vs receive private traffic
• Environment isolation (with a Pro workspace or higher) or AWS PrivateLink for private egress/ingress patterns

For step-by-step architecture examples and Blueprint patterns, see references/communication-patterns.md. For failure modes and fixes, see references/troubleshooting.md.

Private Network Basics

Private connectivity is available only when all of the following hold: