The “Custom domain” screen lets you open your cloud instance at your own
address (for example assistant.company.com) instead of the managed
<name>.cloud.aihummer.ru.
How it works
Enter the desired domain on the “Custom domain” screen. The domain is
lowercased and lightly validated (must contain a dot, no spaces).
In response you get a CNAME target — your managed address
<subdomain>.cloud.aihummer.ru.
In your DNS settings create a CNAME record: <your-domain> →
<CNAME target>.
Once DNS propagates, the platform verifies the CNAME, issues a TLS certificate
and connects the domain. This runs in the background.
Statuses and the step-by-step wizard
The screen shows a four-step wizard — domain entered → the CNAME record
(type, host and a copyable target value) → DNS check → certificate — and a
badge with the current status:
Checking (pending) — the platform is verifying the CNAME and issuing
the certificate; the “Check now” button requests a fresh verdict.
Connected (connected) — the certificate is issued and the domain works;
an “Open” link to https://<your-domain> appears.
Failed (failed) — verification or certificate issuance failed: check
the CNAME record and retry.
Keep in mind DNS records do not propagate instantly — after creating the CNAME
the check may stay “Checking” for a while.
What happens next
When the domain is connected, it replaces the managed address on the instance
dashboard and in the “Open panel” link. An empty domain clears the mapping and
restores the managed address. The managed subdomain
<name>.cloud.aihummer.ru keeps working in parallel.
Tips
Use a subdomain (for example ai.company.com), not the root domain — a CNAME at
the apex isn’t supported by every registrar.
The certificate is issued automatically; you don’t upload it separately.
Make sure an old record for that name (A/AAAA/CNAME) doesn’t conflict.
The **"Custom domain"** screen lets you open your cloud instance at your own
address (for example `assistant.company.com`) instead of the managed
`<name>.cloud.aihummer.ru`.
## How it works
1. Enter the desired domain on the "Custom domain" screen. The domain is
lowercased and lightly validated (must contain a dot, no spaces).
2. In response you get a **CNAME target** — your managed address
`<subdomain>.cloud.aihummer.ru`.
3. In your DNS settings create a **CNAME** record: `<your-domain>` →
`<CNAME target>`.
4. Once DNS propagates, the platform verifies the CNAME, issues a TLS certificate
and connects the domain. This runs in the background.
## Statuses and the step-by-step wizard
The screen shows a **four-step wizard** — domain entered → the CNAME record
(type, host and a copyable target value) → DNS check → certificate — and a
badge with the current status:
- **Checking** (`pending`) — the platform is verifying the CNAME and issuing
the certificate; the "Check now" button requests a fresh verdict.
- **Connected** (`connected`) — the certificate is issued and the domain works;
an "Open" link to `https://<your-domain>` appears.
- **Failed** (`failed`) — verification or certificate issuance failed: check
the CNAME record and retry.
Keep in mind DNS records do not propagate instantly — after creating the CNAME
the check may stay "Checking" for a while.
## What happens next
When the domain is connected, it **replaces** the managed address on the instance
dashboard and in the "Open panel" link. An empty domain clears the mapping and
restores the managed address. The managed subdomain
`<name>.cloud.aihummer.ru` keeps working in parallel.
## Tips
- Use a subdomain (for example `ai.company.com`), not the root domain — a CNAME at
the apex isn't supported by every registrar.
- The certificate is issued automatically; you don't upload it separately.
- Make sure an old record for that name (A/AAAA/CNAME) doesn't conflict.
## Next
- [Instance dashboard](/en/v1.0/portal/instance) — where the connected domain
appears.
- [External access](/en/v1.0/webui/api-access) — public addresses in self-hosting.
- [Subscription management](/en/v1.0/portal/subscription) — instance status.