A white-label platform is software built and maintained by someone else that you sell under your own brand: your name, your domain, your pricing, your customers. The part that matters is not the logo on the login screen but what sits underneath it — who owns the code, the data and the customer relationship when the arrangement ends.
What a white label platform actually is
A white-label platform is a complete product you can resell as if you built it. Three layers travel together: the brand layer (name, domain, look), the product layer (the features customers log in for) and the operating layer (hosting, updates, support). A vendor can hand over all three, or any one of them.
The term is slippery because it gets applied to arrangements as different as a reseller licence and a purpose-built multi-tenant system. Both let you put your logo on it. Only one leaves you holding an asset.
What you own, and what you only rent
Ownership is decided by the contract, not the branding, so settle these before you compare quotes. If two vendors look identical on price, the difference is almost always in this list.
- The code. A licensed product usually stays closed: you get a configuration surface, not a repository. A platform built for you is yours, or licensed to you, and any team you choose can extend it.
- The data. Ask who holds the customer records and whether you can export them in a usable format without permission. “Export available” and “export practical” are different promises.
- The customer relationship. If the vendor invoices your customers or appears on their statements, you do not own the relationship.
- The roadmap. A licensed product improves on the vendor’s schedule. A platform you own improves on yours.
- The exit. Test what leaving costs: migration help, data handover, notice period, and whether the brand layer is portable.
The three white label arrangements
Most of the confusion in this market comes from buyers comparing quotes for three different things. Name the arrangement first, then price it.
- Reseller or SaaS licence. Cheapest and fastest: you resell the vendor’s hosted product under your brand for a per-seat or revenue share. You own no code, and their roadmap is your roadmap.
- Hosted white label. The vendor runs a multi-tenant platform and gives you an isolated branded instance, sometimes with limited extension points. Middle cost, faster than a build, still rented.
- Custom platform you own. A software development company builds a multi-tenant system for you to brand and resell. Highest upfront cost and lead time, and the only arrangement where the platform becomes an asset on your side of the balance sheet.
For the third option, our services set out how a build like this is scoped and priced.
What to specify before the build starts
White-label platform projects fail in the same few places, and every one of them is a decision that has to be made before code is written rather than after.
- Tenancy model. One shared database with a tenant column, a schema per tenant, or a deployment per tenant. This decides your cost curve, your isolation story and how hard a custom request is to grant.
- Branding surface. Which parts a tenant can change — logo, colours, domain, email sender, invoices — and which are locked to keep support tractable.
- Domains and TLS. Whether tenants bring their own domains and who manages certificates at scale.
- Billing and plans. Whether the platform meters usage, seats or transactions, and who can change a price without a release.
- Admin and roles. What an operator can see and do across tenants, and what stays invisible by design.
- Data residency and deletion. Where records live and what “delete my account” actually removes.
White label vs. the alternatives
If you are weighing a licence against owning the platform, the honest comparison is not price but control over three things: the roadmap, the data and the exit.
- Reseller licence: lowest cost, live in weeks, no code ownership, roadmap dictated by the vendor.
- Hosted white label: moderate cost, some extension points, tenant data usually on the vendor’s infrastructure.
- Custom platform: highest cost and build time, full control of code, data and roadmap, plus the maintenance that comes with owning software.
Owning the platform is not automatically correct. If the product is close to a commodity and your advantage is distribution rather than software, renting is the rational choice.
Where these projects go wrong
The recurring failure is a buyer who wants an owned platform but budgets for a licence, then spends the build discovering the difference.
- Pricing a white-label licence as if it were a one-off build, and missing the recurring fee.
- Assuming a licensed product can be extended, when the extension points are a fixed list.
- Committing to a tenancy model before understanding the support load it creates.
- Leaving the exit undefined — no data format, no handover clause, no notice period.
The diligence that exposes these gaps is the same work described in how to choose a software development agency: ask what you receive, not what you are shown.
Frequently asked questions
What is a white label platform?
A white-label platform is software you sell under your own brand while someone else supplies the technology. It can be a hosted product you resell, or a platform built and maintained for you. The branding is the visible part; the arrangement that matters is who owns the code, the data and the customer.
Do I own the code in a white label arrangement?
Only if the contract says so. A reseller or hosted licence normally leaves the code with the vendor and gives you a configuration surface instead. A custom-built platform can be owned outright or licensed to you exclusively, which is a different commercial shape and a different price. See custom app development for how that scope is defined.
How much does it cost to build a white label platform?
Cost tracks the tenancy model, the billing logic and the admin tooling more than the number of screens. A shared-database product with simple plans is a fraction of a multi-tenant system with per-tenant domains, metered billing and operator analytics. Scope those three decisions first — they move the number more than anything else.
Can a white label platform use my own domain?
Yes, and it belongs in the specification rather than being treated as an add-on. The decisions are whether tenants bring their own domains or use subdomains you control, and who manages certificates and DNS at scale. Settle both before the build, because retrofitting per-tenant domains touches routing, sessions and email.
White label vs. custom software: which should I choose?
Choose a licence when the product is close to what you would build anyway and speed matters more than control. Choose a custom platform when the software is the product, the roadmap is your competitive edge, or the data cannot sit outside your control. Owning software also means maintaining it, so budget for that as well as the build.