Skip to main content
Every deployed HTTP workload gets a LazyCloud hostname. Custom domains need a Team or Business plan. They belong to your account and work in every workspace you own.

Register the domain

Registering a domain and verifying its DNS are account setup. A workload’s domain setting selects a registered hostname and creates no DNS records.
The command prints a CNAME record to create at your DNS provider, and any records needed to prove you own the name. Create them, then check:
The status reports DNS and certificate progress; the hostname serves HTTPS once its certificate is ready. The dashboard has the same flow under Settings, then Domains.

Point a workload at it

A workload names the hostname in its domain setting:
Save this as custom_domain.py, replace app.acme.com with your verified hostname, then run uv run lazycloud deploy custom_domain:count_words. Send a request as in the quickstart, with your custom URL. The endpoint still requires a token by default. @app.endpoint, @app.asgi, and @app.realtime accept domain.

Remove it

Removing a domain discards its certificate. Deployments keep their LazyCloud hostnames.