# Use your own domain

> Serve your Maven client portal from your own subdomain, such as reports.youragency.com, verified through DNS with SSL issued automatically. Included in the workspace price.

Source: https://mavendata.ai/docs/client-portal/custom-domain

The client portal can run on a hostname you own, such as `reports.youragency.com`. You connect the domain in Maven and then add DNS records at your DNS provider. Maven verifies the records through Cloudflare for SaaS and issues an SSL certificate automatically. Once verified, your domain serves the same portal as your Maven-hosted address. It doesn't expose the Maven admin app. The white-label portal is included in the workspace price. See [Plans and pricing](https://mavendata.ai/docs/account/plans).

## Before you start

- Set up the portal's Maven-hosted subdomain first. See [Set up a client portal](https://mavendata.ai/docs/client-portal).
- Choose a **subdomain** of a domain you control, for example `reports.youragency.com` or `analytics.example.com`. Root domains such as `youragency.com` aren't supported yet.
- Make sure you, or someone on your team, can add DNS records for that domain.

## Connect the domain

1. Open **Settings** from the user menu, then **Portal**.
2. Under **Portal identity & domain**, enter the hostname in **Custom Domain (optional)**.
3. Select **Connect Domain**. Maven starts verification and shows the DNS records to add.
4. At your DNS provider, add each record exactly as Maven shows it. Every record has a **Host** and a **Value**, each with a **Copy** button:
   - **Portal CNAME**: points your hostname at Maven. It routes the portal and lets Cloudflare issue SSL.
   - **Hostname pre-validation**: a TXT record that proves you own the domain. It only appears when it's needed.
   - Other certificate validation records, if Maven lists any.
5. Return to **Portal** settings. While verification is in progress, the domain shows **Pending**. Select **Refresh** to check again.

When the domain is live, it shows **Verified**. Maven only treats a domain as verified once the hostname and its certificate are active and plain HTTP visits redirect to HTTPS.

Don't copy record values from anywhere else, including this page. The values are generated for your portal, and Maven always shows the current ones.

## What happens next

- **You don't need to stay on the page.** Maven keeps checking in the background and activates the domain on its own once DNS is in place.
- **DNS can take up to 48 hours to propagate.** Each record shows **Required** until Maven sees it, then **Active**. The page also shows the raw **Verification status** and **SSL** status from Cloudflare.
- **Your Maven-hosted address keeps working.** Changing the subdomain and connecting a custom domain are separate settings.

## Troubleshooting

| Message | What to do |
|---|---|
| "Use a subdomain like analytics.example.com. Root domains are not supported yet." | Use a hostname such as `reports.youragency.com` rather than the bare domain. |
| "Cannot use a Maven domain as a custom domain" | Enter a domain you own, not a Maven address. |
| "Domain is already in use by another Maven product or customer" | Choose a different hostname. |
| "Custom domain is not active yet. Confirm the CNAME below…" | Check the CNAME host and value at your DNS provider, wait for propagation, then select **Refresh**. |

If your DNS is on Cloudflare, the **Open Cloudflare DNS** link takes you to your DNS records.

## Related

- [Set up a client portal](https://mavendata.ai/docs/client-portal)
- [Client logins and sharing](https://mavendata.ai/docs/client-portal/sharing-and-access)
