Connect your domain and wait for HTTPS.
Add a domain you own to a published project, copy the exact A and ownership TXT records from the workspace, then check DNS. Share the address when the workspace reports Connected · HTTPS.
Before you begin
You need an invited account, a published project and access to the domain's DNS provider. The Free beta allowance includes one custom domain. This beta supports DNS-only IPv4 routing, with no wildcard domains, IPv6 routing or proxied DNS.
Connect the published project
- Open Domains and choose the project to connect.
- Enter the exact hostname you own, such as www.example.com.
- Copy the generated A and TXT records into your DNS provider. Use the supplied host and value; examples are not production records.
- Keep the A record in DNS-only mode and remove conflicting routing records for that hostname if your provider reports a conflict.
- Choose Check DNS after your provider has saved the changes.
- Wait for ownership, routing and certificate checks to complete and for Connected · HTTPS to appear.
DNS changes can take time to reach resolvers. Recheck the actual hostname, record host and record value if validation remains pending. Keep the verification TXT record present after connection.
What does a pending state mean?
Pending DNS means the expected ownership or routing evidence has not been confirmed. A certificate-pending state means the connection has not finished HTTPS activation. Neither state is proof of a working website address. The service periodically checks connected domains; use the status and error reference shown by the workspace when troubleshooting.
Let an assistant read the recorded setup
A compatible MCP client with projects:read and domains:read permission can use domain_status for a project. It returns the stored DNS, routing and HTTPS states, check timestamps and the A and ownership TXT instructions. This is a read of the latest recorded check, not a fresh DNS query or network probe. It does not change records at your DNS provider or connect a domain automatically.
Request the domain-read permission explicitly when connecting an assistant. Existing connections are not silently granted this additional access. Use the dashboard to perform a new check or change the connection.
Domain routing and browser storage
A verified customer-owned domain serves the selected project at its own root origin and allows normal browser cookies and storage. Shared platform and preview addresses retain a restrictive browser sandbox. The application you upload remains responsible for its authentication, permissions and external API behavior.
Disconnect a domain
Disconnecting stops DeployBeacon from serving the project at that hostname. Remove or replace its DNS records separately at your DNS provider. Retained project releases remain subject to the normal project permissions and retention rules.
Explore the product and guides
Access is invitation-only. No payments are collected during the private beta. Sign in to your invited workspace.