What problem does it solve? Connecting services on Render without exposing traffic to the public internet requires understanding internal hostnames, port rules, region and workspace constraints, and service-type limitations, which are easy to misconfigure and hard to debug. ## Core Features & Use Cases - Private Network Configuration: Explains which Render resource types (Web Services, Private Services, Workers, Cron Jobs, datastores) can send or receive private traffic, including free-tier inbound restrictions. - Service Discovery & Ports: Covers the [hostname]-discovery DNS pattern for multi-instance services, the 75-port limit, reserved ports (10000, 18012, 18013, 19099), and multi-port Web Service behavior. - Troubleshooting Guidance: Diagnoses DNS failures, cross-region and cross-workspace limits, protocol mismatches, and environment isolation issues via references/troubleshooting.md. - Use Case: When a Fastify API on Render cannot reach a background worker or Postgres over the private network, use this Skill to identify that workers have no internal hostname and that datastores must be reached via their internal URL. ## Quick Start Ask how to connect two Render services privately, for example: how do I let my web service call my private backend on Render without exposing it publicly?
