White Label Micro Drama App - Vertical Short-Drama OTT with Coin & VIP Monetization, Under Your Own Brand

Yes. Vertical short-form drama is a format rather than anyone’s property, and the commerce patterns behind it – a free opening window, coin unlock, VIP tiers, a check-in streak – are used across the whole category. What you must own is the content. Every episode you publish needs a licence you can produce or a production you commissioned. The platform ships with no catalog attached: the seed script creates structure, not titles.

The platform starts at $3,399 for a launch-ready deployment under your own brand, with the full source code handed over. Scope moves that figure: catalog size, which payment gateway you clear, whether the store build goes out alongside the web app, ad network setup, and the storage and CDN tier your episode library needs. Content licensing and production sit outside this price and are usually the larger line in year one.

Six working days on our side. Because the platform is already built, the work is rebranding it and deploying it to your server. What actually stretches a calendar is what comes from you: brand assets, hosting access, the catalog and episode files, and a merchant account for whichever gateway you switch on.

Four facts are read the moment a viewer opens an episode: is it locked in the catalog, does its number sit inside the free window, is there an active VIP window on the account, and does a per-user unlock row already exist. Coins, a rewarded ad and auto-unlock all write that same row, so the entitlement is identical no matter how it was earned.

Purchased coins come from a coin pack and never expire. Reward coins come from the ladder, ads, referrals and bonuses, and carry an expiry window. Spending always draws the reward balance first, so promotional inventory is consumed before money the viewer actually paid, and the two roll into a single displayed total.

Everything a viewer or an app store reviewer can see. The logo and colour system across the web app, the store build and the operator console; the app name, icon, splash screen and store listing copy; the sender name and templates on transactional email; the coin pack and VIP plan names; the legal pages, which point at your entity rather than ours; and the receipts your payment gateway issues. Inside the codebase, package identifiers and bundle IDs are set to your namespace before the store build is compiled. What does not change is the engineering underneath – the unlock logic, the wallet ledger, the rewards ladder and the analytics – because that is the part you are actually buying.

On the store build, yes – AdMob with your own unit IDs, which is an integration step at deployment. On the web surface the ad unlock is a simulated timed preview rather than a live ad network, so it demonstrates the flow without earning anything. We say so plainly here because it is exactly the kind of thing that otherwise surprises a buyer in week two.

Five: English, Hebrew, Hindi, Arabic and Spanish, with right-to-left layout for Hebrew and Arabic across the consumer web app, the store build and the operator console. An app language editor in the console lets you change client copy without a rebuild. Be aware that some later Hindi, Arabic and Spanish web strings fall back to English, so completing that copy is a configuration task at launch.

Not as shipped. The withdrawal method and request models exist in the schema, with minimum thresholds in settings, so the wallet architecture supports the idea. The consumer flow, the operator payout desk and the bank rails are advanced setup. We describe it as architecture that can support cash-out, never as a live payout product.

Yes, in full: the consumer web application, the Next.js 14 operator console, the Express API with all 33 Mongoose models, the seed catalog script, and the Flutter store build for iOS and Android. Ownership transfers with them – modify, rebrand and extend without licence conditions.

A dedicated VAPT reference maps the platform against the OWASP Top 10, and it is deliberately candid. Shipped controls: hosted checkout with no card data stored, magic-byte upload inspection, a server-enforced view-only demo operator, proxy rules hiding sensitive paths, and native screenshot restriction. The same document prints the backlog: password hashing currently uses reversible encryption rather than a slow hash, request rate limiting is not bundled, CORS defaults open, the client settings payload is unscoped, and staff permissions are enforced in the console rather than on every route. Those are closed with you at deployment.