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

# Custom Domains

> Serve the partner portal on your own domain so partners reach it at your address, not a generic one.

> Custom Domains put the partner portal on your own web address, so partners reach a portal that is unmistakably yours from the URL onward.

## What it does

A custom domain serves your partner portal at your own hostname, such as
partners.yourcompany.com, instead of a shared address. You point a domain at Introw, add the
DNS records Introw provides, and once they verify, the portal goes live on your domain with a
secure certificate. Partners bookmark and visit your address, reinforcing that the portal is
part of your brand.

This completes the white-label story. Branding makes the portal look like you; a custom domain
makes the URL itself yours, removing the last visible seam between your product and your partner
program.

## The problem it solves

A shared portal URL undercuts an otherwise polished program:

* **The portal lives on a generic URL** → Serve it on your own domain partners recognize.
* **The address does not match the brand** → Use a hostname like partners.yourcompany.com.
* **Setup feels like an engineering project** → Add the DNS records Introw provides and verify.
* **Security needs to be obvious** → A secure certificate is issued automatically once verified.

## From problem to solution

Custom Domains make the portal's address yours. Point a domain at Introw, add the provided DNS
records, and once verified the portal serves securely on your hostname. Partners get a portal
that is yours from the URL down.

## Use cases

<CardGroup cols={2}>
  <Card title="Own the portal URL" icon="circle-check">
    Serve the portal at your own recognizable address.
  </Card>

  <Card title="Complete the white-label" icon="circle-check">
    Pair branding with a matching domain for a seamless experience.
  </Card>

  <Card title="Verify with DNS" icon="circle-check">
    Add the provided records and go live once they verify.
  </Card>

  <Card title="Stay secure" icon="circle-check">
    Serve over a secure certificate automatically.
  </Card>
</CardGroup>

## Impact

* **Low total cost of ownership** - Ops sets up the domain without an engineering project.
* **Time to value** - The portal goes live on your domain as soon as DNS verifies.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner Operations" icon="user">
    Configures the domain and DNS for the portal.
  </Card>

  <Card title="VP Partnerships / CPO" icon="user">
    Wants a portal that is fully branded, down to the URL.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="Branding & White-label" icon="browser" href="/features/portal/branding">
    Your domain, your brand.
  </Card>

  <Card title="Portal Access" icon="browser" href="/features/portal/portal-access">
    Partners reach the portal on your domain.
  </Card>

  <Card title="Single Sign-On" icon="shield-halved" href="/features/access/sso">
    Run SSO on the custom domain.
  </Card>
</CardGroup>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Integration surface and code.
  </Card>
</CardGroup>