Custom Domains

Every app gets a managed *.watasuhost.com URL. Production apps usually want their own.

Custom domains attach to public web processes — the ones named web or *-web. Watasu provisions and renews TLS certificates for you.

Add a domain

watasu domains:add www.example.com --app my-app

If your app has more than one public web process, point the domain at the right one:

watasu domains:add admin.example.com --process admin-web --app my-app

Watasu prints the DNS target you need to configure with your DNS provider — typically a CNAME record (or an ALIAS/ANAME for apex domains, depending on your provider).

Wait for verification

watasu domains:wait www.example.com --app my-app

This waits for DNS verification. Certificate issuance is a separate step; check the domain’s TLS status in the dashboard before using its HTTPS URL.

Inspect

List all domains on an app:

watasu domains --app my-app

Show details for one domain (status, target, attached process):

watasu domains:info www.example.com --app my-app

Remove

watasu domains:remove www.example.com --app my-app

Apex and wildcard domains

• Apex (example.com) — supported. Use ALIAS, ANAME, or your DNS provider’s apex flattening, following the target Watasu prints.
• Wildcard (*.example.com) — supported. Powerful, but every subdomain under the wildcard now resolves to that one app, so plan accordingly.

TLS

TLS is managed end-to-end. You don’t upload certificates and you don’t renew them. As long as DNS keeps pointing at the right target, the certificate keeps renewing.

DNS can start routing to Watasu before the certificate is ready. During that window, HTTPS connections are rejected instead of receiving a certificate for another hostname. Your browser may show a connection error. HTTPS starts working when a matching, valid certificate is available; certificate validation over HTTP continues during this period.