Web Work hosts your app. You can use a custom domain (e.g. www.yourbrand.com) — buy one right here through Web Work, or connect a domain you already own by pointing it to the address we show on the preview screen. This guide explains both paths in plain language.
A one-time step per brand. The process is similar across most registrars.
Common options: Cloudflare Registrar, Namecheap, Porkbun, Google Domains (now Squarespace Domains), and others. Compare first-year and renewal prices; pick a company you are comfortable logging into when changing DNS.
The first year is often discounted; subsequent years cost more. Enable auto-renew if you do not want to lose the name when it expires. If payment fails, the domain may become available to others.
Many registrars offer free or paid WHOIS privacy so your personal details are not published. Enable it to reduce spam.
After you enable hosting in Web Work, the preview page shows two types of records:
A CNAME says “this hostname is an alias for another.” For example, www can point to the Web Work target (project ID + our hosting host). This routes traffic to the hosted app.
A TXT record stores text. We add a short string to verify that you control the domain before we accept it as connected.
DNS changes are not instant everywhere. From a few minutes to up to 48 hours (rare). If verification fails, wait and try again. TTL on old records slows the update.
Turn the orange cloud OFF for the CNAME record so it reads "DNS only" (grey cloud). A proxied CNAME hides the chain from public DNS and blocks our certificate from being issued, so the domain never goes live. For an apex domain (@) add the same CNAME — Cloudflare flattens it to A records for you.
Browsers expect encrypted HTTPS. After DNS points to Web Work hosting, the operator provides a certificate for the hostname (e.g. Let’s Encrypt or a load balancer). A certificate warning may mean propagation is still in progress or an edge setup is missing — check with your Web Work administrator.