VOD streaming platform with adaptive HLS and paywall
Employer
Andriy
Project parameters
Type of cooperationOne-time project
SectionWeb development
Prepaymentwithout prepayment
Payment methodsCash, Bank transfer
Acceptance of requestsfrom today, 06:29 until Sep 24, 2026
Project description
We run a growing library of video content — a mix of recorded courses and original media — and we want to move it off third-party hosting onto our own branded streaming site. The goal is a Netflix-style experience: a viewer opens a title, presses play, and the video starts almost instantly and stays smooth whether they are on fibre or on a phone in a weak cell zone. This is video-on-demand from a catalogue, not live webinars, so there is no real-time broadcasting to worry about — everything is pre-recorded, ingested once, and served many times.
The core of the job is the media pipeline. When we upload a source file it should be validated, stored, and transcoded into several renditions (roughly 1080p, 720p, 480p and a low mobile profile), then packaged for adaptive HLS so the player switches quality automatically according to the viewer's bandwidth. Segments and playlists must be delivered through a CDN with signed, expiring URLs so a link cannot simply be copied and shared. On top of that we need a clean web player with the usual controls — resume from where you stopped, playback speed, subtitle tracks and a quality selector — plus a paywall and access control: only a logged-in subscriber or someone who bought a specific title may get a playable stream.
Finally we want basic analytics that actually tell us something: views started, average watch time, completion rate, drop-off points inside a video, and which qualities are being served. Please describe your proposed architecture, the transcoding stack you would use, how you would handle storage and CDN costs, and your estimate of timeline and ongoing running cost. Experience with real streaming projects is strongly preferred.
— Ingest, transcode and HLS packaging pipeline
— Adaptive player with resume, subtitles and speed control
— Signed URLs, subscription and per-title access control
— Viewership analytics dashboard
The core of the job is the media pipeline. When we upload a source file it should be validated, stored, and transcoded into several renditions (roughly 1080p, 720p, 480p and a low mobile profile), then packaged for adaptive HLS so the player switches quality automatically according to the viewer's bandwidth. Segments and playlists must be delivered through a CDN with signed, expiring URLs so a link cannot simply be copied and shared. On top of that we need a clean web player with the usual controls — resume from where you stopped, playback speed, subtitle tracks and a quality selector — plus a paywall and access control: only a logged-in subscriber or someone who bought a specific title may get a playable stream.
Finally we want basic analytics that actually tell us something: views started, average watch time, completion rate, drop-off points inside a video, and which qualities are being served. Please describe your proposed architecture, the transcoding stack you would use, how you would handle storage and CDN costs, and your estimate of timeline and ongoing running cost. Experience with real streaming projects is strongly preferred.
— Ingest, transcode and HLS packaging pipeline
— Adaptive player with resume, subtitles and speed control
— Signed URLs, subscription and per-title access control
— Viewership analytics dashboard
