Custom domains were the one feature that shipped complete and then got hidden behind a flag before a single customer could touch it. Not because it doesn't work - because I realized "verified" and "actually live" are two different problems on shared hosting.
The straightforward half
A performer who wants `theirname.com` instead of a subdomain adds it in the admin panel, which writes a row to a custom_domains table (one domain per user, a verified flag defaulting to false). Verification is a DNS lookup - PHP's dns_get_record() checking whether the domain's A record points at this server's IP. Only once that comes back true does the domain start routing to their tenant page.
That lookup is a blocking network call with no timeout parameter, which matters more than it sounds like it should: someone waiting on DNS propagation, refreshing the page every few seconds, would otherwise pin a PHP worker for however long the lookup takes on every single refresh. The fix was throttling the automatic check to once a minute per user, while an explicit "Check DNS now" button always does a real lookup on demand.
The problem no code could fix
DNS pointing at the right IP doesn't mean Apache will actually serve that domain, and it doesn't get the domain an SSL certificate. On shared cPanel hosting, both of those require the domain to be manually added as a Parked or Addon Domain in cPanel first - a real, per-customer, human step on my end that no amount of application code eliminates on this hosting tier.
Which means a customer could have done everything right - added the DNS record, seen "Verified" light up green - and still hit a 404 or a certificate warning, because the one step that actually makes it work hadn't happened yet on my side. That gap is exactly the kind of thing worth not shipping past. The feature is now hidden behind a flag until I'm ready to onboard someone: the admin dashboard card and the domain page itself both disappear cleanly rather than presenting a working-looking form that quietly doesn't work yet.