Before you start
You can serve a published app at a subdomain you own, such as booking.example.com, with HTTPS set up for you. The app’s original address keeps working.
- Publish the app first.
- You need to be the app’s owner or an admin.
- Custom domains are part of paid plans, and need access to your domain’s DNS settings.
Connect a domain
- Open the app’s Dashboard and find Custom domain.
- Enter the subdomain and select Connect domain.
- Atomic shows the DNS records to add: a CNAME record that points your subdomain at Atomic, and a TXT record that proves the domain is yours.
- Add both records at your DNS provider. Use DNS-only mode while connecting: if your provider offers a proxy, such as Cloudflare’s, keep it off until the domain is connected.
Some DNS providers add your root domain to record names automatically, so enter only the part they ask for. Keep the TXT record in place until the domain is connected.
Follow the connection
Atomic checks the records automatically and shows the status and the next step. Check again asks for a check now; it can be used every 30 seconds. The Connection timeline records what happened and when.
Once connected, the status shows when the connection started and how long the certificate is valid. Renewal is automatic. Open domain opens the app at its new address.
Remove a domain
Remove domain disconnects it. The app stays available at its original address. You can then delete the DNS records at your provider.
If your plan changes to one without custom domains, a domain that is already connected keeps working; only connecting a new one is refused.