White Label Video Streaming Platform Features: By Role
An OTT service has three kinds of user, and each needs a different set of screens. Viewers want to press play and be recognized. Producers want to watch their minutes add up and be paid for them. Operators want to approve, price and measure everything. This page covers the platform underneath the video streaming clones, sorted by who touches each feature.
Book a Live Demo →See PricingFeature Set by Role
Viewer apps are what people picture when they hear "streaming". The producer side is what turns a personal library into a network where partners supply the catalog, and it is the part a simple video script tends to skip.
Viewer
- Sign-in by email, social login, one-time code or QR session
- Several profiles per household, plus a kids profile with maturity filtering
- Hero banners, trending rows, genre shelves, cast and crew browsing
- Films, seasons and episodes, standalone videos and trailers
- Live channels by category, open to all or gated by plan
- Weekly, monthly or annual plans, single rentals and pay-per-view unlocks
- Quality selection, subtitles and alternate audio on every player
- Offline downloads and 360 VR-ready viewing where content and device allow
- Watchlist, plus Continue Watching that follows the viewer across devices
- Invoices for every renewal, rental and purchase
- PIN and parental lock, with push notifications for new releases
Producer
- A separate login and dashboard, apart from the admin console
- Content proposals carrying documents and contract terms
- Films, series, video and live TV submitted for review
- Views and watch minutes reported per title
- Revenue share visible as it builds up
- Bank details on file and payout requests raised in the panel
- Performance analytics for their own catalog
- Nothing goes live until the operator says so
Operator
- Approve or reject producer submissions before publishing
- Arrange films, series, episodes, banners, trailers and metadata
- Set plan prices, durations and limits, plus rental windows and PPV prices
- Run coupon campaigns scoped to a plan or a single title
- Review watch-minute logs and clear payout requests
- Manage viewers, devices, sessions and live TV channels
- Control app versions, mandatory updates and feature flags per platform
- Roles, reports, notifications, backups and branding from one console
Test the producer column hardest. A platform that models only viewers and an admin can run your own library, but it cannot run a business where other people's titles earn them money.
Rented Platform vs One-Time Script vs Miracuves Platform
Three ways to get a streaming service running, compared on the rows that decide an OTT launch. Market figures are indicative ranges from the open market, and vendors vary.
| Capability | Rented or hosted platform | One-time script | Miracuves platform |
|---|---|---|---|
| Cost shape | A recurring fee, roughly $399 to $3,900 a month for hosted OTT and $49 to $499 for creator-video tools | A one-time purchase, roughly $250 to $1,500 | $3,699 one time for the ready-made package |
| Apps | Varies by plan, and store listings often sit under the vendor | Cheaper tiers often ship web-view apps rather than native ones | Flutter apps for Android and iOS plus a web app that installs as a PWA |
| Ways to earn from a title | Often centered on one model, usually subscription | Frequently plans only | Plans, rentals and pay-per-view on the same catalog, plus coupons |
| Producers and partners | Rarely offered | Usually absent | A producer panel with watch-minute revenue sharing and payout requests |
| Bringing in outside catalog | Depends on the vendor | Typically one title at a time by hand | A content acquisition API with a proposal workflow behind it |
| Live channels beside on-demand | Varies | Seldom both in one app | A live TV module in the same apps |
| Source code | You rent access, so you never hold it | Some vendors withhold it from every published tier | Complete and unobfuscated, handed over with the database |
| Where the video sits | On the vendor's infrastructure, with delivery folded into the fee | On your own servers | On the cloud and CDN accounts you choose |
| Studio-grade DRM | Varies by vendor | Rarely offered | Enterprise scope, quoted separately |
| Time to live | Quick, on the vendor's terms | Setup and app work fall to you | Six working days |
White label here means a handover. If a provider keeps the source, controls the deployment or takes a cut of your subscriptions, that is a license with your logo on it. Note also that a subscription can bundle hosting and delivery, so the fair comparison is a one-time software price against a recurring fee, not a promise of a lower total.
How It Works, End to End
Follow a single title through the whole platform, from the moment a producer proposes it to the moment they ask to be paid.
The producer proposes and attaches terms
A submission arrives with its documents and contract terms, not as a live upload. Keeping the proposal separate from publishing is deliberate, because on a network the operator's editorial and rights decisions are the asset being protected.
Admin review ends in approve or reject
Someone on your team reads the proposal in the console and decides. Approval publishes it, and you then choose how it earns: inside a plan, as a rental, as a pay-per-view unlock, or in a premium bundle. One title can sit in several of those together.
The title is placed where viewers look
Banners, carousels, genre pages and Top 10 shelves are arranged by you, so the front page reflects an editorial choice rather than an upload date. Series with seasons, trailers, standalone videos and live channels share the same structure.
A viewer gets access one of three ways
Through a live plan, a rental with a window that runs out, or a single pay-per-view purchase. Coupons apply at checkout, an invoice is issued and the purchase joins their history. Ask to see a lapsed rental in the demo and confirm that playback stops.
Playback keeps its place per person
Streams run over HLS or MP4, with 360 VR-ready viewing when the file and the device both support it. Resume points and history belong to the profile, so four people on one login do not overwrite each other's progress.
Every watched minute lands in a log
This log is the fulcrum of the producer model. A payout figure taken from measured viewing can be explained to a partner, while one taken from a headcount of clicks cannot. Minutes also favor what people finish over what merely gets tapped.
The payout request closes the loop
Revenue share is computed from the accumulated minutes under the rule you configured, the producer sees the total in their dashboard, and they raise a request. The admin reviews the logs and bank details before releasing it. Both parties read the same figure.
Steps one, six and seven separate a platform that runs a content network from one that merely hosts files.
Every Feature Earns Its Place
A long feature list proves little. Each row below exists because something specific breaks on a streaming service when it is missing.
| Capability | Why it is not optional |
|---|---|
| Minutes logged per title | Payouts need a number you can defend. Clicks flatter the best thumbnail, while minutes credit whoever made something people sat through. |
| Review before publishing | If partners can go live on their own, your standards and your rights exposure are theirs to set. |
| Per-profile resume | One login serves a household. A shared resume point sends the same episode to the wrong person every night. |
| Rental windows that close | A rental is a time-limited right. Without enforcement you have sold permanent access for a rental price. |
| Three revenue paths per title | The same film can sit in a plan, be rented by non-subscribers and be sold at premiere. One model per title leaves rights you already hold unmonetized. |
| A dashboard for producers | Partners trust payouts they can check. When totals travel by email, the model stops working around the fifth producer. |
| An acquisition API | Loading partner libraries through an admin form one entry at a time puts a ceiling on catalog growth. |
| Parental lock and kids profiles | A mixed catalog in a family app becomes a support burden and, in some markets, a compliance question. |
| Live channels in the same app | Sport and events pull casual viewers in, and sending them to a second app to watch loses many of them. |
| Role-scoped admin access | The person who clears payouts should not also be able to take the catalog offline. |
None of it is exotic. These are simply the ten places where hosting video stops and running a streaming business begins.
The Technology Behind the Features
The choices are common ones on purpose, so whichever team inherits the code after handover already knows the tools.
Why the minute log matters more than any other table
Plans, purchases and invoices are ordinary commerce that any store platform handles. The minute log is what makes this an OTT business. It feeds producer revenue, backs every payout and shows honestly whether a title deserves its shelf space. A system that counts views but not minutes can quote a producer a number, yet it cannot defend that number, and on a revenue-share model that is the figure that gets disputed.
The whole Laravel backend and the Flutter projects transfer to you with the database, and rebranding is applied across every viewer, producer and admin surface.
What Is Not Included in the Base Package
Everything shown above ships in the ready-made package and can be opened in the demo. The items below are Enterprise scope, add-ons or things that stay yours, and we name them here rather than let a quote imply otherwise.
Enterprise scope, add-on or yours to own
- DRMStudio-grade rights management is Enterprise scope. Content licensors often write Widevine or FairPlay into their contracts, so this requirement can decide your tier before any other feature does. Raise it in the first conversation.
- Smart TV appsAndroid, iOS and web are covered. Apps for Android TV, Apple TV, Fire TV, Roku, Samsung or LG are separate scope, each with its own store process.
- Recommendation engineDiscovery in the base package is curated by you. Machine-learned suggestions from watch history are an Enterprise add-on.
- Advanced producer termsPayout on minutes viewed under a configured rule is included. Extended contracts, automated statements, licensing terms and multi-producer analytics belong to the producer marketplace add-on.
- Provider catalog integrations and multi-region rolloutThe acquisition API is included. Connecting a specific content provider with its own API keys, or running several regions, is scoped separately.
- Advertising moduleVAST or custom ad placements and sponsor slots are an add-on. Age gating, country-specific policies and on-premise deployment are also quoted work.
- iOS store submissionAndroid publishing support is included, and the apps go live under your own developer account. iOS compilation, signing and App Store submission are a separate scope.
- The content and its rightsNothing to watch comes with the platform. Sourcing titles and holding the licenses to stream them in your territories is the business itself.
- Gateway, SMS and push accountsOpened in your name, with keys that stay with you. Approvals differ by market.
- Storage and bandwidthVideo is costly to keep and to serve. Delivery scales with hours watched, not with sign-ups, and the bill is yours on your own accounts.
- ISO 27001 and SOC 2 certificatesSecurity practices are aligned to the controls those frameworks describe, but no certificate is held or claimed.
Settle DRM first. Most other items can be added after launch without disturbing what is live, whereas a rights-management demand that appears after content deals are signed can reshape the entire deployment. Miracuves is an independent software company, and this platform contains no code, design or content taken from any streaming service.
Compare provider types before you commit
How rented platforms, script vendors, custom agencies and Miracuves differ, the questions to put to each, and four named client deployments, on the Provider page.
Frequently Asked Questions
How is this different from renting a hosted OTT service?
Can plans, rentals and pay-per-view run together?
How does producer revenue sharing work?
Why pay producers on minutes rather than views?
Is DRM part of the ready-made package?
Does it handle 360 VR and live TV?
Send a title through as a producer, then trace its minutes
That is the demo to request. Approve it as an admin, watch it as a viewer, then follow the payout it produced.
Explore the White Label Video Streaming Platform
See every role in one working demo
Open the viewer app, the web platform, the producer panel and the admin console. Plans, rentals and pay-per-view share one catalog, and the source code and database come to you.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Netflix, Amazon Prime Video, or any other streaming service.
“White label video streaming platform” describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from any third-party streaming website or application.
All third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
