Custom Domain or CNAME

Typesense Cloud does not natively support the ability to use custom domains. You also cannot CNAME a Typesense Cloud hostname, due to SSL certificate mismatch issues.

Instead, you would have to set up something like Cloudflare DNS (even the free version would suffice), set up a record for each of your Typesense Cloud hostnames, with the proxy setting enabled. (As a bonus, you also get DDoS protection for free.)

For example, for a 3-node cluster, you'd set up the following proxied connections:

ts-ha.yourdomain.com -> xxx.a1.typesense.net
ts1.yourdomain.com -> xxx-1.a1.typesense.net
ts2.yourdomain.com -> xxx-2.a1.typesense.net
ts3.yourdomain.com -> xxx-3.a1.typesense.net

Where xxx*.a1.typesense.net  is your Typesense Cluster's individual nodes' hostnames, found in your dashboard.

You'd then use the ts*.yourdomain.com  hostnames when instantiating the client libraries or making API calls, so that requests are routed through Cloudflare before they reach your origin Typesense nodes.