Runex

Docs

Custom domains on Runex

Every deployment gets a platform URL on *.runex.cloud. For production brands and client apps, attach your own domain — for example app.example.com — by pointing a CNAME to cname.runex.cloud.

Platform domain vs custom domain

TypeExampleNotes
Platform URLhttps://<slug>.runex.cloudCreated with the deployment; HTTPS provided
Custom domainapp.example.comCNAME to cname.runex.cloud, then attach in Runex

Steps

  1. Deploy your application so a Runex deployment exists.
  2. In your DNS provider, create a CNAME record for the hostname you want (for example app) targeting cname.runex.cloud.
  3. In the Runex dashboard, add the custom domain to the deployment and wait for DNS propagation / HTTPS provisioning.
  4. Verify in a browser: https://app.example.com should serve your app.

DNS example

# Hostname: app.example.com
Type:  CNAME
Name:  app
Value: cname.runex.cloud
TTL:   300 (or provider default)

HTTPS

Runex provides HTTPS for supported public deployments, including custom domains once they are correctly attached. We do not use vague encryption marketing claims — TLS is the concrete control.

Troubleshooting

  • Domain not resolving: confirm the CNAME target is exactly cname.runex.cloud and wait for DNS TTL.
  • Wrong site: ensure the domain is attached to the intended deployment in the dashboard.
  • Apex domains: some DNS providers need ALIAS/ANAME for apex (example.com). Prefer a subdomain when unsure, or follow your DNS provider’s CNAME-flattening guidance.

Related