Bind Your Own Domain: From xxx.studio.acedata.cloud to ai.yourbrand.com

Bind Custom Domain

At this point, your sub-site already has its own brand and pricing. But the address is still yourprefix.studio.acedata.cloud—which clearly indicates it's "under someone else's umbrella."

In this article, we will attach your own domain. After completing this, users will access ai.yourbrand.com (or any domain you own), clean and neat, like an independent product.

This step is optional, but I strongly recommend doing it—it is the dividing line between "looking professional / looking amateur."

What You Need to Prepare

Only two things:

  1. A domain you own (can be purchased from any registrar like Alibaba Cloud, Tencent Cloud, Cloudflare, GoDaddy, etc.).
  2. Access to its DNS management backend (permission to add a record).

No need to buy a server, no need to configure certificates, no need to understand operations.

Principle: A CNAME is Enough

The essence of binding a white-label domain is to make your domain point to the Studio main site, which will then load "your set" of configurations based on the incoming domain.

So what you need to do is add a CNAME record in your DNS, pointing your domain (for example, ai.yourbrand.com) to the target address provided by the platform.

   ai.yourbrand.com   ──CNAME──►   （Target domain provided by the platform）
                                        │
                                    Studio main site loads your brand/pricing/capability configuration based on the domain

Steps to Operate

1. In the Custom Domain section, enter the domain you want to bind

Main site → Click the gear icon in the lower right corner to enter Settings → Open the Custom Domain section and enter your full domain, such as ai.yourbrand.com.

Custom Domain: Enter your own domain, the page provides the target address for CNAME, Let's Encrypt HTTPS auto-issue + renewal, status Active

The system will tell you which target address to CNAME to (refer to what is actually displayed on the page—do not copy the example values from the internet or this article). The line with studio.zhishuyun.com in the screenshot has a status of Active, which is a real example that has been successfully bound and the certificate issued.

2. Go to your DNS backend and add a CNAME record

Log in to your domain registrar's DNS console and add a new record:

Type Host Record Record Value
CNAME ai (or your desired subdomain, like studio) The target address provided by the platform

Using a subdomain (ai.yourbrand.com, studio.yourbrand.com) is the easiest; just CNAME it directly. If you must use a root domain (yourbrand.com naked domain), some DNS providers do not support root CNAME and require using ALIAS/ANAME or CNAME flattening—Cloudflare and DNSPod both support this.

3. Wait for propagation + automatic HTTPS issuance

DNS propagation takes some time, usually from a few minutes to several minutes. After it takes effect, the platform will automatically issue an HTTPS certificate using Let's Encrypt and renew it automatically—completely free, you don't have to deal with Let's Encrypt or worry about certificate expiration; the platform takes care of everything.

Open https://ai.yourbrand.com, and if you see a lock icon, the page loads normally, and it’s still your brand—then the binding is successful.

Common Issues

  • Cannot open / certificate error: Most likely, the DNS has not propagated yet, or the certificate is still being issued. Wait a moment, and use dig ai.yourbrand.com or an online DNS query tool to confirm that the CNAME has pointed correctly before checking again.
  • Pointing to the wrong address: Go back to the sub-site configuration page and ensure the target address matches exactly with what you filled in your DNS (no extra spaces, no missing characters).
  • Root domain cannot be bound: Switch to a subdomain (recommended), or use a DNS provider that supports CNAME flattening.

A Boundary I Must Honestly Inform You About

Binding the domain solves the facade of your AI site—this part is now fully supported (CNAME + free automatic HTTPS). However, there are two areas that currently cannot be changed to your own:

  • Login process still uses the auth.acedata.cloud domain (the brand and login methods can be changed, but the domain field at that moment has not been changed);
  • API domain and CDN resource domain for developers are still the platform's.

In other words, user browsing, chatting, generating, and ordering mainly occur under your domain, and the experience is already very coherent; it’s just that during the login moment, the domain field will briefly show auth.acedata.cloud. I mention this honestly to avoid any miscommunication with your customers. These two areas are not yet live on the roadmap.

With the domain bound, your white-label site is truly "standing" up. The next article "What to Sell, How Much to Sell"—we will enter the most critical step that can determine how much you earn: Choosing Capabilities + Pricing Markup.