Guide
Custom domains for hosted apps
Every hosted app ships on an assigned Layerbase domain served over HTTPS. You can also point your own domain at it. Add a CNAME record at your DNS provider, and Layerbase issues the TLS certificate and routes traffic for you. Once the domain is live, the app's login and install snippet switch to it automatically.
Where it lives
Open the app in your cloud dashboard and go to the Domain tab. The assigned Layerbase domain is shown at the top; the Custom domain card below it is where you add your own.
Setup steps
Enter the domain you want to use (for example replay.acme.com) and click Add domain. The card then shows a CNAME record to create. Setup is CNAME-only on purpose: a CNAME follows the app if it ever moves to another server, and it never publishes the underlying box IP.
At your DNS provider, create the CNAME with the values shown on the card. Put only the subdomain in the Name field, not the full host:
Type: CNAME
Name: replay # just the subdomain, not replay.acme.com
Value: <shown on the card>
TTL: lowest available (3600, 30m, or 1h)Entering the full host in the Name field creates a doubled record (like replay.acme.com.acme.com) that will not verify. For a root or apex domain, use @ as the Name. Field labels vary by provider: Squarespace calls the target Alias Data, and some providers append your zone to the Name for you. After saving the record, return to the card and click Refresh status.
Automatic TLS
You do not request or upload a certificate. Once the CNAME verifies, Layerbase issues the TLS certificate for the domain and keeps it renewed. Issuing the certificate can take a few minutes; use Refresh status to re-check.
The four states
The card shows one status at a time. DNS changes can take a few minutes to propagate, so a fresh domain sits in the first two states for a bit before it goes live.
The domain is added but the CNAME has not been seen yet.
What to do: Create the CNAME shown on the card at your DNS provider, then click Refresh status. Give propagation a few minutes.
DNS is verified and Layerbase is issuing the TLS certificate.
What to do: Wait a few minutes and click Refresh status. No DNS change is needed at this point.
The domain is live over HTTPS. The app's login and install snippet now use the custom domain.
What to do: Nothing. Point your users at the custom domain.
Something went wrong finishing setup (for example a conflicting record or a certificate issue).
What to do: Click Refresh status to retry. If it stays in error, remove the domain and add it again.
What changes once live
When the domain reaches Active, the app serves on it over HTTPS and the install snippet updates to reference the custom domain, so you do not have to edit anything you already embedded. For a Session Replay app, the recorder snippet and app login switch to the custom domain too. The assigned Layerbase domain keeps working as well.
Removing a domain
Click Remove on the card to detach the custom domain. The app falls back to its assigned Layerbase domain. Removing and re-adding is also the way to clear a stuck Error state: remove the domain, fix the DNS record if needed, then add it again from scratch.