Xora
Rendi alternative

Xora vs. Rendi

Both run your own FFmpeg commands in the cloud, with webhooks and stored outputs. The differences are what you pay for, how a command is sent, and whether an AI agent can run jobs or only read the docs.

FeatureRendi (rendi.dev)Xora (xora.sh)
Billing ModelProcessed GB (input size + output size) Credits — processing time + output produced
Paid Entry Plan$25 / mo for 250 GB processed$15 / mo for 400 credits
Free Tier50 GB / mo; card required ($5 refunded check); 1-minute command cap 25 credits / month, no card required
Command FormatSingle command string (quoting and escaping are on you) JSON args array — nothing to quote or inject
Pre-built RecipesNo (custom commands only) Yes (9 recipes like webReady, plus a probe mode)
AI Agent AccessMCP server that searches the docs; llms.txt MCP server that runs jobs (OAuth or API key); llms.txt; agent skill
Job NotificationsPoll, or webhooksPoll, or webhooks
Storage ArchitectureRendi-hosted storage with stable URLs Managed storage, or your own Cloudflare R2 bucket (BYOB, paid plans)
Egress Bandwidth FeesNoneNone — and no download step with BYOB

Rendi prices and limits from rendi.dev, checked on 13 October 2026.

Billing Mechanics: Processed GB vs. Credits

Rendi charges for the size of the files a command touches. Xora charges credits for the work a job actually performs — processing time plus output produced. See how this affects your bill.

Scenario A

Thumbnail seek from 2 GB video

Extracting a single JPEG preview frame at the 10-second mark of a raw upload.

Rendi Pricing

~$0.20

Bills input + output size: about 2.0 GB, at the $0.10/GB of Rendi's Pro plan ($25 / 250 GB).

Xora Pricing

~0.1 credits

With stageInput: false, a ranged read grabs the frame — the 2 GB never moves. About $0.004 at Build's ~4¢/credit.

Xora is ~98% cheaper for seeking & trimming

Scenario B

High-compression of 50 MB video

Running a heavy CPU transcode that takes 3 minutes of processing.

Rendi Pricing

<$0.01

Bills 75 MB of input + output — under 1¢ at the Pro plan's $0.10/GB.

Xora Pricing

~3.3 credits

3 minutes of processing + 0.25 credits for the 25 MB output — about $0.12 at Build's ~4¢/credit.

Size-based billing wins on small, CPU-heavy files — credits win wherever files outweigh the work

Shell Command vs. Arguments Array

Rendi takes the whole job as a single command string. When your application assembles that string from dynamic values — file names, user-supplied text for a drawtext overlay — quoting and escaping those values correctly is your job, and a missed quote means a broken or misbehaving command.

Xora takes an arguments array. Each element reaches the FFmpeg process exactly as written — no shell string to assemble, nothing to quote, nothing to inject — so an apostrophe in a user’s caption can’t rewrite your command.

Rendi payload (string command)
{
  "ffmpeg_command": "-i {{in_1}} -vf \"drawtext=text='CONFIDENTIAL':x=10:y=10:fontsize=24\" -c:v libx264 -crf 23 {{out_1}}",
  "input_files": { "in_1": "https://example.com/source.mov" },
  "output_files": { "out_1": "output.mp4" }
}
Xora payload (safe args array)
{
  "mode": "ffmpeg",
  "input_files": { "in_1": "https://example.com/source.mov" },
  "output_files": { "out_1": "output.mp4" },
  "ffmpeg": {
    "args": [
      "-i", "{{in_1}}",
      "-vf", "drawtext=text='CONFIDENTIAL':x=10:y=10:fontsize=24",
      "-c:v", "libx264",
      "-crf", "23",
      "{{out_1}}"
    ]
  }
}

Three Architecture Differences

1. Direct Storage Delivery (BYOB)

Rendi stores every output in its own storage with a stable URL, and your app pulls the files from there. That is an extra network hop, and your media stays with a third party until you move it.

