FFmpeg VPU Transcode Node
FFmpeg VPU Transcode Node is available in the NetActuate Marketplace as a one-click, open-source appliance you can deploy into any NetActuate PoP. FFmpeg transcode appliance with ABR output, tuned for NETINT VPU nodes. It is grouped under the Media & Streaming category.
What It Does
FFmpeg is the open source, cross-platform framework that records, converts, and streams audio and video, and it is the transcoding engine behind a large share of the internet video pipeline. This appliance packages FFmpeg as a turnkey, self-serve transcode node: point a stream or a file at it and get adaptive-bitrate outputs back, driven by a small token-guarded control API.
This listing is NetActuate marketplace item #4, the open source proof of the VPU economics and the on-ramp to Bitstreams. It is built to run FFmpeg accelerated by NETINT Video Processing Units (Quadra / T408) in VPU-equipped PoPs: the listing declares a VPU requirement so the deploy wizard steers you to a VPU-capable location and attaches an accelerator, and the node selects the NETINT encode path when a VPU and an SDK-enabled build are present.
What the appliance boots
- FFmpeg on Ubuntu 24.04 LTS, ready to transcode on first boot
- A token-guarded transcode control API and status page (default port 8080): list profiles, submit jobs, and run a self-test transcode
- Outputs written to a configurable directory, ready to push to an origin or object store
Key features
- H.264 and HEVC output profiles (1080p / 720p / 480p) plus an ABR-ladder starting point
- Submit-a-job REST API guarded by a generated API token, and a read-only status page
- Selects the NETINT VPU encode path automatically when a VPU and an SDK-enabled FFmpeg are present, and transcodes on the CPU otherwise
- Deployable to the PoP nearest your source or your audience for regional transcode
Use cases
- File and live ABR transcoding for OTT and streaming workflows
- Regional, per-PoP transcode placed near contribution or delivery
- A low-cost open source path to hardware transcode economics, ahead of the Bitstreams self-licensing appliance
Open source and VPU note FFmpeg is community open source software (LGPL / GPL depending on build options, https://ffmpeg.org/). NetActuate packages this ready-to-run appliance; the software belongs to its community. This build ships software (CPU) FFmpeg. NETINT VPU acceleration requires an FFmpeg built with the NETINT libxcoder SDK plus an attached VPU; bundling that SDK inside a customer-consumable image is an open licensing item with the NETINT partnership, so the SDK-enabled image and the flagship VPU story follow once that clears. Until then this node transcodes on the CPU and never claims a VPU it does not have.
Vendor and Project
FFmpeg VPU Transcode Node is an open-source project, offered here under the Open Source listing with best-effort community support.
- Project home: ffmpeg.org
NetActuate supports the underlying infrastructure. Application-level support follows the listing SLA class (open-source, best effort).
Sizing
| vCPU | RAM | Disk | |
|---|---|---|---|
| Minimum | 4 | 8 GB | 100 GB |
| Recommended | 8 | 16 GB | 500 GB |
This appliance requires a NETINT VPU for hardware acceleration. Choose a VPU-capable size and location at deploy.
Configuration Fields
When you deploy, you provide these fields. They are written into the appliance at first boot.
| Field | Required | Default | Notes |
|---|---|---|---|
| API token | No | generated | Bearer/Basic token guarding the transcode API (submit + selftest). Generated automatically and stored in your secret list; never echoed back. Stored write-only in your account secret list |
| API port | No | 8080 | TCP port for the transcode control API and status page (default 8080). |
| Default transcode profile | No | h264-720p | Output profile applied to jobs and the self-test. |
| Default input source | No | none | Optional default input (file path, http(s) URL, or RTMP/SRT ingest). Blank leaves the node idle until a job is submitted. |
| Output directory | No | /var/lib/ffmpeg-transcode/out | Directory transcoded outputs are written to. |
| Accelerator | No | cpu | cpu (software x264/x265) or netint (NETINT Quadra/T408 VPU). netint requires an attached VPU and an SDK-enabled FFmpeg; the current OSS image ships the CPU build and falls back to cpu. |
Using the Appliance
The FFmpeg transcode node is up. Log in over SSH with the key you supplied (user root or ubuntu). The transcode control API and status page listen on port 8080 (default 8080); the status page is http://YOUR_VM_IP:8080/ and health is /healthz. Your generated API token is in your secret list (never echoed). Submit a transcode: curl -X POST -H 'Authorization: Bearer <token>' -H 'Content-Type: application/json' -d '{"input":"https://example.com/in.mp4","output":"out.mp4","profile":"h264-720p"}' http://YOUR_VM_IP:8080/api/jobs . Run a built-in self-test transcode: curl -H 'Authorization: Bearer <token>' http://YOUR_VM_IP:8080/api/selftest . Outputs are written under /var/lib/ffmpeg-transcode/out. This build transcodes on the CPU; NETINT VPU acceleration activates automatically on a VPU-capable PoP once the SDK-enabled image ships.
FAQ
Is there a software license fee? No. FFmpeg VPU Transcode Node is open source and free to run. You pay only for the NetActuate infrastructure and bandwidth.
Where is the web interface?
On port 8080 at path /healthz by default.
Do I need special hardware? Yes. This appliance requires a NETINT VPU. Select a VPU-capable size and location at deploy.
Who supports it? NetActuate operates the underlying infrastructure. The application itself is community-supported open source (best-effort SLA class).
Version and Changelog
| Version | Status | Released |
|---|---|---|
| 6.1.1 | Current (default) | 2026-07-10 |
Deploy
- Deploy in the portal: Deploy FFmpeg VPU Transcode Node
- View the listing: portal.netactuate.com/platform/marketplace/l/ffmpeg-vpu-node
- Public listing: netactuate.com/marketplace/ffmpeg-vpu-node
Need Help?
Contact support@netactuate.com or open a support ticket from the portal.