Dekimu Hub's Designer ships tenant sites at `<slug>.dekimu.site`. From today, any workspace can point a custom domain — `acme.com`, `studio.example.io` — at the same site, with managed SSL, automatic verification, and zero DNS babysitting from us.
From the Designer dashboard, paste the hostname you want to use and we attach it to your site. A status pill — pending, verifying, live, error — updates as DNS and the certificate come up, no refresh needed. The flow is fire-and-forget: close the tab, come back when it's green, point the next domain.
Tenant sites are served at the same speed whether they live at `<slug>.dekimu.site` or at your own apex. Hot paths are cached so the routing decision doesn't add a round-trip on every request. If a domain gets re-assigned to a different workspace, the change is reflected on the next render — no stale-cache surprises, no manual purge.
A custom domain is the moment a tenant stops feeling like they rent a slug and starts feeling like they own a site. The infrastructure has to be invisible — that's the whole point.
DNS propagation is the slowest part of any custom-domain flow, and pretending otherwise just makes the UI lie. We poll on a cadence short enough that a focused user can finish setup in one sitting and long enough to stay quiet between checks. The loop is idempotent — it'll happily re-verify until the domain hits a terminal state, then quiets down.
A few small UX polish items — better error copy when DNS isn't pointing yet, an explicit 'remove domain' confirmation, a real-domain smoke pass — land in Phase 3. Designer's roadmap §Phase 5 flips green when those close.