PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Feature scope - proposed scope

White Label Video Streaming Platform Features: By Role

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Scope areas for this kind of build

Feature 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

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

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

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.

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.

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.

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.

Boundaries we state in writing for your build

Enterprise scope, add-on or yours to own

  • DRM Studio-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 apps Android, 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 engine Discovery in an initial scope is curated by you. Machine-learned suggestions from watch history are an Enterprise add-on.
  • Advanced producer terms Payout 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.

More pages on this build

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.

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Netflix , Amazon Prime Video , or any other streaming service.

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com