ReelSDK vs Rendi: $0.02 a minute vs $0.10 per extra GB

A Rendi alternative that bills ffmpeg by the minute: $0.02 per compute minute, no plan

ReelSDK charges for the machine's whole time on the job, fetching inputs and storing outputs included, at $0.02 per compute minute from 1 s. Rendi charges for the gigabytes a command reads and writes instead: 50 GB a month free with a card, then plans from $25 a month and $0.10 per extra GB. For a 60 s 1080p clip, a full re-encode costs about 1.4 cents on ReelSDK and about a third of a cent on Rendi; a stream copy costs under a fifth of a cent on ReelSDK and still about a third of a cent on Rendi.

Two jobs on one 60 s 1080p clip
  • ReelSDK, stream copy0.14 cents
  • Rendi, stream copy0.35 cents
  • Rendi, re-encode0.35 cents
  • ReelSDK, re-encode1.37 cents

ReelSDK: wall time x $0.02 per compute minute, an upper bound (about 4 s for the copy, 41 s for the re-encode). Rendi: input plus output size, about 35 MB for either job, x $0.10 per GB, the extra-credit rate and the rate of the $25 plan with 250 GB.

Which one to pick

Pick ReelSDK if

  • Your commands move bytes more than they burn CPU: remuxing, trimming or adding +faststart with -c copy cost under a fifth of a cent here, against about a third of a cent on Rendi
  • You want no plan and no card: $0.50 of free credit at sign-up, then prepaid credit
  • You also want slideshows, captions or faceless shorts from the same key, at $0.03 per output minute or from $0.30 a short

Pick Rendi if

  • You mostly re-encode: per-GB billing made our 1080p re-encode about a quarter of what it cost on ReelSDK
  • You need more CPU per command: up to 32 vCPU, and unlimited runtime on plans from $50 a month
  • You want a large free tier: 50 GB a month is about 1,400 runs of a 60 s 1080p re-encode, if 1 minute per command is enough

Price per minute

Rendi plans and ReelSDK prices

Rendi meters processing as input plus output size in GB. ReelSDK meters the seconds its machine spends on the job, fetching inputs and storing outputs included. Which one costs less depends on how much work each byte needs.

Rendi plans and ReelSDK prices
PlanPriceIncludedPer command
Rendi Free$0, card required50 GB a month, 4 vCPU1 minute, 4 commands a minute
Rendi ProFrom $25 a month250 GB, 4 vCPU10-minute runtime; unlimited runtime from $50 a month
Rendi Pro, largest$1,600 a month16 TB, 256 vCPUUp to 32 vCPU per command
Rendi extra credits$0.10 per GBNever expireNo egress or ingress fees
ReelSDK raw ffmpeg$0.02 per compute minuteNo plan, first $0.50 free, no card10 minutes, 500 MB per input, 1 GB per job

Rendi Pro runs unlimited commands per minute. A failed ReelSDK job costs $0. See ReelSDK pricing. Prices from Rendi pricing, checked November 2026.

Head to head

ReelSDK and Rendi, feature by feature

ReelSDK and Rendi compared
ReelSDKRendi
Billing unitCompute minute, billed from 1 sGB processed: input plus output
Re-encode a 60 s 1080p clipAbout 1.4 cents (41 s of compute)About a third of a cent (35 MB)
Stream copy of the same clipUnder a fifth of a cent (about 4 s)About a third of a cent (35 MB)
PlansNone: prepaid credit, first $0.50 free, no cardFree with a card, Pro from $25 a month
Requestinputs, an args array and outputsinput_files, output_files and one ffmpeg_command string with {{in_1}} and {{out_1}}
Getting the result?wait holds the request up to 300 s, then 202 and a poll URLPoll GET /v1/commands/{command_id} or use a webhook
Run time per command10 minutes1 minute on Free, 10 on Pro, unlimited from $50 a month
Throughput3 running jobs and 500 jobs a day per key4 commands a minute on Free, unlimited on Pro
WebhooksHMAC-SHA256 in Reelsdk-Signature, up to 6 attempts over about 7 hRetried on a schedule; your endpoint must answer within 15 seconds

Be honest

