Networking
How services are exposed to the internet and how they communicate with each other.
Every service on Simplifyd Cloud lives inside an environment. Networking in Simplifyd Cloud has two dimensions: how traffic reaches your services from the outside world, and how services talk to each other internally.
Public networking
Services are private by default. To make a service reachable from the internet, you add an ingress — an HTTP or gRPC endpoint with automatic TLS termination. Simplifyd Cloud assigns a domain immediately; you can attach your own domain at any time.
Learn about public networking →
Private networking
Every service automatically gets a stable internal hostname that other services in the same environment can use to reach it. Internal traffic never leaves the cluster and is not billed as egress.
Learn about private networking →
Custom domains
Replace the Simplifyd-assigned domain with your own by pointing a DNS CNAME at the platform. TLS is provisioned automatically.
Zerodata Proxy
Route traffic through Simplifyd Cloud's global edge network to reduce latency and inter-service egress costs.
Networking at a glance
| Concept | What it is |
|---|---|
| Ingress | An HTTP or gRPC endpoint that exposes a service to the internet with automatic TLS |
| Private domain | A stable internal hostname for service-to-service communication within an environment |
| Custom domain | A user-supplied FQDN attached to an ingress endpoint |
| Zerodata Proxy | An edge proxy that routes traffic through Simplifyd Cloud's global network |
SIMPLIFYD_PUBLIC_DOMAIN | Platform variable containing the public hostname assigned to a service |
SIMPLIFYD_PRIVATE_DOMAIN | Platform variable containing the internal hostname for a service |
