I do not want my clients to see your infrastructure address

Every client inbox has a default address that is long and names our infrastructure. If you would rather your clients never saw it, that address can be replaced with a subdomain of your own. What their staff see and bookmark is entirely yours.

One subdomain per client

Understand this up front: each client needs its own subdomain. Every client has a separate inbox, and one domain name can only point at one inbox. There is no way to make a single address serve all your clients without sending them back to their original address.

So each new client means one new CNAME on your side, and one setup on ours.

The steps, without contacting us

1. Create the CNAME first. Point your chosen subdomain at that client's default address:
   clientname.yourdomain.com. CNAME waco-clientname-a1b2c3.s3.idcloudhost.com.
2. Register it through the API:
   POST /api/partner/v1/tenants/<tenant_id>/domain with {"domain": "clientname.yourdomain.com"}
   The response also carries cname_tujuan, so calling it first still tells you exactly where to point the record.
3. Done. We check DNS every 5 minutes, install the domain, issue the HTTPS certificate, and point every internal link, email included, at your domain.

Track it yourself through GET /api/partner/v1/tenants: domain_status reads menunggu (pending), aktif (active), or gagal (failed), and domain_galat explains why when it is not yet active. You never need to ask us.

Usually finished a few minutes after your DNS propagates. If the CNAME is not in place yet we keep waiting for up to 48 hours before giving up, so there is no rush.

The default address keeps working throughout, and stays working afterwards. If anything goes wrong with your domain, your client never loses access.

Why the CNAME has to come first

The HTTPS certificate is issued by proving that the name really does point at us. If we set things up before your DNS does, that proof fails and has to be repeated. One minute of waiting for DNS saves a round trip.

What is not enough on its own

A CNAME alone will not work. DNS only points at a machine; it does not tell that machine what to serve. Without setup on our side visitors get a 404, and before that the browser already shows a security warning because the certificate does not cover that name.

If you would rather run a reverse proxy on your own server, that works too. Still tell us the final domain: the links inside staff invitation and password reset emails are generated on our side, and only we can point them at your domain. Without that, the original address still appears in email even though the web view is masked.

Before you settle on a name

Choose a subdomain you will not change. Once it is in use it lives in staff bookmarks and in emails already sent. Changing it breaks those links, and the people left confused are your client's staff, not you.