Where Rendi is the better choice

  • Cheaper heavy encodes

    Rendi bills bytes, not time, so a CPU-heavy command costs the same as a light one. Our 1080p re-encode came to about a third of a cent on Rendi, about a quarter of what it cost on ReelSDK. If most of your jobs re-encode video, Rendi's model costs less.

  • More CPU and longer runs

    A Rendi command can use up to 32 vCPU, plans go up to 256 vCPU, and runtime is unlimited from $50 a month. A ReelSDK job stops at 10 minutes.

  • A bigger free tier

    50 GB a month covers about 1,400 re-encodes of a 60 s 1080p clip, as long as each command finishes within 1 minute; it needs a card. ReelSDK gives $0.50 of free credit at sign-up with no card.

Migration

Moving a render from Rendi

Rendi names inputs and outputs in two maps and refers to them with placeholders in one command string. ReelSDK's ffmpeg API does the same with inputs, outputs and an args array, so a Rendi command moves over almost token for token. This job ran on our API in 41 seconds; here is the output.

Rendi today

rendi.sh
curl https://api.rendi.dev/v1/run-ffmpeg-command \
  -H "X-API-KEY: $RENDI_KEY" \
  -H "Content-Type: application/json; charset=utf-8" \
  -d '{
    "input_files": { "in_1": "https://api.reelsdk.com/f/lib/in/vs/bbb-1080p-60s.mp4" },
    "output_files": { "out_1": "out.mp4" },
    "ffmpeg_command": "-i {{in_1}} -c:v libx264 -crf 23 -preset fast -c:a aac -b:a 128k -movflags +faststart {{out_1}}"
  }'
# { "command_id": "<uuid>" }

# Poll until status is SUCCESS, then read output_files.out_1.storage_url
curl https://api.rendi.dev/v1/commands/$COMMAND_ID \
  -H "X-API-KEY: $RENDI_KEY"

The same render on ReelSDK

reelsdk.shTry it
curl "https://api.reelsdk.com/v1/ffmpeg?wait=120" \
  -H "Authorization: Bearer $REELSDK_KEY" \
  --json '{
    "inputs": {
      "in.mp4": "https://api.reelsdk.com/f/lib/in/vs/bbb-1080p-60s.mp4"
    },
    "args": [
      "-i", "in.mp4", "-c:v", "libx264", "-crf", "23", "-preset", "fast",
      "-c:a", "aac", "-b:a", "128k", "-movflags", "+faststart", "out.mp4"
    ],
    "outputs": ["out.mp4"]
  }'

Field by field

Rendi fields and their ReelSDK equivalents
RendiReelSDK
input_files.in_1inputs["in.mp4"]
{{in_1}} in the commandin.mp4 after -i
output_files.out_1outputs: ["out.mp4"]
ffmpeg_command stringargs array
max_command_run_secondstimeout_s, 1 to 600
GET /v1/commands/{command_id}?wait=120 on the create call, or GET /v1/jobs/{id}
output_files.out_1.storage_urljob.outputs["out.mp4"], kept 7 days

FAQ

ReelSDK vs Rendi, answered

Is ReelSDK cheaper than Rendi?

It depends on the command. Rendi bills $0.10 per GB of input plus output; ReelSDK bills $0.02 per compute minute. On the same 60 s 1080p clip, a full re-encode cost about a third of a cent on Rendi and about 1.4 cents on ReelSDK, while a stream copy cost about a third of a cent on Rendi and under a fifth of a cent on ReelSDK.

Does Rendi have a free plan?

Yes: 50 GB a month with 4 vCPU, but each command can run for 1 minute, you can send 4 commands a minute, and it needs a card. ReelSDK gives $0.50 of free credit at sign-up with no card, which is 25 compute minutes of ffmpeg.

How do I move a Rendi command to ReelSDK?

Put each input URL under a file name in inputs, write the command as an args array that uses those names, and list the outputs. {{in_1}} becomes in.mp4 and {{out_1}} becomes out.mp4, and max_command_run_seconds becomes timeout_s, from 1 to 600.

How long can a command run?

Up to 10 minutes on ReelSDK. Rendi allows 1 minute on Free, 10 minutes on Pro and unlimited runtime on plans from $50 a month, so very long encodes fit Rendi better.

Other comparisons

Ready to build?

Ship video from your app today

Your first $0.50 is free, and one key covers every endpoint.

Moonlit lake with a lit cabin under the mountains