White-Label IPTV App — What You Actually Get, and What to Watch For

2026-08-28 · Business · 5 min read

If you sell IPTV subscriptions and your customers use a third-party player, you have a problem you can probably name: the app is the product they touch every day, and it carries somebody else's name. Support requests come to you and the software is not yours to fix.

A white-label player addresses that. This post covers what a licence actually includes, the four ways they are sold, and the terms that decide whether you end up owning a business or renting one.

We license Xtiva this way, so treat this as an informed but interested account. The questions below are the ones we would ask a supplier, including us.

What is actually in the box

Branding. Your name, icon, splash screen and colours. Sometimes your typeface. The interface itself is the same player underneath — that is the point of white-label, and any supplier claiming a bespoke interface at this price is describing a colour change.

Server pre-configuration. Your portal address compiled in, so customers enter only a username and password rather than a server URL. This is worth more than it sounds: the server field is where most customer setup failures happen, and removing it removes a support burden.

A store listing. Under a developer account — and whose account is the question that matters most, covered below.

Updates. New versions as the base player develops. Ask specifically whether these are guaranteed or discretionary, and what happens to your app if the supplier stops.

Support. Usually to you, not to your customers. Your customers remain yours to support, which is the arrangement you want.

The four commercial models

One-off rebrand fee. A few hundred dollars, an APK delivered, no ongoing relationship. Cheapest, and you own a binary that will not be updated. When Android's next release breaks something, you pay again or you are stuck. Reasonable only for a genuinely short-term need.

Flat monthly licence. A fixed fee regardless of subscriber count. Predictable, scales in your favour, and keeps your numbers private. This is the model we use, and we would argue for it whoever you buy from.

Revenue share or per-subscriber. A percentage, or a fee per active user. Attractive at the start because it costs almost nothing while you are small. It requires reporting subscriber numbers to a supplier, and the cost grows exactly as you succeed. It also means the supplier knows the size of your business, which is not information you owe them.

Full platform. Player plus middleware, billing, transcoding and CDN. Enterprise pricing, long procurement, and appropriate if you are building an operator-grade service. Overkill if you have a working panel and need an app.

The questions that decide the deal

Who owns the developer account? The most important term here. If the supplier publishes under their account, they hold your listing, your reviews, your install base and your ability to ship an update. Leaving means starting from zero — new listing, no reviews, no installs, and customers you must migrate by hand. Some suppliers rely on this. Insist on publishing under your own account.

What happens if you leave? Ask directly. Do you keep the app, in any form? Do your customers keep working? What is the notice period? A supplier who is unclear here has told you something.

What happens if they disappear? Many IPTV app suppliers are one person and a rebranding script. If they stop answering, is there any path to keeping your app updated?

Who handles store rejection? This is the one people do not ask and should. Branded IPTV apps are rejected routinely, and the reasons are specific and largely avoidable — we have written about the Google Play policy surface for IPTV apps in detail. Establish whether the supplier will work through a rejection with you or hand you a compliance document and wish you well.

Is the source of updates guaranteed? "We will keep it updated" is not a commitment. Ask what happens when Android's next target API requirement lands, because that one has a deadline and non-compliance removes your listing.

Can they see your subscribers? In a properly built player, credentials go from device to your panel and the app supplier sees nothing. Confirm it, because the alternative means a third party holds your customer list.

What white-label does not fix

Worth being blunt, because it is oversold.

It does not make an unlicensed service lawful. A branded player is still a player. If the underlying service redistributes content without rights, branding changes nothing about that — it only puts your name on it. This is not a technical caveat; it is the whole of your legal exposure.

It does not survive a bad service. If streams buffer, the app carrying your name is what customers blame. A player cannot improve a stream it was given.

It does not remove support. Customers will contact you about their setup, their television, and their network. The app helps at the margin.

It is not a differentiator on its own. Every serious reseller has a branded app. It is table stakes — the absence is noticed, the presence is not.

What a sensible arrangement looks like

Flat monthly fee, no revenue share, no per-subscriber reporting. Your developer account, your listing, your reviews, your install base. Updates included and specified. Credentials never leaving the path between the device and your own panel. Clear exit terms. A named human who answers within a stated time.

That is how we structure Xtiva's licensing — $99 a month for Starter, $199 for Professional, custom for Enterprise, with a build turnaround of about a week. We publish the prices because a supplier who will not is usually pricing by how much you appear able to pay.

The standing note

Xtiva is a media player. It ships with no channels, playlists or streams of any kind — under our brand or yours — and your subscribers supply their own credentials. What you license is software. The service you run on it, and its legality, remain entirely yours.

Next: publishing a branded IPTV app on Google Play without getting rejected, which is where most of these launches actually stall — then moving your existing subscribers onto it, which is where the support load lands.