Custom domains
Point your own domain at a Vorynza-hosted app.
Every app gets a free your-app.vorynza.cloud subdomain the moment it's first deployed. Add your
own domain on top of it whenever you're ready — the platform subdomain keeps working
either way.
Adding a domain
From your app's Domains tab, enter the hostname you want to use (for example
app.example.com) and add it. Vorynza shows you the DNS records to create:
| Record | Type | Purpose |
|---|---|---|
| Routing | CNAME | Points your domain at Vorynza's edge |
| SSL | CNAME | Lets Vorynza's certificate authority validate you own the domain |
Create both records with your DNS provider, then Vorynza verifies them and issues a TLS certificate automatically — no action needed on your end once the records exist. This typically takes a few minutes, occasionally longer depending on DNS propagation.
One certificate per domain
Each custom domain gets its own dedicated routing setup and certificate. Adding a second
domain never affects a domain (or your *.vorynza.cloud subdomain) that's already working.
Renaming a domain
You can change your app's default *.vorynza.cloud subdomain from the app header. The change
takes effect within a few seconds — your existing custom domains are unaffected.
Removing a domain
Delete a domain from the Domains tab. This stops routing traffic for that hostname and cleans up its certificate; your platform subdomain and any other custom domains keep working.
Which deployment a domain serves
Custom domains always point at whichever deployment is currently promoted to production — the
same one your *.vorynza.cloud subdomain serves. See Deployments for
how promotion and rollback work.