White-label
Micro drama app, white-labelled for you
A customizable short-drama streaming app under your branding. Original code, finished under your branding, scoped in writing before any build starts.
What it typically includes
- Episode feeds, unlocks and watch progress
- Subscriptions, coins or ads as scoped
- Content management for series and episodes
How white-labelling works
- Your name, logo, colours and domain throughout the product.
- Store listings and support channels under your company.
- Your content, your terms and your customer relationships.
Related reading
Scope areas for this kind of build
Overview
Launch a Short-Drama App as Your Own
- Name, palette, catalog and coin pricing are operator settings, so the product reaches your market as your brand rather than as a licensed skin a viewer could recognise.
Viewer App - Watch & Unlock
- What a viewer sees: banner rails, trending, new releases, coming soon, For You trailers, search, and a vertical episode player carrying lock, comments, likes and subtitles.
Coins, VIP Plans & the Rewards Ladder
- Where the money moves: coin packs with bonus coins, VIP plans by validity window, a seven day check-in ladder, ad reward tasks, social follow and email bonuses, and referral credit.
Cinema Operations & Governance
- Running it day to day, from its own subdomain: overview analytics, film category and list, episode reorder, users and wallets, coin and VIP plans, reports, staff roles and settings.
Modelled Reference - A White Label Micro Drama Deployment
A modelled reference deployment showing how this platform is configured for a regional operator taking it to market under its own name and its own catalog. This is not a client engagement, and the figures are properties of the platform rather than results reported by a customer.
A regional short-drama service launched on this platform under its own brand, with coin unlock, VIP windows and a rewards ladder live from day one.
What Is a White Label Micro Drama App?
Vertical drama sells in ninety-second pieces, which makes the platform underneath it a paywall with a player attached. Categories, titles and numbered episodes sit on one side. A wallet that decides free window, coins, rewarded ad, or an active VIP period sits on the other. White label means both sides carry your name from the first frame, and the source code that runs them is handed to you.
Not a Rental Platform
- Handover, not access: the source, the 33 model schema and the seed script are yours. No per-seat fee, no dependency on our roadmap, and a standard MongoDB underneath.
Honest About Readiness
- Three things are stated up front rather than found later: web ad unlock is a simulated preview, passwords use Cryptr rather than bcrypt, and cash-out exists as data architecture only.
- 01 Vertical episodes with a configurable free window
- 02 Coin, rewarded ad and VIP unlock on the same episode
- 03 Reward and purchased coin split with expiry
What Does White Label Ownership Mean Here?
- The viewer app, the store listing and its icon, the episode player, the coin store, the transactional emails, the invoices, the VIP badge and the operator console all render your name and nothing else. There is no vendor watermark on the player, no attribution line in the footer, and no third-party name in the app store metadata a viewer reads before installing.
- The full source code is handed over: the consumer web application, the Next.js operator console, the Express API with all 33 Mongoose models, the Flutter build and the seed catalog script. It deploys on your server, your domain, your merchant account and your own ad network IDs. Coin balances, viewer records, watch history and payout data sit in a database you hold, and you can read, export or migrate them without asking us.
Micro Drama Platform Features - Catalog, Unlock, Wallet, Rewards & Operations
Catalog & Content Types
- Publishing runs straight from the console: categories, titles typed as movie or web series, and numbered episodes, with episode 0 reserved by convention as the trailer.
- Categories, titles and numbered episodes
- Movie and web series content types
- Episode 0 as the trailer convention
Discovery Rails
- Five rails carry the home screen - banner carousel, trending, new releases, coming soon and category - and coming soon titles are excluded from every other rail, so an unreleased title never leaks onto a shelf.
- Banner carousel, trending and new release rails
- Coming soon rail with an announce date
- Category rails grouped from the catalog
Search & My List
- Matching runs on title and plot with an optional genre filter on both consumer surfaces. My List is held at series level, and continue watching stays on the client.
- Search on title and plot with an optional genre
- For You trailers grouped by title
- My List at the series level
Vertical Episode Player
- Playback is sequential and carries a subtitle track, likes, episode comments capped at 400 characters, reports, share, and immersive fullscreen on the store build.
- Vertical episode player with sequential play
- Subtitle track from a stored VTT or SRT file
- Likes, episode comments capped at 400 characters
Three Ways to Unlock
- The free window is set globally, coin unlock is priced per episode, and rewarded ad unlock carries a per-title daily cap, with auto-unlock available for the remainder of a title.
- Free episode window set from one setting
- Coin unlock priced per episode
- Rewarded ad unlock with a per-title daily cap
Coin Wallet with Expiry
- Reward and purchased balances are tracked apart, spend draws reward first, promotional balances expire on a configurable window, and a typed ledger sits behind every movement.
- Reward coins and purchased coins tracked apart
- Spend draws reward coins first
- Promotional coins carry an expiry window
Coin Packs & VIP Plans
- SKUs carry a bonus coin allowance and an offer price, sell through hosted checkout or a store billing flow, and land in a purchased balance that never expires.
- Coin packs with bonus coins and an offer price
- VIP plans by validity and validity type
- PayPlus hosted checkout with no card data stored
Rewards Ladder
- Return visits are bought with inventory rather than cash: a seven day check-in with a streak, ad reward tasks under a daily cap, social follow and email bonuses, a login bonus, and a referral loop that credits the referrer.
- Seven day check-in ladder with a streak
- Ad reward tasks with a daily cap
- Social follow bonuses on your own channels
Operator Analytics
- Everything reads live operational data: overview counts and charts, user analytics, monetization and the coins economy, and performance at both series and episode level.
- Overview, user, monetization and coins analytics
- Series and episode level analytics
- Order history for coin and VIP purchases
Operator Console - Catalog, Economy, Staff & Settings
Admin Console Sections
- 01 Overview Date bounded counts with user and revenue charts plus a paid revenue trend, reading live operational data rather than a warehouse.
- 02 User Management Paginated users with search and country filter, profile and history views, wallet inspection, a block toggle and a balance adjustment.
- 03 Monetization & Coins Paid revenue monitoring, series revenue breakdown, top revenue episodes, and coin economy analytics tied to the ledger codes.
- 04 Film Category & List Genre buckets plus titles with poster, banner, type, trending, coming soon, auto-animate and active toggles, and region chips for targeting.
What an engagement can include
Delivery here is a handover, not access. You receive the application source, the schema behind it, and the documentation a technical buyer will ask to see. Ownership transfers in full: no runtime licence, no per-seat fee, no revenue share, and no dependency on what we choose to build next.
Full Source Code
- Four codebases transfer: the consumer web application, the Next.js (version confirmed in writing) operator console, the Express API and the Flutter store build. Modify, rebrand and redeploy them without licence conditions.
- Consumer web application on Vite and React
- Operator console on Next.js (version confirmed in writing)
- Express API with Mongoose models
33 Model Schema
- Six domains are modelled on MongoDB - identity, catalog, engagement, messaging, commerce and configuration - with a seed script and indexes placed on the paths the player and the ledger actually hit.
- 33 Mongoose models on MongoDB
- Indexes on the catalog and ledger hot paths
- Unique compound keys on the unlock rows
Consumer Web App
- Vertical episode player with subtitle track
- Rails, search, For You trailers and My List
- Store, rewards ladder and referral
- Legal CMS pages and a language picker
Flutter Store App
- Five tabs, episode-wise reels, coin and ad unlock, wallet histories, rewards quests, five locales, referral, and native screenshot restriction on the device.
- Five locales with right-to-left layout
- App language JSON editing in the console
- Series language catalog kept separate
Operator Console
- Overview and analytics sit alongside catalog and episode modules, users and wallets, plans and orders, reports, staff roles, campaigns and the settings tabs.
- 24 permission modules across four actions
- Block, comment hide and report queue
- Campaign desk with an in-app inbox
Payments & Wallet
- PayPlus hosted checkout leads, with four further gateway switches behind it, plus coin and VIP plans, a typed ledger, and reward coin expiry handled in the wallet helpers.
- Coin and VIP plan modules with order history
- PayPlus hosted checkout plus four more switches
- Reward tables across four operator tabs
Upload & Storage
- Storage is a switch across local disk, AWS S3 and DigitalOcean Spaces. Magic-byte inspection sits in front of it and discards renamed executables, archives and PDFs.
- Storage switch across local, S3 and Spaces
- Magic-byte inspection on every upload
- Midnight crons resetting the ad counters
Technical Documentation
- Entity relationship and schema references
- Complete API collection across both routers
- Developer and security handbook
- VAPT posture, PRD and feature catalogue
Who Is This White Label Micro Drama Platform Built For?
This fits operators who hold or license vertical drama and want to charge for it episode by episode instead of asking every viewer for a monthly commitment.
Producers who already own vertical series and need a storefront, a wallet and an operator console rather than another distribution deal on somebody else s terms.
Micro Drama Use Cases - Studios, Regional OTT, Licensors & Publishers
Which part leads changes with the operator; the codebase does not. A studio leads with catalog and episode pricing, a regional service with locales and the payment rail, a licensor with reporting. All three are configuration, and none of them is a fork you then have to maintain.
Run an owned catalog of vertical series with episode level coin pricing, a free window you can move from a settings screen, and analytics that show which titles and which episodes actually convert.
Industries We Serve
Anyone selling access to episodic short-form drama is running the same shape of business, and the platform is built around that shape rather than around one operator s catalog.
How a Micro Drama Platform Works - Discover, Watch, Unlock & Convert
From the outside this looks like a player with a paywall in front of it. Underneath it is a tightly sequenced catalog, entitlement and wallet pipeline. What follows is the path a viewer actually takes, from a first rail to a paid unlock to a return visit.
Viewer Journey, From First Rail to Paid Unlock
- 1 Enter and Discover A viewer arrives with no account required. Guest entry creates a durable identity so rails, My List and rewards all work before any payment instrument exists. Guest entry, or email and password on both surfaces
- Banner carousel, trending, new releases and coming soon
- Search across title and plot with an optional genre
- For You trailers grouped by title
Technology options we may propose
Behind the player, three things have to hold: a wallet that cannot drift, an unlock decision made identically on every client, and a console that stays usable as the catalog grows past a few hundred titles. Here is how each one is built.
How we would design for scale
Catalog Reads Under Rail Load
- Rails and search are where the read load lands, so the catalog is indexed on visibility and release date instead of falling back to collection scans.
- Indexes covering active titles and release date
- Start and limit pagination on every list endpoint
- Coming soon titles excluded from the other rail queries
Unlock Lookups That Stay Cheap
- Every episode view has to answer one question does this viewer already own this episode so the rows are keyed to answer it in a single hit.
- Unique compound key across viewer and episode
- Unique compound key across viewer and title for auto-unlock
- Catalog lock and free window resolved without a join
A Wallet That Reconciles
- A coin economy is only credible while any balance can be explained, so nothing moves by silent field update every movement writes a typed ledger row.
- Reward and purchased balances held apart
- Seven typed codes spanning earn and spend
- Expiry applied ahead of any credit or spend
Media Off the Application Host
- Episode bytes have no business passing through the API process, which is why storage is a switch rather than an assumption.
- Local disk, AWS S3 or DigitalOcean Spaces, one active at a time
- Magic-byte inspection before any file is accepted
- Static consumer web served directly by the proxy
Static Consumer Web
- The viewer application is a static build served by the proxy, so browsing and playback never occupy the API process.
Indexed Hot Paths
- Visibility, release date, ledger timelines and unlock lookups are all indexed, which keeps the busiest queries cheap as the catalog grows.
Storage as a Switch
- Local disk, AWS S3 or DigitalOcean Spaces, exclusive and operator selected, with a CDN in front of the bucket as a deployment choice.
Process Model
- A process manager sits behind the proxy running both the API and the console, so adding capacity is an instance decision rather than an architectural one.
Upload Safety Built In
- Magic-byte inspection reads the first bytes of every upload and discards executables, archives, PDFs and markup before the controller runs.
Micro Drama Content Rights & Platform Readiness - What the Software Provides and What Stays Yours
A white label micro drama app is software, not a content licence or a certification. Omnistu builds and hands over the catalog, entitlement, moderation and wallet tooling this page describes. The titles you stream, the rights behind them, and your obligations under local law stay with you as the operator.
What Stays the Operator s Job
- Licensing every episode you publish, including music and regional rights, any DRM vendor your licensors require, your terms and privacy policy, and the people who work the report queue. The software enforces the regions and locks you enter; it does not acquire the rights behind them.
Local Law Decides the Rules
- Catalog & vertical player
- Coin & VIP wallet
- Operator console
- 1 Pick the modules Choose at launch, or add later - the core never needs a rebuild.
Micro Drama Revenue Models - Coins, VIP, Ads & Licensing
Revenue arrives from four directions at once here, and each is modelled as its own lever, so raising one does not quietly damage another.
because they are aimed at two different people: the viewer who spends at midnight to find out how it ends, and the one who has decided this is now a habit.
Describe your Micro drama app
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.comMore pages on this build
4 pages describing this proposed build.