Engagement scope - proposed scope
Choosing a White Label Video Streaming Platform Provider
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
Typical scoping questions
Who holds the source and the database?
- Ask for the repository and the subscriber records by name. Access to run software is not ownership, and a provider that keeps the code, controls the deployment or takes a cut of your subscriptions is selling a license with your logo on it.
What is left the day you stop paying?
- With a rental the site, and often the audience, goes when the invoice does. With a platform you own you keep running on hosting and bandwidth bills alone. Get the answer in writing.
Where are watch minutes recorded?
- Minutes per title, not view counts. Without that log a producer payout has nothing to be computed from, and every settlement turns into a negotiation.
Rent a title, then let the window close
- Try to play it afterward. If expiry is stored but never checked at playback, you have been selling permanent access at a rental price without noticing.
Could this design accept DRM?
- The question is whether the architecture can take it, not whether a brochure lists it. If you will ever license studio content, the answer sets a ceiling on how far the platform can go with you.
What do the delivery days cover, and what do they not?
- Ours cover setup, branding, payment rules and handover. Gateway and store approvals, the content and its rights, and your bandwidth bill stay with you. A quote without exclusions was never costed.
Is any of the source encrypted or license-checked?
- Both practices appear in this market and both give the vendor leverage over you. Ours is no to each, which you can verify in the repository when it is transferred.
The Six-Step Delivery Process
What happens from your yes to your first stream, and who is responsible for each stage.
Configure the catalog and prove playback
- Genres, categories and content types are created, then real devices play HLS or MP4 streams. Live channels and 360 VR-ready titles are checked too when they are in your plan.
Apply your brand everywhere
- App name, icon, splash screens and colors reach both mobile apps, the web platform, and the producer and admin panels. Emails and invoices are branded and your domain is connected.
Write the commercial rules
- Gateway keys are installed and tested, plans are priced, rental windows and pay-per-view unlocks are defined, and coupons prepared. Producer accounts follow, with the payout rule and approval flow demonstrated to you.
Red Flags That Mean Walk Away
Six statements that should end a sales call, whoever makes them, including us.
If you hear these, stop
- "You get a license, the code stays with us" Then each change you want is a favor you have to request. Software you cannot alter is a storefront with your logo painted on.
- "We host the video for you" They then earn a margin on every gigabyte you serve, permanently, and your exit means migrating a catalog and an audience together. In streaming, the owner of the cloud account owns the economics.
- "Views and minutes amount to the same thing" They do not. Views reward the thumbnail, minutes reward the content, and the choice shapes which producers you attract. Views are also the figure partners dispute.
- "DRM can always be added later" Sometimes it can, often it cannot, and if a licensor names Widevine or FairPlay in the contract, "later" means reopening the deal. Confirm the design can take it before signing.
What a Streaming Platform Has to Get Right
Set out before the purchase, because a limit discovered after signing costs far more than one printed in advance.
Smart TV apps are quoted separately
- Android, iOS and the web platform are covered. Apps for Android TV, Apple TV, Fire TV, Roku, Samsung or LG are separate scope, each with its own store process.
Discovery is curated, not algorithmic
- Banners, genres and shelves are arranged by you. Machine-learned recommendations are an Enterprise add-on, and they pay off only once the catalog outgrows what manual curation can cover.
Content, rights and iOS submission are yours
- The platform arrives with nothing to watch, and no software supplies the licenses. Storage and bandwidth are billed to you on your own cloud. Android publishing support is included, while iOS compilation, signing and App Store submission are a separate scope.
- Security practices are aligned to what those frameworks look for, including TLS, token-based access, rate limiting and role-based access, but no certificate is held or claimed. Certification is a separate program with its own auditor.
- A provider who publishes these limits is easier to hold to account than one who does not. Hold us to them.
Choose on the answers, not the pitch
Named clients in production, a scope boundary published in advance, complete source at handover, and a bandwidth bill that lands on your own account at cost.
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