Documentation

Private Services

Host apps that only accept traffic from your other services.

Deployra private services are just like web services, with one exception: private services aren't reachable via the public internet. They do not receive a deployra.app subdomain.

Private Service

service-name.service

No Public Access

Internal network only

Important

Private services are reachable by your other Deployra services on the same private network! This means they're perfect for services that only your own infrastructure needs to talk to. Private services can listen on almost any port and communicate using any protocol.

Use cases for private services

Search engines

Deploy Elasticsearch or other search tools

Run search engines like Elasticsearch that only need to be accessed by your application servers, not by end users directly.

Analytics databases

Deploy ClickHouse and similar analytics tools

Run analytics databases that process internal data and don't need to be exposed to the public internet.

Internal APIs

Backend services that only serve your application

Deploy internal APIs and microservices that should only be accessible to your other services, not to the outside world.

Background processors

Handle jobs and process queues privately

Run background task processors, job queues, or other services that don't need direct user interaction.

Connecting to private services

Within your Deployra private network, services can reach each other using internal hostnames, which follow this format:

service-name.service

For example, if you have a web service named "api" and a private service named "search", your api service can connect to the search service using "search.service" as the hostname.

Example: Connecting to Elasticsearch

If you deploy Elasticsearch as a private service named "elasticsearch", your web services would connect to it using this connection string:

http://elasticsearch.service:9200

Where 9200 is the standard port that Elasticsearch listens on.