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

# White-label branding

> Run Enginy under your own brand and domain for your customers

## Overview

White-label partners can serve Enginy to their end customers under their own brand: your logo, product name, and primary color replace the Enginy brand across the app, and your customers sign in on your own domain (for example `app.yourdomain.com`).

Setup is self-serve from **Settings → Workspace** and has two parts:

1. **Branding** — logo, brand name, and colors.
2. **Custom domain** — point a domain you own at Enginy and verify it via DNS.

<Info>
  White-label branding is available on the **White Label** partner plan, and editing it requires a **workspace
  admin** grant. If you don't see the Workspace tab in Settings, or the controls are disabled, contact your
  Enginy account manager.
</Info>

## 1. Configure your branding

In **Settings → Workspace → Branding**:

1. Enable **Custom branding**.
2. Upload your **logo** (PNG, JPEG, GIF or SVG, up to 1MB).
3. Set your **brand name** — it appears in page titles, the sign-in heading, and the two-factor authenticator label.
4. Set your **primary color** (6-digit hex, e.g. `#1A73E8`). The entire app theme — buttons, accents, highlights, spinner — is derived from this single color.

<Note>
  A dark-mode primary color can be stored, but it is not applied yet: the platform currently ships in light
  mode only.
</Note>

There is no per-account targeting: your brand shows for **every** account accessed through your domain, and never anywhere else.

## 2. Add your custom domain

In **Settings → Workspace → Custom domain**:

1. Add the domain your customers should use, e.g. `app.yourdomain.com` (subdomains only — wildcards and IP addresses are rejected).
2. The panel shows two DNS records to create at your DNS provider, each with a copy button:
   * a **CNAME** record pointing your domain at Enginy, and
   * a **TXT** record that proves you own the domain.
3. Create both records, then press **Check now**.

The domain moves through three states:

| Status                  | Meaning                                                                                  |
| ----------------------- | ---------------------------------------------------------------------------------------- |
| **Pending DNS**         | Waiting for you to create the records and verify.                                        |
| **Verification failed** | One of the records is missing — the message tells you whether it's the CNAME or the TXT. |
| **Active**              | Both records verified. Your domain now serves the branded sign-in.                       |

<Note>
  DNS changes can take a few minutes to propagate. If verification fails right after you created the records,
  wait a bit and press **Check now** again — the error tells you exactly which record is still missing.
</Note>

### The certificate badge

Once your domain is **Active**, a second badge tracks its HTTPS certificate:

| Badge                   | Meaning                                                                                         |
| ----------------------- | ----------------------------------------------------------------------------------------------- |
| **Certificate pending** | We're issuing the TLS certificate that lets your domain serve HTTPS. Nothing to do — just wait. |
| **Certificate active**  | Your domain serves HTTPS. Safe to share the URL with your team and customers.                   |

What happens during **Certificate pending**: our edge provider validates that your domain routes to us
(it does, via the CNAME you created) and then issues and deploys a TLS certificate for it across the
network. This is fully automatic and **usually takes under 10 minutes**. Until the badge turns green,
visiting the domain over HTTPS will show a browser security error — that's expected, not a
misconfiguration.

<Note>
  Still pending after **an hour**? That means issuance is blocked, not slow. Re-check that your CNAME record
  is still in place, and — if your domain has **CAA** records — that they allow certificate issuance (our edge
  uses Google Trust Services, Let's Encrypt and SSL.com). Domains without CAA records need no change.
</Note>

## 3. What your customers see

* **On your domain** — the sign-in and register pages, and the app after login, carry your logo, name, and colors from the first paint. Enginy marketing and legal links are hidden.
* **Anywhere else** (`app.enginy.ai`) — stock Enginy branding, always. The domain the app is accessed on is the only thing that decides the brand.

## Current limitations

* **Emails sent by the platform** (e.g. password reset) currently link to the Enginy domain.
* Branding applies in **light mode**; a dark theme is not available yet.

<Info>Removing an **Active** domain immediately stops the branded sign-in on it, so remove with care.</Info>