Skip to main content
A
// CASE FILE 15 / 19
← All case files

API Transcoder

Studio Build4 RENDITIONS · RTMP IN, HLS OUTFastAPIffmpegMinIOWebSocket
01> HOW IT SHIPPED
// THE CHALLENGE01

Uploading a video is the easy half. Returning four renditions, a live stream and honest progress — while the file is still moving — is the half that fails in front of the customer.

// THE APPROACH02

FastAPI over ffmpeg for a 360p to 1080p ladder, RTMP in and HLS out for live, MinIO tuned for large multipart uploads, Supabase JWTs at the edge, and per-quality progress pushed over WebSocket and SSE rather than polled.

// THE OUTCOME03

A client uploads once and watches each rendition finish on its own clock, with a failure reported against the quality that failed instead of collapsing the whole job into one opaque error.

case --info api-transcoder
> client · Altacee
> sector · Video Infrastructure
> stack · FastAPI · ffmpeg · MinIO · WebSocket
> result · 4 RENDITIONS · RTMP IN, HLS OUT
> case/api-transcoderSHIPPED ▮

Want a system like this?

Tell us what you're building. We'll respond with a scoped plan, not a sales pitch.