White-label is not a logo upload: the six places your brand actually has to survive

"White-label" has been diluted to the point of uselessness. It now typically means: you can upload a logo, and the platform's own name appears in a slightly smaller font.

The reason it matters is not vanity. It is that members treat a space with somebody else's branding on it as a place they are visiting, and a space with yours as a place they belong to. If your community lives at yourname.someplatform.com, sends mail from notifications@someplatform.com, and charges cards under a name your members do not recognise, you have not built an asset. You have a tenancy.

Here is the checklist I would use, in the order that actually matters.

1. The address

The bar: your own domain, not a subdomain of theirs, on every page a member ever sees — including login, checkout and the emails' links.

This is the one most platforms do offer, often only on their most expensive tier. Two things to check beyond "do you support custom domains":

• Does verification actually check DNS, or does it just believe you? A setup screen that flips to "Active" the moment you click a button is telling you nothing. In Klaas, "Verify setup" performs a real DNS lookup on the server and reports pending, verifying, active or failed, with a last-checked time. It can say no.
• What happens to sessions on the custom domain? This is the unglamorous one nobody mentions. Cookies do not cross between an apex platform domain and your own domain, which means a member who was signed in on one may arrive signed out on the other. We document that rather than let people discover it. Ask any vendor the same question and watch what happens.

2. The email

The bar: transactional mail sent from your domain, with SPF/DKIM aligned so it lands in inboxes rather than spam.

This one is routinely skipped, and it is the most visible leak of all — your welcome email is the first thing a new member reads, and it is where the platform's name most often shows up uninvited.

The thing to be sceptical of is a vendor that lets you set a display name and calls that white-label email. Changing "Some Platform" to "Your Academy" while the actual sending domain stays theirs means the message still says "on behalf of" or "via someplatform.com" in most mail clients, and it does nothing for deliverability.

Verifying a real sender on your own domain is a small amount of DNS work and it is the difference between mail your members trust and mail they never see. We ask you to do it and we send a real confirmation to a real inbox to prove it works — there is deliberately no dry-run mode, because "the DNS looks right" is not the same claim as "a message arrived".

3. The payment

The bar: the charge on your member's card statement should be yours.

This is the leak nobody puts on a checklist, and it is the one members actually complain about — a line item from a company they have never heard of is a chargeback waiting to happen.

If the platform is the merchant of record, the descriptor is theirs, the receipt is theirs, the refund policy is theirs and the dispute is theirs. If payments run through Stripe Connect into an account you own, all four are yours. In Klaas the Checkout Session is created on your connected account, so the funds, the descriptor and the customer relationship are yours from the first charge. (It is also why we take 0% — there is no point in the flow where we could take a cut.)

4. The look

The bar: it should look like a considered product, not like a generic template with your colour applied to the buttons.

Almost every platform in this space renders the same grey card layout with a configurable accent colour. You can spot them from across the room, which is the opposite of white-label.

Klaas ships eleven complete designed themes — type, colour, corner radius, shadow, light/dark treatment — plus your brand colour, logo, cover and favicon. Notably the brand-colour picker shows a live WCAG contrast readout, because the most common branding failure is not ugliness, it is a brand colour that renders text unreadable and nobody notices until a member with low vision emails you.

We deliberately do not offer a custom-CSS box. That is a longer argument, and it is a real trade-off, not a limitation we are hiding.

5. The small print

The bar: you should be able to remove the platform's name, and you should be able to stay out of their shop window.

Two separate switches, both of which Klaas has:

• "Powered by" removal. Obvious, and the one everybody asks about.
• Directory listing opt-out. Less obvious, more important. Many platforms list every community they host in a public directory. That directory is their lead-generation, built from your members' attention, and it puts a link to your competitors one click from your front door. Ours is opt-in — you are not in it unless you say so.

There is a third, quieter one: whether your own name appears as the host. Some people are building a personal brand and want it front and centre. Others are running an association or a company account and specifically do not want a named individual attached. That should be a switch, not an assumption, and for us it is.

6. The mobile app — and why I would not weight this heavily

Almost every white-label checklist you will read puts "native mobile apps under your own brand in the App Store" near the top, usually with a statistic about mobile traffic attached.

It is worth understanding why that promise is so complicated. Apple's App Store Review Guideline 4.2.6 states that apps created from a commercialised template or app-generation service will be rejected — with the exception that the content provider may submit them under their own developer account. So a genuine per-community branded app is not something a platform can simply switch on for you. In practice it means you maintain an Apple Developer account, you own the submission, you handle review, and you re-submit for every update. Some hosts genuinely want that. Most, on discovering the actual shape of it, do not.

There is a second cost that gets skipped: the moment you sell inside an iOS app, Apple's in-app purchase rules apply to the transaction, and the platform's "0% fee" becomes academic next to a 15–30% store commission on your membership.

I am not saying branded apps are worthless. I am saying that when a vendor lists this as a bullet point with no asterisk, they are either not telling you the whole shape of it, or they have not hit it yet.

What we do today: Klaas Academy runs in the browser on any device, at your address, with your branding, and members do not install anything. That is the honest state of it, and I would rather write that down than imply otherwise.

The one-line test

If you want to compress all of this into a single question to ask a vendor:

"If I send my most sceptical member a link, at what point in the flow — page, email, receipt — do they first see your company's name instead of mine?"

A good answer is a specific one. A vague answer is the answer.