Connect your domain
Your conference is always available at your-event.buildaconf.com. On the Pro or Custom plan you can use your own domain, e.g. conf.yourcompany.com. You buy the domain yourself (any registrar) and connect it in 3 steps.
1. Add the domain in the dashboard
Event dashboard → Domain → enter the hostname (e.g. conf.yourcompany.com) → Add. You will see two DNS records.
2. Create the DNS records at your registrar
| Type | Name / Host | Value |
|---|---|---|
| CNAME | conf | sites.buildaconf.com |
| TXT | _buildaconf.conf | bac-verify=… (copied from the dashboard) |
TTL: auto or 300 s. Most registrars append the domain automatically: enter just “conf”, not “conf.yourcompany.com”.
Where to find it at each registrar
| Cloudflare | Dashboard → your domain → DNS → Records → Add record. Set the CNAME to “DNS only” (grey cloud). |
| GoDaddy | My Products → Domain → DNS → Manage DNS → Add New Record. |
| Namecheap | Domain List → Manage → Advanced DNS → Add New Record. In “Host” enter only the subdomain (e.g. conf). |
| Porkbun | Domain Management → Details → DNS Records → add the record. |
| Squarespace Domains (ex Google Domains) | Domains → your domain → DNS → Custom records → Add record. |
| NIC.bo / registradores locales | If the panel has no CNAME support, delegate the domain to Cloudflare (free) by changing nameservers, then follow the “Cloudflare” row. |
Root domain (yourcompany.com without a subdomain)?
Many registrars do not allow a CNAME at the root. Options: use a subdomain (www or conf), use an ALIAS/ANAME record if your registrar offers it, or delegate DNS to Cloudflare, which flattens the CNAME automatically.
3. Verify
Go back to Dashboard → Domain and press “Check”. DNS propagation takes minutes to 24 h. Once the status is “Active” we issue the HTTPS certificate automatically (Cloudflare for SaaS) and your site and app are live on your domain.
The app (PWA) lives at https://your-domain/app. If the event is downgraded to Free, the site falls back to the platform subdomain.