Pricing
Simple, transparent pricing. Start free and scale as you grow.
Free
For individuals who are exploring
- 4 vCPUs
- Process 50GB monthly
- Up to 1 minute command run time
- 5 GB-month storage
- 4 commands per minute
- Store\Upload and analyze files
- Multiple API environments
- Zapier and Make integration
- Community support
Pro
For production applications with the power to scale
Everything in Free, plus:
- Unlimited commands per minute
- Priority processing
- Private file storage with presigned URLs
- Dynamic input and output files
- Chained Commands
- API webhooks
- Expert 1-on-1 consultation session
- Email support
See full price list
| vCPU | Price / mo | Processing | Storage |
|---|---|---|---|
| 4 | $25 | 100 GB | 50 GB-month |
| 8 | $50 | 400 GB | 100 GB-month |
| 16 | $100 | 1 TB | 250 GB-month |
| 32 | $200 | 2 TB | 500 GB-month |
| 64 | $400 | 4 TB | 1 TB-month |
| 96 | $600 | 6 TB | 1.5 TB-month |
| 128 | $800 | 8 TB | 2 TB-month |
| 192 | $1,200 | 12 TB | 3 TB-month |
| 256 | $1,600 | 16 TB | 4 TB-month |
| vCPU | Price / mo | Processing | Storage |
|---|---|---|---|
| 4 | $100 | 500 GB | 100 GB-month |
| 8 | $200 | 1 TB | 200 GB-month |
| 16 | $400 | 4 TB | 500 GB-month |
| 32 | $800 | 8 TB | 1 TB-month |
| 64 | $1,600 | 16 TB | 2 TB-month |
| 96 | $2,400 | 24 TB | 3 TB-month |
| 128 | $3,200 | 32 TB | 4 TB-month |
| 192 | $4,800 | 48 TB | 6 TB-month |
| 256 | $6,400 | 64 TB | 8 TB-month |
Enterprise
For large-scale companies
Everything in Pro, plus:
- Uptime SLAs
- Premium enterprise support
- SOC2
- Custom terms & assurance around DPA/SLAs
- Custom API limits
- Dedicated infrastructure
Frequently Asked Questions
How is processing calculated?
Processing is the sum of the size of the input and output media a command has processed. For example, an FFmpeg command that processes a 1 GB input file and creates a 0.5 GB output file will sum to 1.5 GB processing units. Pro plans are priced as low as $0.10 per GB processed.
What is command run time?
Each FFmpeg command can run for a different amount of time, depending on the media, requested command and compute power. The command run time is the maximum amount of time a single FFmpeg command can run with its specified resources.
How does vCPU allocation work?
Your account has a total amount of vCPUs available. You can specify the amount of vCPUs for each command. Multiple commands can run in parallel as long as their total vCPU usage doesn't exceed your quota. Each single command can use up to 32 vCPUs. We are using AMD processors for our compute instances.
Store and analyze files
Submit a file to be analyzed with FFprobe and stored in Rendi's storage. Read more about the endpoint here.
What are chained commands?
Submit multiple FFmpeg commands for batch processing together. Following commands can depend on output of previous commands. Running chained FFmpeg commands is faster than running each command separately because we re-use system and network resources between the multiple FFmpeg commands. Processing quota is shared between the commands, and is more efficient than running each command separately. Read more about the endpoint here.
What other costs are there?
No unexpected costs. No egress or ingress fees. No special cost units per different encodings, video duration or resolution. You only pay for the processing and storage you choose.
Why does the free tier require a credit card and a charge of $5?
We require a credit card to verify your identity and prevent abuse. The $5 is to confirm your payment method, and will be refunded once your card is successfully validated. You will not be billed any recurring fees for the free tier.
Consultation session
Paying customers who want to quickly set up their Rendi automation pipeline or optimize their existing commands are eligible for a one-on-one video consultation session with us. We offer a money-back guarantee if you are not satisfied with the results.
Dynamic input and output files
You can use wildcard patterns in your commands to process many inputs by sending a compressed zip folder using input_compressed_folder. You can also output dynamic files using our OUTPUT_FOLDER flag, to receive all output files as a zip folder. And, you can create playlists (HLS or MPEG-DASH) using playlist-outputs.