MpegFlow is the category's trust benchmark — “FFmpeg, orchestrated” as a managed SaaS, with the compliance paperwork to match. The fork in the road is simpler than any feature table: their model uploads your footage; ours never does.
Both columns describe what actually ships — theirs from what they publish, ours from the product. Nothing guessed, nothing padded.
| TRNSCODE | MpegFlow | |
|---|---|---|
| Where encoding runs | Inside your network, on hardware you own | On their managed fleet — a cloud SaaS |
| Your media | Never leaves the building; no upload step exists | Uploads to their infrastructure for processing |
| Pricing | Published: Solo free forever; $29–$999/mo flat by worker ceiling | Not published on their site |
| Compliance posture | Runs behind your firewall — your existing controls and NDAs govern it; no third party touches the footage | SOC 2 Type II and ISO 27001 published audits, GDPR DPA — their genuine strength |
| Operational transparency | Verification evidence attached to every job you run | Public status page, uptime ledger (99.987% published) and dated postmortems |
| Engine | FFmpeg — plain invocations you can read, copy and debug | FFmpeg — node-graph/DAG orchestration |
| Post-production ingest | EXR · OCIO · ACES, per-project profiles, dailies and references | Not published |
| NLE round-trip | Avid, Premiere, FCP, Resolve — OTIO, EDL, AAF | Not published |
| Named customers | Not yet — the product launched in 2026 | A named broadcast customer with a public story |
Their trust file is real: audited SOC 2 Type II and ISO 27001, public postmortems, a published uptime ledger, a named broadcast customer. If your security team's checklist starts with a vendor audit report, they have one and we do not. Our counter is structural, not paper: TRNSCODE cannot leak, hold, or train on footage it never receives — the NDA-relevant surface area is your own network, which your controls already govern.
You want a managed service with no fleet to run, your footage is cleared to leave the building, and audited vendor compliance is the deciding checkbox.
Your footage contractually cannot leave the building, you already own the machines a fleet needs, you want published flat pricing instead of a quote call — and the deliverable should carry its own QC evidence when it lands.
If MpegFlow ships something that makes a row here outdated, tell us — info@trnscode.com — and the row gets fixed. These pages are only worth keeping if both columns stay true.
For a SaaS it should be: their servers hold your footage, so you need their audit. TRNSCODE is self-hosted — your media never reaches us, and the license check is the only thing that phones home. The infrastructure to audit is yours, under controls your facility already passed. Ask us anything about the license service's posture: info@trnscode.com.
Whichever has more hardware behind it that day. Their fleet is theirs and shared; yours is yours — every idle edit bay, render blade and spare desktop you add is throughput, at no marginal cost, with nothing queuing behind another customer.
Sure — some rooms keep a SaaS lane for cleared, public-facing content and run TRNSCODE for everything under NDA. Solo is free forever on one machine, so the comparison costs nothing to run on your own footage.
Install the master, join a worker, submit a job. Self-hosted and free to run on hardware you already own.