Custom domains

Every web service you deploy gets an instant URL on computesphere.app — for example, silver-cobra.computesphere.app. A custom domain lets you serve that same web service from your own domain (example.com or app.example.com) instead, with SSL handled for you.

You add the domain in ComputeSphere, then add one DNS record at your domain provider that points it back to your web service. Once the record resolves, ComputeSphere issues and renews the SSL certificate automatically — there is no certificate file to upload and no verification record to copy.

note

Custom domains apply to web services — the service type that serves HTTP traffic on a public URL. Other service types (such as cron jobs) don't have a public address.

How it works

1. Add the domain to your service in ComputeSphere (Console or API).
2. Point your domain at your service by adding a DNS record at your provider — a CNAME for a subdomain, or the apex equivalent for a root domain (see Choose your record).
3. ComputeSphere detects the domain, issues an SSL certificate, and starts serving your service over HTTPS. The certificate renews automatically for as long as the record stays in place.

Your traffic is always served through ComputeSphere's edge, which provides TLS termination and DDoS protection — you never point your domain directly at an origin server.

Add the domain

1. Open the Console → Domains, or go to a service and open its Domains section.
2. Click Add custom domain.
3. Enter the domain — for example www.example.com or example.com — and click Add domain.
4. ComputeSphere shows the DNS record(s) to create. Add them at your domain provider (next section), then return; the status moves from Validating to Active once the record resolves and the certificate is issued.

Prefer to bring your own certificate?

When adding the domain, enable Use custom SSL certificate and paste your certificate and private key. ComputeSphere then serves your certificate instead of issuing one. Most customers leave this off and let ComputeSphere manage SSL automatically.

Choose your record

Which record you add depends on whether you're connecting a subdomain or a root (apex) domain.

Connecting	Record to add	Value
Subdomain — www.example.com, app.example.com, api.example.com	CNAME	your service URL, e.g. silver-cobra.computesphere.app
Root / apex — example.com	depends on your provider — see below	your service URL, e.g. silver-cobra.computesphere.app

Subdomains are simplest

A subdomain is a single CNAME record and works on every DNS provider:

Type    Name    Value
CNAME   www     silver-cobra.computesphere.app

That's the whole setup — no other records.

Root / apex domains

The DNS standard does not allow a CNAME on a root domain (example.com), so the steps depend on your provider:

• Your provider supports ALIAS / ANAME / CNAME flattening to an external hostname (e.g. Cloudflare, DNSimple, DNS Made Easy): point the apex straight at your service URL with an ALIAS/flattened record. The apex is served directly.
• Your provider does not (e.g. GoDaddy, Namecheap): make www your primary address (a CNAME, as above) and redirect the root to it using your provider's domain-forwarding feature. Visitors who type example.com are sent to https://www.example.com.

note

We recommend using www (or another subdomain) as your primary address and redirecting the root domain to it. It works on every provider with no extra records.

Configure your DNS provider

Step-by-step guides for the most common providers:

• Namecheap
• Cloudflare
• Other providers (GoDaddy, DNSimple, …)

Automatic SSL

ComputeSphere provisions and renews an SSL certificate for every custom domain automatically once your DNS record resolves — and for your default computesphere.app URL. HTTP requests are redirected to HTTPS. You don't manage, upload, or renew anything (unless you chose to bring your own certificate).

Domain status

In Console → Domains, each domain shows a status:

Status	Meaning	What to do
Validating	ComputeSphere is waiting for your DNS record to resolve and is issuing the certificate	Add the record (if you haven't), then wait — DNS can take a few minutes to a few hours to propagate. Use Verify now to re-check.
Active	The domain is live and served over HTTPS	Nothing — you're done

If a domain stays in Validating, the most common cause is the DNS record not being in place or not yet propagated. Double-check the record name and value against the provider guide.

Multiple domains

You can connect more than one custom domain to the same service — for example a root domain and its www, or several brands pointing at one app. Each is added the same way and gets its own automatic certificate.

Wildcard domains

Wildcard custom domains (*.example.com) are not yet self-serve. If you need one, contact support.