Administration

Use your own domain

A managed deployment answers at yourcompany.naxistechnologies.com from the day it is born. It can also answer at a domain of yours, say assistant.yourcompany.com: one DNS record, a click on your account page, and an automatic certificate. Included on every plan, and the Naxis address keeps working beside it.

The whole procedure

Attach the domain. On your account page, open your deployment's Use your own domain and enter the name, for example assistant.yourcompany.com. You can do this before or after the DNS step; either order works.
Point the DNS at Naxis. At your DNS provider (wherever yourcompany.com is managed), create this record:

Type A

Name / host the host part, e.g. assistant (use @ for the domain's root)

Value the IP shown on the account page (the managed server's address)

For a subdomain, a CNAME record pointing at yourcompany.naxistechnologies.com works just as well; a domain root needs the A record.
Let it verify. The account page checks the DNS for you, on the spot and again every time you open it. The moment the record is visible, the deployment reconfigures itself, usually live within a couple of minutes, and you get an email when it answers.

Type	`A`
Name / host	the host part, e.g. `assistant` (use `@` for the domain's root)
Value	the IP shown on the account page (the managed server's address)

HTTPS is automatic

The certificate is requested from Let's Encrypt automatically once your DNS points at the managed server; there is nothing to buy, upload or renew. The very first visit after connecting can take a few extra seconds while the certificate issues; every visit after that is instant.

What changes, what does not

Both addresses work	The Naxis subdomain is never retired; your own domain answers beside it. Bookmarks, channel webhooks and sign-ins on the old address keep working.
Email links	The assistant's own emails (invitations, digests) link back to the public address set in its console under Application settings. Set it to the new domain if you want those links on it; the "domain is live" email reminds you.
No extra charge	Custom domains are part of every plan, not an add-on.
Changing your mind	Attach, detach or replace the domain from the account page whenever you like. Detaching returns the deployment to its Naxis address within minutes and nothing else is touched.

If it does not verify

DNS has not propagated	New records take minutes to appear; a record edited from an old value can take as long as its previous TTL. The account page tells you which addresses it currently sees for your name.
A proxy sits in front	Some DNS providers proxy traffic through their own network (often shown as an orange cloud). Switch the record to plain DNS, at least until the certificate has issued.
A CAA record forbids issuance	If your domain carries `CAA` records, they must allow `letsencrypt.org`, or the certificate cannot issue even with correct DNS.
The old site still loads	Your own browser may have cached the old DNS answer. Try a private window, another network, or simply wait a few minutes.

Self-hosted deployments

A self-hosted assistant runs on your infrastructure, so its domain is yours by nature: point the DNS name at your own server and set the public address in the console's Application settings. The install guide covers TLS and reverse-proxy setup.

Stuck on a DNS provider's particular screens? Open a ticket with the provider's name and the domain; we answer with the exact records.