Run live streaming workflows on VPU hardware
from a browser, without writing FFmpeg.
The standards-based path your engineers chose stays intact underneath. What changes is
who can drive it. Bitstreams runs on each VPU server. Bitstreams Manager brings every
server into one interface.
Control, templates, telemetry and API for each VPU server. Comes preloaded on Quadra Video Server and Quadra Mini Server. Also ships as a Docker container on your existing Linux host, alongside the VPU cards.
One control plane for every Bitstreams instance you run, on-prem or cloud. No VPU in it. No video through it.
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.
Live preview, status, duration, stream URLs (SRT and HTTP), input stream details and event history.
Reusable encoding profiles. Output formats, video and audio parameters, HLS settings. Create, edit, reuse.
Six capabilities cover most of what a broadcast operator does on a working day.
Per-card health, utilization, thermal headroom, and per-stream throughput, alongside the FFmpeg log in one view.
Role-aware access from any laptop on the network. No SSH key handoff.
Ad markers preserved end to end through the encode. SCTE-104 over SDI.
CEA-608 and 708, Teletext, DVB Subtitle and SBTVD carry through without a side process.
SDI, SMPTE ST 2110, ATSC tuner, and multicast and unicast RTP. No gateway in front.
Prebuilt and custom profiles standardise configurations across operators, shifts, and venues.
Streaming activity and hardware sit side by side, with the FFmpeg log on screen. One person sees the hardware and the encoder at once.
VPU utilisation
turns yellow
VPU utilisation
turns red
Cards throttle
above this
Manage every Bitstreams server from one browser. The Manager sends control commands only.
Video stays on your servers.
On-prem or cloud,
in one interface.
Two-way mTLS over HTTPS, outbound from each instance. No inbound firewall rules.
Once a server enrolls, its local interface goes read-only.
Ubuntu 24.04 and Docker. 4 cores, 16 GB RAM, SSD.
Eleven ways in and eleven ways out on one server, with no gateway in front. H.264, HEVC,
AV1, VP9 and JPEG, 8-bit and 10-bit, up to 8K.
Schedulers, playout systems and your own platform start, stop and monitor VPU encoding through a REST API. It is the highest-level way to integrate NETINT VPUs. Your team builds its own application or UI with no FFmpeg knowledge required, and NETINT engineering handles the integration and validation underneath.
Bitstreams is an added control layer. FFmpeg, libxcoder and the Quadra VPU underneath
stay as they are. A video operator opens a browser. An architect drops to the terminal when
they need to.
Standards-based underneath.
FFmpeg and libxcoder paths remain intact.
No proprietary SDK.
The skills your team already has still apply.
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 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
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.
No. It wraps FFmpeg. The FFmpeg and libxcoder paths remain intact, and the FFmpeg log stays on screen.
Nothing below it changes. Your FFmpeg pipeline runs exactly as it does today.
No. The skills your team already has still apply. Automation runs over a standard REST API with a published OpenAPI definition.
No. Launch, monitor, and recover streams from a browser using prebuilt or custom templates.
The dashboard tells you. VPU utilisation shows yellow at 80% and red at 90%. Cards throttle above 70°C.
Yes. SCTE-35 passes through end to end, and CEA-608/708, Teletext, and DVB Subtitle carry through without a side process.
No. It runs on Ubuntu 24.04 and Docker with 4 cores, 16 GB RAM, and an SSD. No video passes through it.
It goes read-only. Once a server enrolls, the Manager is the single source of truth.
Each server connects to it. Two-way mTLS over HTTPS, outbound from each instance, on-prem or cloud.
Yes. Activation is per server, sold through NETINT or authorised resellers. Without a licence the software runs read-only.
No. Bitstreams installs as a Docker container on your existing Linux host alongside the VPU cards. It comes preloaded on Quadra Video Server and Quadra Mini Server.
24/7. Technical support through online ticketing.
Yes. The Cloud Pilot Program lets you test VPU encoding in the cloud at no cost, funded by VPU Ecosystem cloud partners. Terms vary by partner.
