White-label

The White-label page — per-brand custom domains, accent theming, and powered-by suppression. How a brand goes live, how the runtime resolves a brand per request, and how to preview any brand without touching DNS.

White-label

The White-label page lets an operator run the platform under a customer's own brand — a custom domain, an accent color, and the HostSSH wordmark suppressed. It's gated by the white_label.manage privilege; without it the page shows a locked state ("You need the white_label.manage privilege to manage brands & domains.").

A brand is a themed skin bound to a hostname. When a request arrives on a brand's live domain, the whole app renders in that brand's accent, and — when powered-by is hidden — without the HostSSH mark. This is the surface that delivers the MSP/Enterprise white-label promise from Licensing; the tenants that own these brands are managed on Tenants.

What the page shows

Four KPI stats: Brands (total), Live, DNS ready (brands where SPF + DKIM + DMARC all pass), and Powered-by hidden. A persisted / demo data badge indicates the store backend; on demo data the brands shown are the seed set (Northwind Backup Cloud, Atlas Vault).

The brands table lists each brand's name (with its accent swatch), domain, status, and powered-by state, plus a Preview action:

StatusMeaning
draftNot serving — created but not pointed at the platform
verifyingDNS being checked — not yet themed on its real domain
liveThemes its real domain

Only a live brand themes its real domain. Point the brand's DNS at the platform, mark it live, and its domain renders in the brand's accent with the wordmark suppressed (when powered-by is hidden).

Creating and editing a brand

New brand opens a drawer; clicking a brand name opens it for editing. The fields:

FieldNotes
Brand nameRequired
Custom domainThe host this brand serves on (e.g. vault.acme.com); validated as a real domain
Accent colourA hex color (#38bdf8-style), pickable or typed
Statusdraft / verifying / live
Hide "powered by HostSSH"Full white-label — suppress the wordmark

Delete one brand from its drawer, or select rows and Delete selected — both confirm first and permanently remove the brand and its domain routing.

The create/edit form covers name, domain, accent, status, and powered-by. The SPF/DKIM/DMARC readiness shown in the KPIs and on the Tenants brands card comes from the stored brand record's DNS flags; those email-auth checks aren't edited from this form.

Neutralization (powered-by suppression)

"Neutralization" is the Hide 'powered by HostSSH' toggle. With it on, a live brand's domain renders as a fully unbranded product — the HostSSH wordmark is suppressed so the customer's users never see the upstream vendor. In the table this shows as hidden (green) vs. shown; the KPI Powered-by hidden counts how many brands are neutralized.

How a brand is resolved per request

At runtime the app picks the active brand in a fixed order (lib/brands/resolve.ts):

  1. Operator preview cookie (__brand=slug) — lets any brand be previewed on the platform domain (see below).
  2. Tenant workspace subdomain — a request on ‹sub›.hostssh.com themes with that tenant's brand, if it has one. A claimed-but-unbranded subdomain gets the default theme.
  3. Live custom domain — a non-platform host is matched to a live brand's domain (getBrandByHost, which only matches status = 'live').

Platform hosts (hostssh.com, app.hostssh.com, localhost, *.vercel.app, *.sslip.io) never resolve to a brand — they always show the default HostSSH theme.

Previewing without changing DNS

Preview on a brand row sets the operator preview cookie (previewBrandAction) and opens the site in a new tab, themed as that brand — so you can see any brand on this domain without pointing real DNS at it. The preview cookie is short-lived (one hour) and operator-scoped. Stop preview clears it and returns to the default theme.