Networking
How services are exposed to the internet and how they communicate with each other.
Networking has two halves: how traffic from the internet reaches your services, and how your services talk to each other privately.
Public networking
Services are private by default. To make a service reachable from the internet, you add an ingress. HTTP and gRPC ingress endpoints get automatic TLS and an assigned domain. TCP and UDP ingress endpoints expose a public port directly.
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 stays within the environment and is not billed as egress.
Learn about private networking →
Cross-project access
Grant another project in your workspace access to one private port on a service, without exposing it publicly.
Learn about cross-project access →
TCP and UDP endpoints
Expose a non-HTTP service on a public port, and restrict which addresses may connect.
HTTP Gateway
Put several services behind one hostname and route by path prefix.
Learn about the HTTP Gateway →
Custom domains
Replace the Simplifyd-assigned domain with your own by pointing a DNS CNAME at the platform. TLS is provisioned automatically.
Wildcard custom domains
Attach a single *.example.com domain to cover every subdomain with one certificate. Requires two DNS records: a * CNAME for traffic and an _acme-challenge CNAME for certificate validation.
Learn about wildcard domains →
Zerodata Proxy
Route traffic to an app hosted anywhere through Simplifyd Cloud so that end users on supported mobile networks are not charged for the data.
Networking at a glance
| Concept | What it is |
|---|---|
| Ingress | A public HTTP, gRPC, TCP, or UDP endpoint for a service |
| Private domain | A stable private hostname for service-to-service communication within an environment |
| Custom domain | Your own domain attached to an ingress endpoint |
| Allowed sources | A list of CIDR ranges permitted to reach a TCP or UDP port |
| Private access grant | Permission for another project to reach one private port on a service |
| Wildcard domain | A *.example.com custom domain covering all subdomains under a single TLS certificate |
| Zerodata Proxy | A proxy that makes your site data-free for users on supported mobile networks |
SIMPLIFYD_PUBLIC_DOMAIN | Platform variable containing the public hostname assigned to a service |
SIMPLIFYD_PRIVATE_DOMAIN | Platform variable containing the private hostname for a service |
