Aegilume
Console

Set up a custom domain

Overview

Published projects use a platform-assigned address by default. Once you bind a custom domain, visitors can reach the project through your own domain (e.g. www.example.com). Ownership verification and HTTPS certificate issuance are handled automatically.

Custom domains are a MAX plan feature. On Free or Pro, the "Custom domain" entry shows a MAX badge that takes you to the pricing page to upgrade.

Before you start

  • You own a domain and can sign in to its DNS provider's console (e.g. Cloudflare, GoDaddy, Alibaba Cloud).
  • The project has been published from the editor and has its default address.

Step 1: Add the domain

  1. Open the project's deploy configuration popover and click "Custom domain".
  2. Enter your domain — either a root domain (e.g. example.com) or a subdomain (e.g. www.example.com) — then click "Add".

Once added, the dialog lists the DNS records you need to create.

Step 2: Configure DNS

In your DNS provider's console, create the two records shown in the dialog:

  • TXT record: proves you own the domain. The "Host" is the verification prefix — _jizao-verify for a root domain, or _jizao-verify.<subdomain> (e.g. _jizao-verify.www) for a subdomain; paste exactly what the dialog shows. The "Value" is the verification token generated by the platform.
  • CNAME record: points your domain at the platform's ingress. The "Host" is @ for a root domain, or the relative prefix for a subdomain (e.g. www); use the "Value" shown in the dialog. If you're setting up a root domain and your provider doesn't allow CNAME at the root, use its ALIAS/ANAME support or an A record pointing to the same ingress — verification accepts both.

Set the TTL to 10 minutes as suggested. DNS changes usually take a few minutes to propagate, but can take up to several hours.

Step 3: Verify and issue the certificate

  1. Back in the custom domain dialog, click "Verify". Checks run in order — TXT first, then CNAME — and each record's result is shown separately, so you can see exactly which one hasn't taken effect.
  2. Once both checks pass, the SSL certificate is requested automatically. Issuance usually takes 1–3 minutes. When the status changes to "Active", your project is reachable at https://your-domain.

If verification fails, make sure the host value was pasted exactly as shown and the record value is complete, wait for DNS to propagate, then click "Verify" again.

Managing bound domains

From the dialog you can copy the domain, open the site in a browser, refresh its status, or remove the binding. When a project is taken offline, its domains and certificates are cleaned up automatically — nothing for you to do.

FAQ

What if I see "This domain is already bound to another project"?

A verified domain belongs exclusively to that project. If the domain is yours, remove the binding from the original project's dialog first, then add it to the current one.

Can someone else occupy my domain before I finish verification?

Not for long. Only a verified binding counts as occupied. An unverified placeholder can be taken over by another project, which issues a fresh verification token. Complete the DNS setup and verification soon after adding your domain.

Can one domain be bound to multiple projects?

No. A domain can only be bound to one project at a time. Each project also has a limit on custom domains — remove bindings you no longer use before adding new ones.

ON THIS PAGE