Skip to main content
By the end of this guide your workspace is reachable at your own hostname — app.acme.com, say — instead of the default acme.gavai.app. You attach the hostname, read the DNS values gavAI generates, set the records with your DNS provider, trigger verification, and poll for the confirmed status. TLS is provisioned automatically once verification completes.

​
Prerequisites

​
Steps

​
Troubleshooting

​
What you built

You attached a custom hostname to the workspace, set the verification and routing DNS records, verified through the API, and confirmed the domain is live. The workspace is reachable at your own domain instead of acme.gavai.app, with TLS handled automatically.

​
Next steps