Custom domains

Every site starts at a yourname.tessryx.app subdomain. On a paid plan you can point your own domain at it (shop.yourbrand.com) from Dashboard → Domains. Adding and verifying a domain is an admin action.

A custom domain isn't just a nicer URL. It's what makes a site fully yours:

• It's indexed by search engines. Subdomain pages are deliberately kept out of search; your own domain is where SEO starts paying off.
• No Tessryx badge. The "Served by Tessryx" pill on subdomain pages is gone.
• It's the front door to an app. You point the domain at a project, and its pages serve from your address.

Each plan includes a number of domains (see Plans and limits); on Pro and Agency you can add more beyond that for $8/month each, so a new client site doesn't mean changing tiers.

#The flow

Adding a domain has a human step in the middle: you (or whoever manages your DNS) has to add two records at your domain provider. Tessryx can't do that part for you, so the process is:

1. Claim it. In Domains, add your hostname. Tessryx gives you two DNS records: a verification record (proves you control the domain) and a routing record (sends traffic to Tessryx and secures it).
2. Add the records at your DNS provider (GoDaddy, Cloudflare, Namecheap, etc.), exactly as shown. Copy-paste the names and values. A typo is the most common reason verification stalls.
3. Verify. Once the records are in, click verify. DNS changes take a few minutes to propagate, sometimes longer, so if it doesn't verify on the first try, wait a bit and check again. (No need to hammer it; giving DNS time is the fix.)
4. Wait for it to go live. The status walks through Pending → Verified → Cert pending → Active. "Cert pending" is a normal waiting stage while your security certificate issues, not an error. Once Active, your domain serves.

Apex vs. subdomain: the one thing that trips people up. The routing record is a CNAME. A subdomain (shop.yourbrand.com, www.yourbrand.com) takes a CNAME cleanly. A bare apex (yourbrand.com with no prefix) can't hold a CNAME on most DNS providers; you need one that supports CNAME flattening / ALIAS records (Cloudflare and a few others do), or point a subdomain like www instead. If an apex domain never finishes verifying, this is almost always why.

www and the apex are two separate addresses. Adding yourbrand.com does not also serve www.yourbrand.com (or the reverse), and there's no automatic redirect between them. Each is its own hostname you add and verify, and each counts toward your plan's domain allowance. Want both? Add both, and decide which one is canonical.

#Pointing it at the right project

After the domain is active, you tell it which app to serve and which page is its home, so yourdomain.com/ lands on your front page and the rest of the paths follow. Your agent usually sets this up; you can confirm it in the domain's settings.

Already on Cloudflare? If your domain is managed there, it can start serving as soon as the records are in, even while the Tessryx certificate is still issuing. Either way, watch the status rather than guessing.

Removing a domain is done here in the web app; if you ever need to move one, remove it and add it again.