About workspace domains

Explanation

Why the branded subdomain is both the address and the isolation boundary, and where a custom domain sits.

Context

Every workspace is served at your-subdomain.hosted.devdocs.ai. That hostname is the public address of the site and the isolation boundary between workspaces. A publish token can only ever write its own site. Content is served over TLS by default.

Why

Hostname isolation keeps one workspace from reading or writing another. The same hostname is what chat, MCP, and the reader use to pick a tenant. A custom domain would have to preserve that mapping. Until it does, the branded subdomain is the honest address.

Enterprise and mid-market teams can have us set the slug during provisioning. Smaller teams choose it in self-serve. If you need a different subdomain later, reach out.

Trade-offs

Serving docs on a domain you own (for example docs.yourcompany.com) is not part of the current design partner program. It is a future consideration, not a current feature, and we will not commit to a date until we can hit it.

Note
We would rather tell you plainly what is not available than imply otherwise. The roadmap is the honest map of live versus planned.

Further reading

*(see How-to: How to brand a site)* *(see How-to: How to publish from your pipeline)* *(see Explanation: About Hosted Docs)*