Live streaming and video platform development
RTMP and SRT ingest, real-time transcoding, HLS delivery and the billing around them. We built zap.stream, a live streaming platform with Lightning payments.
Ingest
RTMP and SRT ingest with per-user stream keys.
Transcoding
Real-time FFmpeg transcoding into several renditions, through direct bindings.
Delivery
HLS segmenting and serving, ready to put behind a CDN.
Monetisation
Per-minute billing from prepaid balances, Lightning tips and zaps.
Uploaded media
Video and image compression, thumbnails, metadata extraction and range requests.
Self-hosting
Docker Compose deploys with an admin UI.
zap.stream runs on a Rust streaming server that takes RTMP or SRT, transcodes with FFmpeg into several renditions, segments to HLS and serves the result. It is packaged with Docker Compose so other operators can run their own copies.
We call FFmpeg through Rust bindings rather than shelling out to the command line, which keeps memory, latency and error handling under control. The same approach powers a media server that stores uploads by hash, compresses images and video, makes thumbnails and answers range requests for playback.
Video turns up elsewhere in our work too, from camera walls on a Raspberry Pi to decoding broadcast television.
- Can you build a streaming backend into our product?
- Yes. We can build ingest, transcoding and HLS delivery around your own accounts and billing, reusing what we built for zap.stream where it fits.
- Do you work with recorded video as well as live?
- Yes. Route96 processes uploaded video: compression, thumbnails, metadata extraction and range requests for playback.
- Can we run it on our own servers?
- Yes. zap-stream-core is designed to be self-hosted with Docker Compose, with or without a public IP.