Rendi

About Rendi

Rendi is a hosted FFmpeg API that runs FFmpeg commands in the cloud without requiring local installation. Users send standard FFmpeg commands as a POST request to a REST API and poll for results, enabling video processing tasks such as converting formats, extracting audio, generating thumbnails and GIFs, burning subtitles, trimming and cropping, adding watermarks or overlays, merging clips, and transcoding between codecs like H.264 and VP9.

The service targets developers and platforms that cannot run FFmpeg directly, particularly serverless environments such as Vercel, Supabase Edge Functions, Netlify Functions, and Cloudflare Workers, which have short timeouts and restricted runtimes that don't support system binaries. It also integrates with automation platforms including Make, Zapier, n8n, and Supabase. Rendi provides a documentation MCP server for AI coding assistants (Claude Code, Cursor, Codex, VS Code, Gemini CLI) as well as docs published in plain markdown with an llms.txt index and an OpenAPI spec.

Rendi runs on high CPU/memory servers with reserve machines to avoid cold starts, supports run times over 20 minutes for heavy commands, and states a 99.9% uptime commitment. It states no egress or ingress fees and no per-encoding, duration, or resolution cost units. The company positions the service as an alternative to self-hosting FFmpeg on a VPS, citing avoided infrastructure management (scaling, patching, on-call) and isolation from FFmpeg codec parser vulnerabilities.

Key features

• REST API to run FFmpeg commands in the cloud without installing FFmpeg
• Supports long run times of 20+ minutes for heavy commands
• MCP server for AI coding assistants like Claude Code, Cursor, and VS Code
• No egress/ingress fees or per-encoding cost units
• Common use cases: format conversion, thumbnails, GIFs, captions, watermarks, trimming, and merging clips
• Auto-scaling infrastructure with reserve machines to avoid cold starts

Frequently asked questions