Hey guys, I built Rendobar because I kept running into the same problem with apps that need any kind of photo or video manipulation: getting the processing side to run reliably in production ends up becoming a whole project on its own. With Rendobar, you give us your media and choose what you want to do with it. You can use one of the jobs we’ve built, or run your own operation with an FFmpeg command when you need something custom. You can also choose where the output goes. We can read from and write to your own storage, including S3, R2, and Supabase, or deliver results through callbacks and webhooks. You don’t need to know FFmpeg to use Rendobar. You can use our higher-level compose job for common video workflows, or drop down to a custom FFmpeg command when you need more control. This way, you can keep things simple when you want and still handle advanced use cases when you need to. Another thing I disliked about other media APIs was the credit-based pricing. I found it hard to predict what a job would actually cost. With Rendobar, we charge based on compute time, so you know what you’re paying for and can optimize your commands or operations to make them cheaper. It started with just FFmpeg and FFprobe, and I’m gradually adding more jobs around the common things developers need: timeline composition, subtitles, animated captions, compression, image generation/editing, and more. There’s also an SDK, CLI, MCP server, webhooks, n8n and Activepieces integrations. I’ll keep adding more jobs as I go, with the goal of making Rendobar the go-to media layer for any app that needs to process, manipulate, or generate images and video. Happy to answer anything!

Rendobar

Video API for developers: FFmpeg, compose, captions, images

Video API for developers: FFmpeg, compose, captions, images