Sometimes you don’t want your service to be accessible to everyone on the Internet. For example, you may want to run an internal cache or database that is only accessible to other services in your Render account. In these cases, you can easily create a private service. Private services can speak any protocol (not just HTTP) and can listen on any port.
Here are a few examples to get you started:
- Deploy a private Redis cache
- Deploy Webdis as a web frontend for Redis
- Deploy Sinatra and Sidekiq backed by Redis
Private services are the same as public web services, but they don’t have a publicly accessible HTTPS URL.
Instead, they have a service address, which is a
Here’s an example from Render’s dashboard:
redis private service above has the service address
This means you can connect to it directly from any of your services using hostname
redis at port
6379 — the hostname resolves to a private IP address that only your own services can access.
You may need to append a URL scheme to the private service address depending on your app requirements. For example, apps that rely on Redis as a cache might require you to specify
redis://redis:6379 instead of just