On paid plans, Xora writes final files directly into your own Cloudflare R2 bucket when the job completes — no copy step. On any plan, downloads from Xora’s managed storage are free.

2. Pre-configured Recipes

Rendi requires a full FFmpeg command for every task, whether it is complex or simple.

Xora has 9 pre-built recipes (like webReady, proxy, compress, trim and thumbnail) plus a probe mode. The webReady recipe probes first: it passes through files that are already web-ready, stream-copies when only the metadata needs moving, and re-encodes only when it has to.

3. Agents That Run Jobs

Rendi’s MCP server helps an agent search and read the Rendi docs. It does not run FFmpeg commands.

The Xora MCP server runs jobs. An agent calls create_job with FFmpeg args or a recipe, polls get_job, and gets a signed URL for the output. See FFmpeg for AI agents.

Move a Rendi Command to Xora

Your FFmpeg command stays the same. Only the envelope around it changes.

  1. Split the string

    Turn the ffmpeg_command string into an array with one element for each argument. Remove the quotes that only grouped an argument; keep the quotes inside filter values.

  2. Keep the placeholders

    input_files, output_files, {{in_1}} and {{out_1}} work the same way. Output names use letters, numbers and underscores, plus an extension.

  3. Send and collect

    POST https://api.xora.sh/v1/jobs with "mode": "ffmpeg" and your API key. Poll GET /v1/jobs/{id}, or pass webhookUrl to get a callback.

Where Rendi Is Strong

Rendi runs real FFmpeg with your own commands, has webhooks, and charges no egress fees. When your files are small and the work on them is heavy — long filter chains on short clips — billing by processed GB can cost less than billing by machine time, as Scenario B shows.

Xora is the better fit when files are large compared to the work: thumbnails, trims, audio extraction and remuxes from big uploads. It also fits when you want recipes for common jobs, outputs in your own R2 bucket, or an agent that runs jobs through MCP.

Which one fits your jobs?
  1. Small files, heavy processing → Rendi
  2. Large files, light processing → Xora
  3. Agents that run jobs over MCP → Xora
  4. Outputs in your own R2 bucket → Xora

See all options in the best FFmpeg APIs compared, and Xora’s pricing.

Frequently asked questions

What is the best Rendi alternative?

It depends on your jobs. Xora is a good fit if you extract thumbnails, trims or audio from large files, want built-in recipes, want an AI agent to run jobs through MCP, or want outputs in your own Cloudflare R2 bucket. Rendi is a good fit if your files are small and the work on them is heavy, because it bills by file size and not by processing time.

How is Rendi priced compared to Xora?

Rendi bills the size of the input plus the output, in processed GB. Its Pro plan is $25 a month for 250 GB, and its larger plans go as low as $0.10 per GB (rendi.dev, checked 13 October 2026). Xora bills credits: one credit for each minute of machine time, plus credits for each GB of output. File size alone does not change a Xora bill.

Do I need a credit card for the free plan?

Rendi asks for a card on its free plan and makes a $5 verification charge that it refunds. Its free plan includes 50 GB of processing a month and up to 1 minute of run time for each command. The Xora Free plan needs no card.

Can I run my existing Rendi commands on Xora?

Yes. Both use {{in_1}} and {{out_1}} placeholders with input_files and output_files maps. To move a command, split the Rendi command string into a JSON array with one element for each argument, remove the quotes that only group an argument, and send it to POST /v1/jobs with mode set to ffmpeg.

Can an AI agent run FFmpeg jobs on Rendi or Xora?

Rendi's MCP server searches and reads its documentation; it does not run commands. The Xora MCP server runs jobs: an agent calls create_job with FFmpeg args or a recipe, polls get_job, and gets a signed URL for the output.

Ready to move a Rendi command to Xora?

Bring the FFmpeg command you already have, run it with one POST, and pay only for the credits your jobs actually use.

Get Started Free View Pricing