White label

White label puts your name on the product. Your team, your publishers and anybody you invite see your brand, your colours and your domain in the console and the publisher portal, and the emails the platform sends on your behalf carry your name.

After this page you can decide whether white label is worth it for your business, get it switched on, and know what changes and what deliberately does not. It is sold as the White label + custom domain add-on, on top of any plan, and is included outright on plans that bundle it. What it costs and which plans include it are on the pricing page.

What changes

A brand is more than a logo: the palette, the shape and weight of buttons, the menu's density, the type family, the layout width and the sign-in page's layout are all part of it, and each is previewed live as you change it. You can also choose which surfaces it applies to, so a brand can go live on the publisher portal before the console if that is the order you want.

Getting it switched on

1. 1

   Ask for it

   From Branding in the console. Requesting costs nothing and does not need the feature — asking is the step before having it — and you can withdraw a request that has not been answered.

2. 2

   We grant it

   White label is granted by us, not switched on by a form. Once it is granted, the editor opens and the custom-domain section unlocks.

3. 3

   Design it

   Upload a logo for light and dark, pick a primary colour, and check the live preview in both themes. The rest of the palette is derived from that one colour so contrast stays readable.

4. 4

   Connect your domain

   Add the host you want to use — calls.yourcompany.example, say. The console gives you one TXT record to publish; add it at your registrar and press Verify. A real DNS lookup decides, and a certificate is issued when it passes.

5. 5

   Publish

   Publishing is going live. Until you publish, everything you have designed is a draft that only you can see; publishing takes a snapshot and that snapshot is what everybody is served. Unpublishing takes it back to a draft without deleting anything.

The five states a brand can be in

Your own domain

• The record is a TXT record on a _buy3-verify subdomain of the host you are claiming, with a value unique to you.
• Verification is a real resolver lookup asked of more than one server, so a cached negative answer from before you published does not fail you.
• Press Verify again after a change; DNS can take minutes or hours to propagate, and nothing is lost by checking twice.
• Your first domain becomes the primary one. A host already claimed by somebody else is refused.
• Enter a bare hostname — no protocol and no path. portal.youragency.example, not https://portal.youragency.example/login.

Email: the look and the envelope

These are two separate questions with two separate answers, and they usually do not arrive together. The look — your name, logo, colour and footer — comes from your published brand and applies the moment you publish. The envelope — the address mail is actually sent from — needs a DNS-verified sending domain, because no provider will send from a domain you have not proved you own.

Setting up a sending domain is the same shape as the custom domain you already did — type it, publish the records your registrar needs, and the platform polls until it verifies. Per-record failures come back as sentences rather than a red cross.

What does not change

• Your data does not move. It is the same workspace, the same calls, the same reports — under a different skin.
• Permissions do not change. A publisher still sees only their own side, and white label does not give anybody access they did not have.
• The platform's own addresses still work. Your own domain is an additional way in, not a replacement that can lock you out while DNS is broken.
• Nothing about billing changes. Your plan, your wallet and the per-minute rate are the same — see Billing and usage.

Worked example: a publisher-facing launch

You are onboarding eight publishers next month and you would rather they never see another platform's name.

1. Request white label now, not the week before. It is granted by a person, and a domain needs DNS to propagate.
2. Design the brand against the publisher portal first. That is the surface your partners live in, and the console can follow later.
3. Add partners.youragency.example as your custom domain and publish the TXT record. Press Verify; if it fails, read the sentence — the usual cause is a registrar that appends your domain, so the record ends up one level too deep.
4. Set your support address in the brand, so replies to invitations reach you rather than us.
5. Start the sending domain at the same time. You can invite publishers before it verifies — your name is already on the message — and the From address improves quietly when it lands.
6. Publish, then invite one publisher and look at what they got: the invitation email, the sign-in page and the portal. That round trip finds anything you missed in ten minutes.
7. Check the activity log: the request, each branding change, the domain and its verification are all entries, so "when did the portal change" has an answer.

When something looks wrong

Next steps