White-label video platform
A white-label video platform is video infrastructure that runs behind your own brand, so viewers see your logo, colors, domain and player design and never the vendor's. The provider operates encoding, storage, delivery and playback, and you present it as part of your product. White-label can mean a finished portal or app that the vendor runs with your branding applied, or a set of APIs and an unbranded player that you build into your own site and apps.
How does a white-label video platform work?
The infrastructure is the same as any streaming service: transcoding into a bitrate ladder, packaging as HLS or DASH, storage, CDN delivery and a player. White-labeling is about removing every place the vendor shows through.
Viewers notice a vendor in three places. The first is the player: a logo bug in the corner, default control styling, a "watch on" link, or an end screen that promotes other content. The second is URLs: an embed page or share link on the vendor's domain. The third is the surrounding experience: a hosted portal, sign-up flow or app listing under someone else's name. A white-label setup removes or replaces each one. The player is themed or swapped for your own, embeds sit on your pages, and the portal is rebranded or replaced by your own front end.
White-label video platform vs. video API
A white-label platform in the portal sense gives you a finished product with your branding applied: a catalog site, often apps, sign-up and payments. It is quick to launch, and it is limited to the screens and features the vendor built.
A video API with an open player is white-label by construction, because there is no vendor front end to rebrand. Your team builds the pages and apps, calls the API for uploads and playback, and themes the player. That takes engineering time, and in exchange the video behaves like the rest of the product. The player can match the design system, use the app's login for access, sit inside a vertical feed, and send playback events tagged with your own user IDs.
The choice usually follows where video sits. If the product is the video service, either can work. If video is one feature inside a larger app, an API avoids running a second branded portal beside the main product.
What should a white-label video platform include?
Start with the player, because it is what viewers see. It should be themable down to controls, captions and colors without forking the code, and it should run on every surface you ship: web, iOS, Android, cross-platform frameworks and TV. Watermarks should be yours and configurable. Accessibility matters here too, since a branded player still has to work with keyboards and screen readers.
Then the parts viewers do not see but your brand depends on. Access control decides whether paid or private videos stay private: signed, expiring URLs at minimum, and DRM for high-value catalogs. Viewer data should flow to you, with per-view quality and engagement you can join to your own users. Upload paths should work from your own apps if users contribute video. Finally, check portability: whether you can export media and metadata, and whether playback URLs in your apps can move if you change providers.
How does a white-label video platform handle domains?
Branding stops at the address bar if the video lives on someone else's domain, so check three levels. The page level is easy: the player is embedded in your own pages and apps, so viewers see your domain in the browser. The share level covers links people copy. A share link should open your page, not a vendor watch page.
The media level is the manifest and segment hostnames the player requests. Viewers rarely see them, but they show up in browser developer tools, in allowlists on school and corporate networks, and in content security policies. Serving them from your own subdomain usually means a DNS CNAME record pointing at the provider's CDN, plus a TLS certificate the CDN can present for that name. With multi-CDN delivery, every CDN in the mix needs that certificate, which is why custom media domains are often a separate feature. Native apps add one more place: the app store listing, which has to be published under your own developer account.
How does FastPix handle white-label video?
FastPix is white-label by design because it has no viewer-facing portal. The front end is your site or app, and FastPix supplies the infrastructure and an unbranded player underneath.
FastPix Player is free and open source, with SDKs for web (including smart TVs and consoles), Android (built on Media3), iOS, tvOS and visionOS (built on AVPlayer), Flutter and React Native. Branding colours, layout and every control and caption are themed with CSS variables without forking, a custom controls slot takes your own buttons, and the watermark is configurable. It meets WCAG 2.1 AA with keyboard navigation and screen-reader labels, ships its UI in 10+ languages, and plays vertical 9:16 feeds as well as 16:9. Delivery runs on a multi-CDN network of 300+ points of presence, and with a custom domain video, posters and storyboards stream from your own domain. Posters are rendered from any frame and size, under the same access policy as the video.
Your backend decides access: signed playback IDs with expiring JWTs, or Widevine, FairPlay and PlayReady DRM. Video Data records each view with your own viewer ID and up to 10 custom dimensions. Inside existing sites, ready-made FastPix plugins for WordPress, Moodle, Strapi and Sanity carry the same player. The WordPress plugin embeds it by block or shortcode with signed playback and AI captions, including on LearnDash, TutorLMS and LifterLMS sites, and the Moodle plugins bring it into Moodle courses with completion tracking.
The themed player is free and open source. What bills is usage: Standard encoding free up to 4K, storage per rendition-minute and streaming per minute watched. New accounts get $25 of credit, and the free plan needs no card.
