Custom domains let customers access the platform through your own branded URL such as `app.yourbrand.com` instead of a default subdomain. It is one of the clearest white-label upgrades because the brand shift is immediate and visible.
Custom domains require an active paid subscription and are not available during trial.
Choose the right setup type
- Subdomain setup is the recommended path for most agencies because it leaves the main website untouched
- Full domain setup is only for agencies that want the platform to power the whole domain and the built-in website
If you already have a live marketing website on the root domain, do not point the full domain at the platform unless you are intentionally replacing that site.
Add the DNS records
If you use Cloudflare, set the record to DNS only while the SSL certificate is being issued. Proxied mode can prevent validation from completing properly.
| Setup type | Records |
|---|---|
| Subdomain | Add one A record for the subdomain pointing to 49.13.0.216 |
| Full domain | Add an A record for @ to 49.13.0.216 and a CNAME for www pointing to the root domain |
Verify and wait for SSL
After saving the domain, click `Verify DNS Records`. If propagation has not finished yet, save and come back later. Once verification passes, the platform configures the domain and requests the SSL certificate automatically.
SSL usually completes within a few hours, though it can take up to a full day in slower cases.
What to check if it does not validate
- Wait for propagation if records were added recently
- Remove conflicting old A or CNAME records for the same host
- Confirm the target values are exact
- Check Cloudflare proxy status if you use Cloudflare