KinoPipe vs Transloadit
Transloadit chains file-processing Robots into Assemblies and bills by gigabytes processed. Its /video/encode Robot even accepts custom FFmpeg parameters. KinoPipe keeps the FFmpeg surface closed behind typed operations and prices by worker time or output size. Both are hosted; the difference is how much control you want and who is writing the request.
Checked against public product pages on August 26, 2026.
| Area | KinoPipe | Transloadit |
|---|---|---|
| Editing model | Typed operations and single-pass compound recipes; no shell, no raw flags | Assemblies and Templates chaining Robots such as /video/encode, /video/concat, /video/subtitle, /video/thumbs and /video/merge |
| FFmpeg control | Closed: every option is schema-validated | Open: /video/encode accepts a custom ffmpeg parameter object and an ffmpeg_stack version (v7 recommended) |
| Agent access | Remote MCP server with OAuth 2.1 plus REST | REST API and SDKs; no MCP server mentioned in the docs we read |
| Free tier | 100 credits once, full output | Community: 5 GB per month, watermarked images and trimmed audio and video, service stops at the limit (as of 26 August 2026) |
| Pricing unit | Credits: the greater of worker seconds or 6 MiB output units | GB processed: input plus output bytes across all steps |
| Entry paid plan | $12 per month for 1,500 credits | Startup at $69 per month for 40 GB, $1.80 per additional GB (as of 26 August 2026) |
| Failed jobs | Credits refunded automatically | Not stated on the pricing page we read |
Before you choose
Transloadit can run custom FFmpeg parameters. Is that better?
It is more powerful, and the right choice when an engineer knows exactly which flags they need. KinoPipe deliberately refuses raw parameters so an agent cannot emit a broken or unsafe command; the trade is less freedom for validation before compute.
How do the billing units compare?
Transloadit bills gigabytes processed (input plus output). KinoPipe bills credits from the greater of worker seconds or output size units, and refunds jobs that fail. Which is cheaper depends on file sizes and render time; compare with a sample of your real files.
Does KinoPipe handle non-video files?
Audio yes (extract, merge, normalize, silence removal, waveforms), images as inputs and outputs (thumbnails, filmstrips, image to video). Documents and generic file conversion are out of scope.