A Transloadit alternative. For video jobs.
Transloadit runs uploads and many kinds of files through Robots. If your files are video and audio, Videxo runs them through ffmpeg directly, as JSON or as your own command.
curl "$VIDEXO_API_URL/v1/transcode" \
-H "Authorization: Bearer $VIDEXO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"input": "https://videxo.io/samples/talk.mp4",
"preset": "web-720p",
"filename": "talk-720p.mp4",
"metadata": {
"order": "1234"
}
}'const response = await fetch(`${process.env.VIDEXO_API_URL}/v1/transcode`, {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.VIDEXO_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
"input": "https://videxo.io/samples/talk.mp4",
"preset": "web-720p",
"filename": "talk-720p.mp4",
"metadata": {
"order": "1234"
}
}),
});
const job = await response.json();Side by side
Videxo and Transloadit. Checked on Nov 5, 2026.
| Topic | Videxo | Transloadit |
|---|---|---|
| Before the first job | An API key as a Bearer token. No bucket, role or queue to create. | A workspace Auth Key; requests signed with the Auth Secret when the workspace requires it. |
| How a job is described | JSON operations, or the ffmpeg command you already run, checked before the job is created. | An Assembly of Steps, each run by a Robot such as /video/encode, often saved as a Template. |
| Where outputs go | Stored for your plan’s retention, 7 days to 30 days, with signed download links that last up to an hour. | Exported by a Robot to your S3, Google Cloud, Azure and others; temporary result URLs last 24 hours. |
| When a job ends | A webhook URL per job or endpoints on your account, signed in the Standard Webhooks format and retried for about a day. | notify_url, a POST when the Assembly ends. |
| Streaming formats, live, DRM | Files in, files out. Adaptive streaming (HLS) and a player Soon | HLS, DASH and CMAF from the /video/adaptive Robot. |
| AI assistants (MCP) | An MCP server that checks, runs and waits for jobs with your API key. | An MCP server for Assemblies, Robots and Templates. |
| Company | BEO TECHNOLOGY sp. z o.o., Poland, in the European Union. | Transloadit-II GmbH, Berlin, Germany. |
Videxo
- Before the first job
- An API key as a Bearer token. No bucket, role or queue to create.
- How a job is described
- JSON operations, or the ffmpeg command you already run, checked before the job is created.
- Where outputs go
- Stored for your plan’s retention, 7 days to 30 days, with signed download links that last up to an hour.
- When a job ends
- A webhook URL per job or endpoints on your account, signed in the Standard Webhooks format and retried for about a day.
- Streaming formats, live, DRM
- Files in, files out. Adaptive streaming (HLS) and a player Soon
- AI assistants (MCP)
- An MCP server that checks, runs and waits for jobs with your API key.
- Company
- BEO TECHNOLOGY sp. z o.o., Poland, in the European Union.
Transloadit
- Before the first job
- A workspace Auth Key; requests signed with the Auth Secret when the workspace requires it.
- How a job is described
- An Assembly of Steps, each run by a Robot such as /video/encode, often saved as a Template.
- Where outputs go
- Exported by a Robot to your S3, Google Cloud, Azure and others; temporary result URLs last 24 hours.
- When a job ends
- notify_url, a POST when the Assembly ends.
- Streaming formats, live, DRM
- HLS, DASH and CMAF from the /video/adaptive Robot.
- AI assistants (MCP)
- An MCP server for Assemblies, Robots and Templates.
- Company
- Transloadit-II GmbH, Berlin, Germany.
Transloadit, as its own pages said on Nov 5, 2026: Authentication Transloadit dictionary Downloading results Services and Robots MCP server Imprint
Moving over
What each part is called here. One request per job.
Every job returns the ffmpeg command it ran, so you can compare the output with what you have today, one job at a time.
Every output type and option| Transloadit | Videxo |
|---|---|
| Assembly | Job |
| Assembly Instructions and Template | The job’s JSON body, or a preset per output |
| Step with /video/encode | A video output with its options |
| /video/thumbs, /audio/encode | image and audio outputs, or POST /v1/thumbnails and /v1/audio |
| /s3/store and other export Robots | A stored output with a signed download_url; copy it to your bucket |
| notify_url | webhook_url, signed in the Standard Webhooks format |
| Uppy and tus uploads | POST /v1/uploads: a one-time upload URL up to 100 MB |
Honestly
When Transloadit fits better. Pick it then.
- Your users upload from browsers and phones and you want resumable uploads with Uppy and tus.
- You process images and documents as well as video.
- Results must be exported straight to your bucket, or files are larger than your plan here takes.
Questions, answered.
What are the limits?
On Pay as you go a job runs up to 10 min of ffmpeg with inputs up to 1 GB; on Scale up to 60 min with inputs up to 10 GB. Uploads from apps and browsers go up to 100 MB.
Which ffmpeg and which codecs?
ffmpeg 6.1.1, with H.264, H.265, VP8, VP9 and AV1 video, and AAC, MP3, Opus, FLAC and WAV audio, among others. The command rules list every option, filter and format a command can use.
Can I send my own ffmpeg command?
Yes. POST /v1/jobs takes input URLs, output names and an ffmpeg command that names files by alias. It is checked before the job exists; a refused command answers with a code for each problem and costs nothing.
How long are the files kept?
Outputs stay for your plan’s retention. Each download link is signed and lasts up to one hour; read the job again for a fresh one, or delete the files sooner with DELETE /v1/jobs/{id}/files.
How do I know a webhook came from you?
Each delivery is signed with your account’s secret in the Standard Webhooks format. Verify it with the standardwebhooks library or a few lines of code; the docs show both.
Who runs Videxo?
BEO TECHNOLOGY sp. z o.o., a limited company in Poland, in the European Union. Write to hello@videxo.io.