Currently, Reverb apps on Ploi Cloud are only reachable via the default Ploi-provided domain. It would be great if we could attach our own (sub)domain to the Reverb endpoint — e.g. ws.myapp.com — just like we can for regular web apps.

Why this matters:

• Branding & trust: browser dev tools and CSP reports show the websocket host to end users and security reviewers; a first-party domain looks professional and avoids questions about an unfamiliar third-party hostname.
• Stable configuration: with our own domain, the client-side Echo/Reverb config never has to change if the underlying Ploi endpoint ever changes — the CNAME absorbs it.
• CSP & cookies: a first-party subdomain simplifies connect-src CSP rules and any same-site cookie considerations.

Expected behavior: add a custom domain to a Reverb service in the Ploi Cloud panel, point a CNAME at the Ploi endpoint, and have TLS provisioned automatically (as with web apps). The websocket upgrade should work transparently on the custom domain.