White-label — running Merlin under your own brand.

White-label Merlin, for agencies operating it as their own platform.

Merlin runs more than one agency brand from a single platform. A white-label brand is a set of stored settings the platform resolves at runtime, not a fork or a second deployment.

What a brand owns

• Domain — clients sign in at an address you own; the request's host decides which brand loads
• Logo and favicon — served per brand, with the platform default behind them
• Palette — your colours in both light and dark, applied as theme variables at sign-in
• Module mix — the modules you sell; anything else is not part of your brand
• Sender address — system email goes out under your address
• Terms and contacts — your terms, privacy policy, support contacts and business addresses
• Billing — your own billing configuration, so invoices are raised under your entity
• Platform accounts — your own Google Ads manager account and your Analytics and Search Console identities, so client links belong to you

The mobile app reads the same brand record, so it follows your colours too.

What a brand does not change

Branding changes what a client sees. It never changes who can see what. Every query is scoped to the brand and the account it belongs to, and the same rules apply to a partner brand as to ours. Clients authorise their own connections and can withdraw them at any time.

Because it is one codebase, a fix or a new module reaches every brand in the same release.

Getting set up

Partner setup is arranged with Disrupt Digital: you point your domain, hand over your logo and palette, choose your module mix, and connect your own platform accounts.