Simplifyd Cloud

Public networking

Expose your services to the internet with automatic TLS and Simplifyd-assigned domains.

Services on Simplifyd Cloud are private by default — they are not reachable from the internet until you add an ingress. An ingress creates a public endpoint, terminates TLS, and forwards traffic to the port your service listens on.

Adding an ingress

  1. Click a service node on the canvas to open the service panel.
  2. Go to the Settings tab.
  3. Click Add Ingress.
  4. Choose the protocol: HTTP or gRPC.
  5. Enter the port your service listens on internally (e.g. 3000, 8080).
  6. Click Apply in the Apply Changes bar.

Once the deployment is live, the public URL appears at the top of the Settings tab.

Protocols

ProtocolWhen to use
HTTPREST APIs, web apps, webhooks, or any HTTP/1.1 or HTTP/2 workload
gRPCgRPC services that require HTTP/2 framing

Both protocols are served over HTTPS/TLS — plain HTTP and plain gRPC are not exposed directly.

Automatic TLS

Simplifyd Cloud provisions and renews TLS certificates automatically for every ingress endpoint, including custom domains. You do not need to manage certificates or configure certificate authorities.

Assigned domain

When you add an ingress, Simplifyd Cloud assigns a domain of the form:

<service-slug>-<random>.<region>.cloud.simplifyd.com

This domain is available immediately and is also injected into the service as a platform-provided variable:

SIMPLIFYD_PUBLIC_DOMAIN=api-x4k2.eu-west.cloud.simplifyd.com

You can reference this value in other services using a reference variable:

API_URL=https://${{api.SIMPLIFYD_PUBLIC_DOMAIN}}

Multiple ingress endpoints

A single service can have more than one ingress — for example, an HTTP endpoint on port 8080 for your REST API and a gRPC endpoint on port 9090 for an internal RPC interface. Click Add Ingress again to add further endpoints.

Removing an ingress

  1. Open the service panel → Settings tab.
  2. Find the ingress entry and click the trash icon next to it.
  3. Click Apply to confirm.

The public endpoint is deactivated immediately once the changes are applied.

Removing an ingress does not affect the service itself — the container keeps running. Only external traffic is cut off.