Custom domains, with the certificate handled
Published on
You can now put a site on your own subdomain.
Add the domain in the site’s settings and we show you the exact CNAME record to create. Add it at your DNS provider, and from there it is ours: we watch for the record, issue the certificate once it is visible, renew it for you, and force HTTPS.
What you see while it happens. The domain moves through waiting for DNS, issuing the certificate, and live, and it says which one it is at rather than leaving you to guess. If something is wrong, it says what is wrong. There is a recheck if you would rather not wait for the next background sweep.
Your agent can do it too. Four tools were added to the MCP server alongside the interface, so an
agent can attach a domain, read back the record for you to create, list domains with their state and
detach one: add_domain, list_domains, remove_domain and recheck_domain. The interface and the
agent use the same code, so neither can drift ahead of the other.
The limitation, stated plainly. Subdomains only. www.example.com works, bare example.com does
not, because the DNS specification does not allow a CNAME at the root of a domain and most providers
have no workaround for it. Point www at us and redirect the root to it at your registrar. We wrote
up the reasoning in why we do not support root domains.
The certificate costs nothing, on every plan.