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

# Branding & Domains

> Brand your white-label platform: name, logo, colours, customer e-mails and legal links, then connect your platform domain and your published-apps domain.

Your customers should only ever see your brand.

This page covers the **Branding** and **Domains** tabs of the partner console: how your platform looks, how it e-mails customers, and where it lives.

## Your Brand Name

Your brand name appears everywhere your customers look.

As you type it, AIWA checks whether it's available. If the name is already taken or reserved, you can't save it, and you're offered two alternatives that are free to use.

Names that differ only in capitals or punctuation count as the same name, so "Acme", "ACME" and "Acme!" can't belong to two partners.

## Brand Studio

The **Branding** tab is your brand studio. Nothing changes for your customers until you save.

| Field | What it does |
| - | - |
| **Logo** | PNG, JPEG, WebP or SVG, up to 5 MB |
| **Colours** | Your palette. Not sure? Let the studio mix two palettes for you |
| **Tagline** | One line used as your search description and on your share card. Select **Suggest taglines**, or leave it blank and one is written from your brand name |
| **Support e-mail** | Where customer replies land, and the address on your documentation's Contact Support page |
| **Sender name** | The name customers see on e-mails from you. Blank uses your brand name |
| **Badge** | Whether customers' published apps show a "Made with" badge with your brand name, or no badge |
| **Documentation URL** | Where your platform's help links go, if you use your own docs site |

The palette and tagline helpers are free for partners.

### Live preview

The studio shows your unsaved changes in a live preview, on desktop and mobile:

* **The app** your customers use
* **The welcome e-mail**
* **The verification e-mail**

## Legal Pages

Your sign-up page should link your own terms.

In the Branding tab, add:

* **Terms of Service URL**: the terms your customers accept when they sign up
* **Privacy Policy URL**: how you handle your customers' data

Both are optional. Until you add yours, your sign-up page links AIWA's standard policies.

## Customer E-mail

Your customers receive welcome, verification and account e-mails.

By default, AIWA sends them from an AIWA address under your brand name, with your logo and support contact.

To send from your own domain, connect a Resend account:

**1. Open the e-mail settings**

In the partner console, find the customer e-mail section.

**2. Paste a full-access Resend API key**

Enter your sending address and a Resend API key with full access, then select **Verify and save**.

**3. Send a test**

Select **Send test to me** to check delivery.

Connecting Resend also turns on **sign-up notifications**, so you're told whenever someone signs up on your platform.

> [!NOTE]
>
> Password-reset e-mails are sent by the sign-in provider and need their own sender configuration. Partner programme e-mails to you (not your customers) come from AIWA.

## Your Two Domains

Your platform uses two addresses, each with its own purpose:

| Domain | What it's for | Example |
| - | - | - |
| **Platform domain** | Where your customers sign in and build | `app.yourbrand.com` |
| **Published apps domain** | Where your customers' apps go live | `yourbrandapps.com` |

## Connect Your Platform Domain

Use a subdomain, such as `app.yourbrand.com`.

**1. Enter the subdomain**

In the **Domains** tab, enter your platform subdomain, without `https://` or a path.

**2. Add two DNS records**

The console shows two DNS records. Add them at your DNS provider.

**3. Wait for the check**

The console checks automatically every 15 seconds.

## Connect Your Published Apps Domain

For the published apps domain, choose where DNS is managed:

| Option | How it works |
| - | - |
| **Keep DNS in Cloudflare** | Use your existing Cloudflare account, with no nameserver change. You can use a domain or a subdomain from a zone already active in Cloudflare |
| **Let AIWA manage DNS** | Use a whole domain dedicated to published apps, such as `yourbrandapps.com`, and change its nameservers at your registrar to the two values the console shows |

### Keep DNS in Cloudflare

Create a Cloudflare API token with **Zone Read** and **DNS Edit** permissions, limited to the zone for this domain. Copy the token and paste it into the console. AIWA stores it encrypted.

### Let AIWA manage DNS

Replace the nameservers at your domain registrar with the two values shown. The console checks automatically.

## Going Live

Once the DNS is correct, AIWA secures the domain with HTTPS. The domain goes live as soon as it's secure, usually within a few minutes.

On the published apps domain, new apps publish there straight away. Existing apps move when they are next published.

## Next: Customers & Offers

With your brand and domains ready, the next step is deciding what your customers pay.

> **[Customers & Offers](/white-label/customers-and-offers.md)**
>
> Set your plans, free offers, project caps and top-up rate.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.