Bitstreams lets video operators run live streaming workflows on VPU hardware from a browser, without writing FFmpeg.
Bitstreams wraps FFmpeg in a web interface. These six capabilities cover most of what a broadcast operator does on a working day.
Prebuilt and custom stream profiles standardise configurations across operators, shifts, and venues.
Per-card health, utilization, thermal headroom, and per-stream throughput surface alongside the FFmpeg log in one view.
HLS ad markers are preserved end-to-end through the encode.
Accessibility carries through the pipeline without a separate side process.
Both transport models live broadcast actually uses, both natively supported.
Role-aware access from any laptop on the network. No SSH key handoff.
Quick tour of the major sections. This is what an operator sees from launching a stream to monitoring it live.
Total live streams, VPU usage, host CPU and RAM, encoding issues, and VPU hardware status, all in one view.
Every running, idle, and stopped stream with input URLs, templates, output URLs, and stream-level status.
Per-stream view: live preview, status, duration, stream URLs (SRT and HTTP), and event history.
Reusable encoding profiles. Output formats, video and audio parameters, HLS settings. Create, edit, version.
The Bitstreams REST API allows schedulers, playout systems and your own platform to start, stop and monitor VPU encoding through automation.
The API is the highest-level way to integrate NETINT VPUs. You can also integrate through FFmpeg, GStreamer, or libxcoder, but those paths demand expertise. The API removes that work. Your team builds its own application or UI with no FFmpeg knowledge required. NETINT engineering handles the complex integration and validation underneath.
Bitstreams wraps FFmpeg. It does not replace it. The standards-based path your engineers chose, FFmpeg, GStreamer, or libxcoder, remains intact underneath. What changes is who can drive it. A video operator opens a browser. An architect drops to the terminal when they need to. The silicon is the same Codensity G5 ASIC running in every Quadra product.
FFmpeg, GStreamer, and libxcoder paths remain intact.
Every stream config is versioned.
Every change is reversible.
The skills your team already has still apply.
Bitstreams ships as a Docker container that installs on your existing Linux host alongside the VPU cards. No new operating system. No new chassis. No new networking decision.
Runs the day-to-day and the 24/7 streams that cannot go dark. Needs to launch a new feed without filing a ticket. Bitstreams puts the stream lifecycle in their hands (template, launch, monitor, recover) without altering the underlying pipeline.
Chose FFmpeg, GStreamer, and libxcoder for a reason. Will not adopt anything that hides the path or locks the toolchain. Bitstreams sits on top of the path they already own. It does not replace it. Rollback is a single action.
Lives between the cards and the camera. Cares about SCTE-35 surviving the encode, captions arriving intact, and RTP inputs working without a side script. Bitstreams treats those as first-class capabilities, not edge cases.
Here’s a quick, high level overview of what’s inside Bitstreams.
Start with a 30-day free trial on Akamai Cloud.
No infrastructure or hardware purchase required.
