Private networking

Communicate between services within an environment using stable internal hostnames.

Every service in an environment can reach every other service in that same environment directly, without going through the public internet. Simplifyd Cloud assigns each service a private domain — a stable internal hostname that resolves only within the environment's network boundary.

How it works

When a service is created, the platform assigns it an internal hostname and injects it as a platform-provided variable:

SIMPLIFYD_PRIVATE_DOMAIN=my-service.internal.cloud.simplifyd.com

Any other service running in the same environment can open a connection to this hostname on the port the service listens on. No ingress, no public exposure, no firewall rules required.

Connecting to another service

Use a reference variable to wire one service's address into another service's configuration at deployment time:

# In your "worker" service variables:
API_HOST=${{api.SIMPLIFYD_PRIVATE_DOMAIN}}
API_PORT=3000

At runtime, API_HOST resolves to the internal address of the api service. Traffic flows entirely within the cluster.

Database connections

Managed Postgres services use the same mechanism. The DATABASE_URL variable Simplifyd Cloud injects for a Postgres service uses the private domain internally, so your application connects without any public exposure:

DATABASE_URL=${{postgres.DATABASE_URL}}

You can reference this directly from any service in the same environment.

Private vs public networking

	Private	Public
Reachable from	Same environment only	Anywhere on the internet
TLS	Cluster-internal (transparent)	Automatic HTTPS/TLS termination
Egress billing	Not billed	Standard egress rates apply
Setup required	None — automatic	Add ingress in service Settings

Environment isolation

Private networking is scoped to an environment. A service in production cannot reach a service in staging over the private network, even within the same project. This isolation is enforced at the network layer and cannot be disabled.

If you need a service in one environment to call a service in another environment, expose the target service with a public ingress and connect over HTTPS.

Platform variables

Simplifyd Cloud injects the following networking-related variables automatically into every service deployment:

Variable	Description
`SIMPLIFYD_PUBLIC_DOMAIN`	The public hostname assigned to the service (only present when an ingress is configured)
`SIMPLIFYD_PRIVATE_DOMAIN`	The internal hostname for service-to-service communication within the environment