Vendors use "white label," "co-branded," and "reseller-ready" almost interchangeably, but the models put very different things in front of your customer. The distinction sounds cosmetic until the first time a client forwards you a backup alert and asks, "Who is this company, and why do they have our data?"
The three models
Retail reselling
You sell a product under the vendor's brand and take a referral margin. The customer knows the product, can Google its retail price, and can buy it without you at renewal. Easiest to start, weakest position to defend.
Co-branding
Your logo appears alongside the vendor's: "YourCompany backup, powered by SomeVendor." This looks like a compromise but inherits the worst of both models — you do the selling, yet every e-mail and login page teaches your customer the vendor's name. Over a multi-year relationship, those impressions add up to a price-shopping event.
True white label
Only your identity exists. Software splash, control panel, domain, e-mail sender, restore dialogs, reports — all yours (see the full branding checklist). The infrastructure provider is contractually and technically invisible. Customers can't price-shop a product they can't identify, and every quiet month of successful backups builds your reputation.
Why it matters: retention math
Backup is sticky revenue only if the customer associates the value with you. Consider what each model trains the customer to believe over three years of monthly status e-mails — roughly 36 brand impressions per customer:
- Retail: 36 impressions of the vendor's brand. You're a middleman.
- Co-branded: 36 split impressions. You're a sales channel.
- White label: 36 impressions of your brand. You're the backup company.
When a cheaper competitor comes knocking — and in backup, one always does — the white label customer has nothing to compare against. The product they'd be leaving is, as far as they know, yours alone.
The restore moment
Branding matters most on the worst day. When a client has lost data and is watching a restore progress bar, whose logo is on that dialog? In a white label model, you get full credit for the save. In a co-branded model, the vendor does — and the client now knows exactly who to call directly next time they buy. Data loss events are the highest-emotion, highest-loyalty moments in the entire IT relationship. Don't give them away.
Questions that expose a fake white label
- Is the control panel on my domain, or yours with my logo on it?
- What address do backup alerts come from?
- Does the installer, or any EULA screen, mention your company?
- If my customer calls your support line, what name do they hear?
- Is there a "powered by" footer anywhere — reports, e-mails, docs?
Any answer that isn't "your brand, everywhere" is co-branding wearing a white label costume.
When co-branding is fine
To be fair: if you're testing demand and expect to exit the business within a year, retail reselling is faster and co-branding is acceptable. But if backup is meant to be a durable revenue line, the branding decision compounds like interest — and it's much harder to migrate customers to your own brand later than to start there. Our platform is white label only, by design; see how the setup works or what it costs to start.