I built Rendofy because video rendering felt unnecessarily awkward to automate. Send structured JSON, get a job ID immediately, and Rendofy sends the finished MP4 back to your webhook when it's ready. No polling or waiting around for renders to finish. It's built for n8n, Make, developers, and other automation workflows, with flat monthly pricing based on concurrency instead of charging for every render.
Hey 👋
Rendofy came out of a pretty simple frustration.
I was building automated video workflows and didn't like how much plumbing was involved just to get a finished video back into the workflow. Submit something, poll for status, deal with render timing, then figure out what to do with the resulting file.
I wanted the rendering step to feel more like infrastructure: send JSON, get a job ID, and carry on. When the video is finished, the MP4 comes back through a webhook.
That's what Rendofy does.
I've been building and testing it with n8n and Make, and we've also put together a public API collection and developer examples for people who prefer working directly with the API.
I also wanted pricing to be predictable, so the plans are based around concurrent rendering capacity rather than counting and billing every individual render.
It's still early, and that's part of why I'm launching it here. I'd genuinely like to know what people would build if video rendering were just another step in an automation.
If you work with n8n, Make, APIs or content automation, I'd especially love your feedback.