Custom domain

Use a custom domain when readers should access your docs from your own domain, such as docs.example.com.

Custom domains are available on Growth and Pro plans. Only organization owners can add or remove a custom domain.

Supported domain patterns

PatternExampleHow Radiant handles it
Subdomaindocs.example.comRadiant provides a CNAME target and manages SSL readiness
Public docs URL with pathexample.com/docsRadiant stores the public URL for display and routing context

Root domains such as example.com are not supported yet for Radiant-managed custom domains. Use a subdomain such as docs.example.com.

Add a custom domain

Open the domain settings

In the Radiant dashboard, open the domain settings for your docs project.

Enter a subdomain

Enter the docs subdomain you want readers to use, such as docs.example.com.

Add the CNAME record

Radiant shows the CNAME record to add at your DNS provider. Add that record for the subdomain.

Return to Radiant

Go back to the dashboard and check the domain status. DNS and certificate readiness can take time to propagate.

Domain status

StatusMeaning
PendingRadiant is waiting for DNS or certificate readiness
ActiveThe custom domain is ready for readers
FailedRadiant could not activate the domain

When the domain becomes Active, readers can use the custom domain to access the docs site.

Change or remove a domain

Organization owners can remove the current custom domain from the dashboard. After removal, the docs site continues to be available from its Radiant-hosted URL unless the project is otherwise unpublished or deleted.

To switch domains, remove the current domain and add the new one.

Common questions

Not yet. Use a subdomain such as docs.example.com for a Radiant-managed custom domain.

Pending usually means DNS or certificate readiness has not completed yet. Confirm the CNAME record matches the value shown in Radiant, then check the status again after propagation.

Organization owners can add or remove custom domains on Growth and Pro plans.

Radiant stores the public docs URL, such as https://example.com/docs, but paths are not DNS records. Use this pattern only when your own routing layer sends that path to the docs site.

Next steps