Skip to main content

Domains

The Domains tab is the account-wide view of every web service's address — its automatic computesphere.app URL and any custom domains you've connected — along with each domain's SSL status.

What you can do here​

ActionWhat it does
See the auto URLEvery web service has a d-<name>-<id>.computesphere.app URL from the first deploy (e.g. d-silver-cobra-ab12c.computesphere.app).
Connect a custom domainAttach www.example.com or app.example.com to a service. Status moves to Active once DNS resolves and the certificate issues.
Check SSL statusCertificates issue automatically once DNS resolves, and renew on their own. No manual step.
SearchType a service name or domain to jump straight to it.

Add a custom domain​

  1. Open the Domains tab, or open a service and go to its Domains section.
  2. Click Add custom domain.
  3. Enter your domain — for example www.example.com — and click Add domain.
  4. The console shows the DNS record to create. Add it at your domain provider; the status flips to Active once the record resolves and the certificate is issued.

For provider-specific walkthroughs (Namecheap, Cloudflare, GoDaddy, others) see Custom domains.

Limits​

  • Apex domains (example.com, without www) need provider support for ALIAS / ANAME records, or the right www-primary pattern. The Custom domains guide covers what works per registrar.
  • DNS propagation takes time. Status can stay at Waiting for DNS until your record propagates; ComputeSphere checks again after 2, 5 and 10 minutes, and Verify now checks at once.
  • Certificate issuance follows DNS. Until the domain resolves to the ComputeSphere edge, the certificate won't issue. The two states aren't independent.
  • One owner per domain. A custom domain attaches to exactly one service or environment at a time. To move it, detach it from the current one first.
  • 50 custom domains per account. A wildcard counts as one. Contact us to increase quota.

What's next​

  • Custom domains — registrar-specific DNS setup, apex vs www, troubleshooting.
  • Networking — IP allowlists and public vs private network controls.
  • Architecture — how the edge handles your domains' traffic.