Developer Infrastructure Comparison

Xora vs. Rendi

Running FFmpeg in the cloud shouldn't penalize your file sizes or lock you into proprietary hosting. Here is a head-to-head breakdown of billing, features, and storage architectures.

Feature	Rendi (rendi.dev)	Xora (xora.sh)
Billing Model	Processed File Size (GB)	Compute Allocation (GB-second)
Storage Architecture	Locked in Rendi's servers	Bring Your Own Bucket (BYOB) S3/R2
Egress Bandwidth Fees	Free egress (limits apply)	Free ($0.00) via direct BYOB writes
Pre-built Recipes	No (Custom arguments only)	Yes (10 optimized presets like `webReady`)
Shell Injection Safety	Command string parsing (high risk)	Sanitized arguments array (secure)
Free Tier Limit	50 GB (requires credit card hold)	1,000 compute-seconds (no card required)

Billing Mechanics: Processed GB vs. Compute-Seconds

Rendi charges based on total file sizes. Xora charges for the exact processor time you consume. 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.40

Bills for processing 2 GB of files (2.0 GB × $0.20/GB).

Xora Pricing

$0.00005

Seeks headers instantly. Job finishes in 1.5s using 2GB (3 GB-seconds).

Scenario B

High-compression of 50 MB video

Running heavy CPU transcode that takes 3 minutes using a 4GB worker profile.

Rendi Pricing

$0.015

Bills for 75 MB total input/output file size.

Xora Pricing

$0.012

Bills for 720 GB-seconds of compute resource duration.

Shell Command vs. Arguments Array

Rendi executes jobs by parsing a single command string. This forces your application to escape dynamic user strings, raising the risk of shell injections.

Xora takes a sanitized arguments array. Parameters are passed directly to the binary executor without shell execution, eliminating string escaping bugs and injection vulnerabilities.

Rendi Payload (String Command)

{
  "command": "ffmpeg -i {{in_1}} -vf \"drawtext=text='CONFIDENTIAL':x=10:y=10:fontsize=24\" -c:v libx264 -crf 23 {{out_1}}",
  "input_files": ["https://example.com/source.mov"],
  "output_files": ["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}}"
    ]
  }
}

Two Major Architecture Upgrades

1. Direct Storage Delivery (BYOB)

Rendi stores your output files on their servers, forcing you to download them to your application hosts. This creates a network hop, latency, and data ownership questions.

Xora writes final transcoded files directly into your own Cloudflare R2, AWS S3, or Backblaze B2 buckets. Egress bandwidth remains internal to your cloud provider, which means **you pay Xora $0.00 in egress fees**.

2. Pre-configured Recipes

Rendi requires you to write the raw FFmpeg command string for every single task, whether it is complex or simple.

Xora provides **10 pre-built, production-tested Recipes** (like webReady, proxy, probe, trim, and thumbnail). The webReady recipe even probes files automatically, performing simple metadata remuxes in milliseconds and only re-encoding when absolutely necessary.

Ready to migrate to Xora?

Configure your API credentials, test custom commands, and pay only for the compute seconds you use.

Get Started Free View Pricing