White Label VPN vs VPN Reseller: What You Actually Own
Many offers say “launch your own VPN brand,” and some of them are free. White label VPN vs reseller is not a question about the logo on the app. It is a question about who holds the developer accounts, the servers, the customer records and the billing, because those decide what you can take with you if the relationship ends.
A reseller sells a provider’s accounts, a white label puts your brand on a provider’s finished apps and servers, and a custom build means the code and infrastructure are yours. Ownership rises in that order, and so do cost and effort. This guide gives you an ownership matrix, a list of questions to put to any vendor in writing, and a hypothetical margin example. Store rules come from Apple and Google, linked as we go.
White Label VPN vs Reseller vs Custom Build: What Each Means
Vendors use these words loosely, so define them in your contract. We use them like this.
- Reseller. In a VPN reseller program you sell a provider’s plans or accounts, usually inside the provider’s apps. You manage customers through a reseller panel (a web dashboard where you create accounts, set expiry dates and device limits) or a reseller API (the same actions over HTTP). The apps, servers and usually the store listing belong to the provider.
- White label. Your brand goes on a provider’s finished apps and infrastructure. The apps carry your name, icon and colors. The code and servers stay with the provider.
- Custom build. Engineers write your apps and backend, and you pay server providers directly. You hold the source code, the accounts and the servers.
- Hybrid. A white label launch with written rights to move later: your own developer accounts and domain from day one, the vendor’s code and servers at first, and a defined path to take either over.
Our guide to white label versus custom VPN development covers the build or buy decision itself. This article is about the ownership detail inside it.
The Ownership Matrix
Read this as typical, not universal. The contract decides each row, and the table’s job is to show you which rows to negotiate.
| What | Reseller | White label | Custom build |
|---|---|---|---|
| Brand | Often the provider’s app with your plan names | Your name, icon and colors | Yours |
| Store listing and developer account | Provider’s | Provider’s or yours, negotiate | Yours |
| Source code | Provider’s | Provider’s, you hold a license | Yours |
| Servers and IP ranges | Provider’s | Provider’s | Yours |
| Customer data | Mostly with the provider | Split by contract | Yours |
| Billing and payment account | You bill customers, the provider bills you | Depends on whose account sells the plan | Yours |
| Support | You answer customers, the provider answers you | Shared, defined in contract | Yours |
| Roadmap | Provider’s | Provider’s, with your requests | Yours |
| Exit path | Win customers back on a new app | App transfer and data export, if contracted | Nothing to exit |
Who is responsible for customer data under privacy law is a legal question, and this is not legal advice. Put it to your lawyer before you sign.
Why the Developer Account Row Decides the Rest
Apple’s App Review Guidelines say in 5.4 that apps offering VPN services may only be offered by developers enrolled as an organization. To enroll as one, Apple’s enrollment page requires a legal entity that can sign contracts, a DUNS Number and a working website tied to the organization. It does not accept DBAs, trade names or branches. Google’s organization accounts also generally need a DUNS number. A reseller whose app lives inside the provider’s account usually does not have to do any of this, which is exactly why the row matters.
Revenue. We could not confirm the payout rules on a primary page, so check them with each store. Our expectation is that the store pays the account that sells the subscription, so whoever holds the account holds the money until they pass it on.
Risk. Guideline 5.4 says apps that do not comply will be removed, and the developer may be removed from the Apple Developer Program. Google’s VpnService policy says non declared uses may lead to suspension of the app or termination of the developer account. Both penalties land on the account, so a shared account shares fate.
Template rules. Apple’s guideline 4.2.6 says apps from a commercialized template or app generation service are rejected unless submitted directly by the provider of the app’s content, and that such services should not submit apps on behalf of clients. Guideline 4.3 says not to create multiple Bundle IDs of the same app and not to submit apps that are indistinguishable from what is already widely available, and Google’s Spam policy lists creating multiple apps with highly similar functionality, content and user experience as repetitive content. How a reviewer treats a white label app that shares code with many others is a question for the vendor.
Exit. Apple lets the Account Holder transfer an app, and the app keeps its reviews, ratings and Bundle ID. Google’s transfer process moves users, ratings and subscriptions, but earnings reports and earlier orders stay behind. Both start with whoever holds the account. If the listing is yours, leaving is a code and server question. If it is the vendor’s, leaving starts with a favor.
Questions to Put to Any Vendor in Writing
Send these before you pay anything, and keep the answers. Our guide to choosing a white label VPN provider covers the wider buying criteria.
- Whose developer accounts publish the app? Ask for the legal entity name on the Apple and Google accounts and who holds the owner roles.
- Who holds the signing keys and the right to upload builds?
- If the accounts are theirs, will they transfer the app to mine on request? Get the notice period and any fee in the contract.
- How many other apps ship from the same code, and who submits them?
- What source code do I receive? Full source with build scripts, a license to use, or nothing? What happens to my apps if you close?
- Who controls the servers, IP ranges and domains my users connect to? Can I move users to my own servers without forcing an app update?
- What do you store about my customers, for how long, and what may you do with it? Get the commitment in writing, in line with guideline 5.4.
- Who is the merchant of record, and where do store payouts and card payments go? Can I export subscriber and billing records?
- Who answers my customers, and who owns an outage? Ask for hours, response targets and how you will hear about incidents.
- What happens when I leave? Notice period, export format, transition help, and any clause that limits selling to the same users afterward.
- How do you make money on a free or cheap plan? And do you or your affiliates run consumer VPN brands that compete with mine?
The Economics, With a Hypothetical Example
Margin per user is the number everyone quotes. The numbers that move the answer are churn and support load, and they depend on how much of the product you control. Our guide to white label VPN pricing models covers the fee structures themselves.
Here is a hypothetical plan. Every figure is invented to show the arithmetic. Price is $6.00 a month, and store or payment fees are set to 15% of price ($0.90), which matches Apple’s Small Business Program rate. The vendor charges $1.50 per active user a month. Each user sends 0.30 support tickets a month at $4.00 each ($1.20). Monthly churn is 8%, so expected lifetime is 1 divided by 0.08, or 12.5 months. Acquiring a user costs $20.
Net margin per user per month is price, less fees, less vendor fee, less support: 6.00 less 0.90 less 1.50 less 1.20 leaves $2.40. Lifetime margin is net margin divided by monthly churn, so $2.40 divided by 0.08 is $30.00.
| Scenario | Net margin a month | Expected lifetime | Lifetime margin | After $20 acquisition cost |
|---|---|---|---|---|
| Baseline | $2.40 | 12.5 months | $30.00 | $10.00 |
| Vendor fee rises $0.50 | $1.90 | 12.5 months | $23.75 | $3.75 |
| Churn rises to 10% | $2.40 | 10 months | $24.00 | $4.00 |
| Tickets rise to 0.45 a user | $1.80 | 12.5 months | $22.50 | $2.50 |
| All three together | $1.30 | 10 months | $13.00 | Loss of $7.00 |
Each change alone leaves a profit. Together they turn the plan into a loss. A reseller can negotiate the vendor fee but has little say over app quality, server health or ticket volume, so two of the three levers sit with someone else. Under white label you get some of them, and under a custom build you get all of them, along with the bill.
Which Model Fits Whom
| You are | Lean toward | Watch for |
|---|---|---|
| Testing demand with an existing audience, no legal entity yet | Reseller | No listing of your own, no data portability |
| Wanting your brand in the stores within weeks | White label under your own accounts | Exit and transfer clauses |
| Running VPN as the core business, or raising money | Hybrid with takeover rights, or custom | Cost and time to launch |
Our own white label VPN page describes what we offer, including that we run the servers, your customers are yours, and revenue settles to your account rather than passing through ours. The rows that page does not settle, such as developer account ownership, source code access and exit terms, are agreed in the contract, so put questions 1 to 11 to us as well.
The “Free” Reseller Offer
If you are looking at a white label VPN reseller free offer, the honest reading is that free is a pricing structure, not an absence of one. Someone pays for the servers and the support. We cannot see inside any vendor’s finances, so we will not guess how a given offer is funded. Ask the vendor to state it: a markup on each account, a revenue share on your sales, a minimum purchase, a paid tier you must move to at a user count, or anything involving your users’ data or traffic.
The last one is the red flag. Guideline 5.4 says VPN apps may not sell, use or disclose any data to third parties for any purpose, and must commit to that in the privacy policy. An offer that depends on user data puts your listing at risk.
FAQ
Is a VPN reseller the same as a white label VPN?
No. A reseller sells a provider’s accounts, usually on the provider’s apps and panel. A white label puts your brand on the provider’s finished apps. The deciding factor is who holds the developer accounts, code, servers and customer data.
What is a VPN reseller panel?
It is a web dashboard where you create customer accounts, set plan limits and expiry dates, and see usage. A reseller API does the same over HTTP. Neither gives you ownership of the apps or servers behind it.
Do I need my own Apple developer account for a white label VPN?
Someone’s organization account has to publish the app, because Apple’s guideline 5.4 allows VPN apps only from organizations. Whether that is yours or the vendor’s is the question to settle in writing.
Can I move from reseller to white label or custom later?
Yes, but how painful it is depends on who holds the listing and the customer records. If both are the vendor’s, your users may have to install a new app and sign in again, so plan for some churn at the switch.
Takeaway
Whichever way you lean on white label VPN vs reseller, compare the ownership matrix row by row and get the answers in writing. Price differences between models can be smaller than the cost of discovering, at exit, that the listing was never yours.
Not sure whether a reseller deal, a white label launch or a custom build fits your plan? Tell us your market and budget on the contact page, and we will tell you what we would do in your position.
Last checked against Apple’s App Review Guidelines, Apple’s developer enrollment and app transfer pages, Apple’s Small Business Program page, and Google Play’s VpnService policy and account and transfer help pages on 8 November 2026.