White-label SaaS is one software platform that many businesses can sell or use under their own brand: their logo, colours, domain and emails, with your product running underneath. You build and maintain a single codebase, and each client or reseller gets what looks like their own product. It suits workflows many businesses share, where branding matters more than customisation.
The appeal is obvious: build once, earn many times. The catch is that "build once" is only true if the platform is designed for it from the start. Retrofitting branding, tenant isolation and reseller billing into a single-company product is painful. This explainer covers how white-label SaaS works, the business models behind it, what the platform must include, and what it costs. For the full product journey, start with our guide to building a SaaS product from idea to paying customers.
How does white-label SaaS actually work?
Every client is a "tenant" on one shared platform, and the platform reads that tenant's settings to decide which brand, domain, features and data to show.
When a visitor arrives at portal.clientbrand.com, the platform recognises the domain, loads that tenant's logo, colours and enabled features, and only shows data belonging to that tenant. Behind the scenes, there's one codebase, one deployment pipeline and usually one database cluster.
This rests on multi-tenant architecture, which we explain without jargon in multi-tenant SaaS architecture for non-technical founders. White-label adds a branding and reseller layer on top.
Which white-label business models work?
There are three common models, and the right one depends on who your buyer is and who owns the end customer.
- Agency or reseller model. You sell to agencies or consultants who rebrand the platform and sell it to their own clients. Example: a marketing agency offering a branded reporting portal to each of its clients. You bill the agency; the agency bills its clients.
- Franchise or network model. A franchisor or industry body provides branded software to its members or outlets, each with their own branding or a shared one.
- Direct white-label model. You sell straight to businesses that want "their own" app or portal, such as a booking system, client portal or learning platform, without building it themselves.
| Model | Who pays you | Who supports end users | Pricing pattern | Main risk |
|---|---|---|---|---|
| Agency / reseller | Agencies | Usually the agency, with you as second line | Wholesale per client account or tiered bundles | Resellers who sell poorly or support badly |
| Franchise / network | The franchisor or each member | Shared, defined by contract | Per location or per member | Slow decision-making, many stakeholders |
| Direct white-label | Each business | You | Setup fee plus monthly subscription | Endless customisation requests |
Pick one model to start. Trying to serve resellers and direct clients at once doubles your sales and support complexity.
What must a white-label platform include?
Beyond the core product, white-label needs per-tenant branding, custom domains, isolated data, flexible roles, configurable features and billing that matches your model.
Branding and domains
- Brand settings per tenant: logo, colours, favicon, product name and email templates, editable from an admin screen rather than by developers.
- Custom domains (
app.clientbrand.com) with automatic SSL certificates. - Branded emails sent from the client's domain, which means setting up email authentication records (SPF, DKIM) per tenant so messages don't land in spam.
- No trace of you on client-facing screens if your contract promises that, including error pages, PDFs and notification emails.
Data isolation and access
- Strict tenant separation so one client can never see another's data, enforced at the data layer, not just hidden in the interface.
- Roles and permissions at several levels: platform owner, reseller, client admin, client staff, and sometimes end customers. Our explainer on role-based access and permissions in business software covers how to design these.
- Audit logs per tenant, which larger clients will ask for.
Configuration, not customisation
- Feature flags to switch modules on or off per tenant or plan.
- Custom fields and settings that let clients adapt workflows without code changes.
- Templates for common setups, so onboarding a new tenant takes minutes.
The golden rule: anything a client asks for should become a setting for everyone or not happen at all. One-off code branches for individual clients are how white-label platforms become unmaintainable.
Billing and onboarding
- Tenant provisioning: creating a new branded instance from an admin panel or automatically after payment.
- Billing that fits your model: wholesale billing to resellers, usage reports per client, or direct subscriptions. Our comparison of Stripe vs Razorpay vs Paddle for SaaS billing helps with the payment side.
- A super-admin console for your team to see every tenant's health, usage and billing status.
What about white-label mobile apps?
Branded mobile apps are possible but add real cost and store-review complexity. Each brand usually means a separate app listing, build and update cycle.
Options to weigh:
- One shared app that loads a client's branding after login. Cheapest to maintain, but the store listing carries your brand.
- Separate branded apps per client, built from one codebase. Clients get their own listing; you take on many store submissions. Apple's App Store review rules are strict about apps generated from templates, and often expect each branded app to be published under the client's own developer account, so plan for that.
- A progressive web app with each client's branding, installable from the browser, avoiding store submissions entirely.
How much does a white-label SaaS cost to build?
A white-label platform typically costs more than a single-brand SaaS of the same features, because branding, domains, tenant management and multi-level roles are extra work. Using GRWW's shared reference ranges (estimates that vary by scope):
| Stage | Global (USD) | India (₹) | Australia (AUD) |
|---|---|---|---|
| MVP with basic tenant branding | $15k–50k | ₹4–12 lakh | $25k–80k |
| Mid-size white-label platform (custom domains, reseller roles, billing) | $50k–150k | ₹12–35 lakh | $80k–250k |
| Complex platform with marketplace or deep integrations | $150k+ | ₹35 lakh–₹1 crore+ | $250k+ |
| Cross-platform mobile app add-on (simple–mid) | $25k–90k | ₹4–15 lakh | $40k–150k |
Timelines are typically 8–16 weeks for an MVP and 4–9 months for a mid-size platform. Budget annual maintenance at roughly 15–25% of the build cost; on white-label platforms, upkeep also includes onboarding support and domain or email issues across many tenants.
When is white-label a bad idea?
- When every client wants something different. If deals depend on bespoke features, you're running a custom development agency with a shared login, not a SaaS.
- When you lack a distribution channel. White-label works because resellers or networks bring customers. Without them, you're just selling SaaS with extra complexity.
- When margins can't support two layers. Reseller pricing has to leave room for both you and the reseller to profit.
- When support responsibilities are vague. Define in contracts who handles end-user questions, outages and data requests.
- When compliance differs sharply by client, such as strict data-residency rules for some tenants but not others, unless you've planned for regional hosting.
Frequently asked questions
What's the difference between white-label and private-label SaaS?
The terms are often used interchangeably. Some people use "private label" for a product made exclusively for one brand, and "white label" for a product rebranded by many. In software, what matters is whether the platform supports many brands from one codebase.
Can I white-label an existing SaaS product?
Yes, but it usually needs work: tenant-aware branding, custom domain support, branded emails and stronger permission levels. If the product wasn't built multi-tenant, data separation may need redesigning, which is the expensive part. A short technical audit will show how much change is needed.
How do resellers usually pay for white-label software?
Common patterns are a wholesale price per client account, tiered bundles of accounts, or a revenue share. Many platforms also charge a one-time setup or onboarding fee. Choose a model that rewards resellers for growing while protecting your margins.
Who owns the customer data on a white-label platform?
That's set by contract, not technology. Usually the client business owns its customers' data, and you process it on their behalf under data protection laws such as India's DPDP Act or Australia's Privacy Act. Make data ownership, export rights and deletion responsibilities explicit in your agreements.
How long does it take to onboard a new white-label client?
On a well-built platform, setting up branding, a domain and initial users can take minutes to a day. Delays usually come from DNS changes, email authentication setup and data imports on the client's side. Templates and a self-serve setup wizard shorten this considerably.
Planning a platform you can sell many times?
A white-label platform lives or dies on decisions made in the first few weeks: tenancy, roles, branding and billing. We help teams make those calls and build the platform around them. Explore our services and past projects, or get a fixed-price plan for your white-label product.