Connect a custom domain

You want your app to be reachable at your own domain (for example app.yourcompany.com) instead of the default <slug>.talkide.dev address. Domain connection is a top-level feature called Domains in the Studio navigation, not something tucked inside a project’s own settings.

There are two ways to connect a domain, and TalkIDE recommends one for you based on a quick DNS check:

• CNAME: you keep managing DNS at your current registrar and add a single CNAME record yourself. Nothing else about your domain changes.
• Full NS delegation: TalkIDE takes over the domain’s DNS zone entirely.

Both are valid. Which one you want depends on how much control you want to keep at your registrar. The steps below walk through the CNAME path in full, since it’s the lighter-touch option most people reach for first.

Before you start

• You need a domain you already own, registered with any provider.
• Know which project and deployment you want to point the domain at, since you’ll pick them during setup.

Steps

1. Open Domains

In TalkIDE Studio, click Domains in the top-level navigation, alongside Overview, Projects, Tasks, and Environments.

2. Start connecting your domain

Click Connect your domain and enter the hostname you want to use, for example app.yourcompany.com.

3. Check the domain

Click Check domain. TalkIDE probes the domain’s current DNS setup and recommends one of the two modes above.

4. Choose CNAME

To keep DNS at your registrar, choose CNAME — connect one subdomain (nothing gets broken), then click Continue with CNAME.

5. Connect the hostname

A Connect a hostname dialog opens. Pick the project and the deployment you want this domain to point to, then confirm.

6. Add the CNAME record at your registrar

TalkIDE shows you the CNAME record to add. Log in to your registrar, or wherever you manage DNS for the domain, and add the record there. Once it propagates, the domain points at your app.

Notes

• You can connect multiple domains to the same app.
• The default <slug>.talkide.dev address keeps working after you add a custom domain.

Change which project or environment a domain points to

You’re not locked into your first choice. Open the domain from the Domains page to see its detail view, including an Attached to section that shows where the domain currently points.

Attaching a domain you registered but haven’t used yet

If the domain isn’t pointed at anything, the Attached to section shows Not attached to any project yet. and a button, Attach to project. Clicking it opens the Attach domain to project dialog:

1. Pick a project from the Project field, then click Continue. Continue stays disabled until you’ve picked one.
2. Pick an environment from the Environment field, which lists that project’s active environments (deactivated environments aren’t offered here). Click Continue, or Back to change the project first.
3. What happens next depends on the environment you picked:
   • If it already has a live, published deployment, the dialog lets you pick a subdomain if needed, checks that it’s available, and gives you a confirm step. Confirming points the domain at that project and environment.
   • If it hasn’t been published yet, the dialog shows This environment hasn’t been published yet. and Go to Project Settings → Deployments to publish it with this domain., with a Go to Project Settings button that takes you there.

Re-pointing a domain that’s already attached

If the domain is already attached, the Attached to section shows the project, environment, and live URL it currently points to, plus a button to change it. That opens the same dialog, with the current project and environment already selected — pick a different project and/or environment and confirm to re-point the domain.

You can also change a domain’s target from inside a project’s own Deployments settings, if that’s where you happen to be working.

Related

• Agent roles: domain and TLS configuration is one of the things Kai handles on your behalf.