Custom domains

Organization owners and admins can serve an Achiral workspace from a branded hostname, such as ai.example.com, instead of only using {slug}.achiral.ai.

Custom domains are managed from the organization dashboard:

https://{your-slug}.achiral.ai/organization/{your-slug}

Open Settings → Advanced → DNS Configuration.

Availability

Custom domains are available for organizations on these plans:

• Rise
• Boost
• Scale
• Grow
• Expand
• Prime
• Elite
• Titan
• God

They are also available when white-labeling is explicitly enabled for the organization.

Add a domain

1. Open the organization dashboard.
2. Go to Settings → Advanced.
3. In DNS Configuration, enter the hostname you want to use.
4. Select Save.
5. Add the CNAME record shown in the dashboard at your DNS provider.
6. Select Verify, or leave the panel open and wait for automatic polling.

The required DNS record is:

Type	Name	Value
CNAME	Your custom hostname	{your-slug}.achiral.ai

Example:

Type	Name	Value
CNAME	ai.example.com	example.achiral.ai

Verification states

The dashboard shows the current state of the custom domain.

State	Meaning
Pending	Achiral has created the custom hostname and is waiting for DNS/TLS verification.
Verifying	A manual or automatic verification check is in progress.
Active	DNS and TLS are ready. Traffic can route through the custom domain.
Failed	Verification failed. Confirm the CNAME record and run verification again.

While a domain is pending or verifying, the dashboard checks status every 10 seconds while the Advanced panel is open. A background sync also checks custom domains periodically.

Remove a domain

1. Open Settings → Advanced.
2. In DNS Configuration, select Remove.
3. Confirm the removal.
4. Remove the CNAME from your DNS provider when it is no longer needed.

Removal clears the organization custom-domain fields and deletes the routing cache entry. Edge caches can retain a removed hostname briefly, so allow up to five minutes for all pods to stop recognizing a recently removed domain.

Operational notes

Achiral provisions custom-domain TLS through Cloudflare for SaaS custom hostnames. The application stores the custom hostname ID, verification status, and verified timestamp on the organization record.

Runtime routing uses an internal lookup endpoint backed by Redis:

custom_domain:{hostname} -> {organization-slug}

If Redis misses, the internal lookup falls back to MongoDB for active custom domains and refreshes the Redis entry.

Self-hosted or operator-managed deployments need these environment variables on the API service:

Variable	Purpose
CF_ZONE_ID	Cloudflare Zone ID for achiral.ai.
CF_API_TOKEN	Cloudflare API token with Custom Hostnames read/write access.

If either value is missing, existing status can still be displayed from stored organization data, but creating or verifying a custom domain returns a configuration error.