KinoPipe vs self-hosted FFmpeg
FFmpeg is free and can do almost anything — but self-hosting it means owning the servers, scaling, security and the command generation. KinoPipe is FFmpeg 9 hosted behind typed operations, so an agent (or you) ships an edit without ever running a shell.
Checked against public product pages on August 25, 2026.
| Area | KinoPipe | self-hosted FFmpeg |
|---|---|---|
| Setup | One API key or an MCP connect — nothing to deploy | Provision servers or containers, install FFmpeg and codecs |
| Who writes the edit | Agent picks a typed operation, validated before it runs | You or the agent write raw FFmpeg command strings |
| Safety | No shell access; every input and option validated | Shell execution — command injection and resource exhaustion are yours to contain |
| Compute | Hosted GPU (NVENC) workers, autoscaled, p50 ~8s for 1080p | Your CPUs or GPUs to size, patch and scale |
| Storage and delivery | Signed uploads and CDN-served outputs handled | You run storage, signed URLs and file cleanup |
| Reliability | Async jobs, retries and automatic failed-job refunds | You build the queue, retries and observability |
| Cost model | Worker seconds or 6 MiB output units via credits | Free binary; you pay for servers, ops time and egress |
Before you choose
Is KinoPipe just hosted FFmpeg?
It runs FFmpeg 9 under the hood, but exposes bounded, validated operations instead of a shell — so an agent cannot submit an unsafe or malformed command, and every edit is checked before it queues.
Can I still do advanced FFmpeg edits?
Common edits are a single call, and complex compound edits run as one single-pass custom recipe. If you truly need the entire raw filtergraph surface, self-hosting keeps that freedom.
Do I save money by self-hosting?
The FFmpeg binary is free, but a production setup means servers, GPU, storage, security and on-call time. KinoPipe trades that for credits based on worker seconds or 6 MiB output units, plus a free tier of 100 credits.