> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asteragents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Domain

> Give your team a branded URL for Aster Agents — either a subdomain we host, or a hostname on your own domain

# Custom Domain

By default your team signs in at **[www.asteragents.com](http://www.asteragents.com)**. You can instead give them a branded URL — one that carries your company name and, optionally, your own domain. The sign-in page and the app sidebar show your logo in place of ours.

Custom domains are set up by the Aster team. There's no self-serve toggle — reach out and we'll configure it.

## Two options

<CardGroup cols={2}>
  <Card title="Aster subdomain" icon="bolt">
    **yourcompany.asteragents.com**

    Nothing needed from your IT team — we own this domain, so we handle it end to end. Usually live the same day.
  </Card>

  <Card title="Your own domain" icon="globe">
    **chat.yourcompany.com**

    Fully your domain in the address bar. Requires two DNS records from whoever manages your domain.
  </Card>
</CardGroup>

Both options give you the same branded sign-in and in-app logo. The only difference is whose domain the address sits on, and whether your IT team is involved.

## What we need from you

1. **The exact hostname you want.** For your own domain, pick the prefix — `chat.`, `ai.`, `agents.`, and `aster.` are all common. It'll be a subdomain rather than your root domain, since your root domain already serves your website.
2. **A logo.** A URL or image file — this replaces the Aster logo on your sign-in page and in the app sidebar.
3. **For your own domain: who manages your DNS.** Sometimes that's your IT team, sometimes an outside web vendor. Knowing early keeps the setup from stalling.

<Note>
  Choose the hostname carefully — changing it later means repeating the whole setup, including new DNS records. It's worth a minute of deliberation up front.
</Note>

## DNS records (your own domain only)

Once you've confirmed the hostname, we'll send you two CNAME records to add. For `chat.yourcompany.com` they look like this:

| Type  | Name         | Value                              |
| ----- | ------------ | ---------------------------------- |
| CNAME | `chat`       | *(we'll send you the exact value)* |
| CNAME | `clerk.chat` | `frontend-api.clerk.services`      |

The first points the hostname at the Aster app. The second lets our authentication provider serve your sign-in session on your domain — without it, sign-in won't complete.

The first record's value is unique to your domain, so wait for the exact value from us rather than copying one from elsewhere.

<Warning>
  **Add the records only when we confirm we're ready.** The hostname goes live the moment DNS resolves, and if our side isn't deployed yet your team will hit a broken sign-in page. We'll give you a clear go-ahead.
</Warning>

**If your DNS is on Cloudflare**, set both records to **DNS only** (grey cloud, not orange). Proxying them causes certificate and sign-in errors.

**This does not touch your email.** No MX, SPF, or DKIM changes are involved — the setup only adds a subdomain and doesn't affect mail delivery for your domain.

<Note>
  Looking to have your agents **send and receive email on your own domain** (e.g. `sales@yourcompany.com`)? That's a separate setup from this app custom domain — see the [Resend integration](/integrations/resend).
</Note>

Once the records are in place, DNS typically propagates within an hour, though it can take longer depending on your provider. We'll verify and confirm when it's live.

## What a custom domain does and doesn't change

**It changes** the URL your team visits, the logo on the sign-in page, and the logo in the app sidebar.

**It doesn't change who can access what.** A custom domain is branding and a convenient entry point — it isn't an access control. Access is governed entirely by organization membership and roles, exactly as before. See [Roles & Permissions](/settings/roles-permissions).

**Sign-in still happens on our domain.** Visitors to your custom domain are briefly redirected to `www.asteragents.com` to sign in, then returned to your branded URL with their session intact. This is standard for this kind of setup and keeps sessions secure across domains.

## Troubleshooting

| What you're seeing                        | Likely cause                                                                            |
| ----------------------------------------- | --------------------------------------------------------------------------------------- |
| The hostname doesn't resolve at all       | The first CNAME hasn't propagated yet, or was added to the wrong zone                   |
| Sign-in starts but never completes        | The `clerk.` CNAME is missing, mistyped, or Cloudflare-proxied                          |
| A certificate warning                     | Records are Cloudflare-proxied — switch both to DNS only (grey cloud)                   |
| Your team lands on the Aster-branded page | Signed in via `www.asteragents.com` directly; the custom URL is the branded entry point |

If something looks wrong after the records are in, send us the hostname and we'll check the verification status on our side.