Unlimited video renders.
One flat price.
Send the JSON your n8n or Make workflow already produces to a webhook, and get an MP4 back through your callback URL. Plans are a fixed monthly fee based on concurrency, so higher render volume doesn't raise your bill.
See what your JSON renders
These are real renders from the built-in templates. Pick one below to see the JSON that produced it.
Compare fixed pricing with usage-based rendering
Running more renders through your n8n or Make flow doesn't cost anything extra on Rendofy.
Cost climbs with usage
As render volume grows, so does the bill. With usage-based pricing, cost scales with how much you render, so the more your automation runs, the less predictable the total gets.
Price stays fixed within your plan
Volume is unlimited. What's capped is concurrency, the number of renders that can run at once. You can send 10 renders or 10,000 renders this month and the price doesn't change.
| Usage-based rendering | Rendofy | |
|---|---|---|
| Pricing model | ✕Metered per render | ✓Flat monthly rate |
| Monthly cost at 1,000 renders | Scales with usage | $39–$199 fixed |
| Cost surprise risk | ✕High: usage spikes bill you | ✓No usage-based charges |
| Built for n8n/Make webhooks | General purpose API | ✓Native webhook-in, callback-out |
Designed for n8n and Make workflows
It's built around how n8n and Make actually send requests, not adapted from a general-purpose video API.
Instant template matching
Common payload shapes, like quote/author or title/subtitle, match locally in under a millisecond, with no AI round-trip and no added latency.
CDN-backed delivery
Every finished video is served from a global CDN, so it's fast to fetch and embed no matter where your automation runs.
Native n8n node
A published community node you can install directly, instead of configuring a raw webhook by hand.
npmjs.com/package/n8n-nodes-rendofy ↗Custom handling for unmatched payloads
If a payload doesn't match an existing template, Rendofy generates a custom composition for it instead of returning an error.
Unlimited renders. Fixed monthly price.
Plans differ by how many renders can run at the same time.
Starter
- ✓Unlimited render volume/month
- ✓Standard quality (1080p)
- ✓Template + custom compositions
- ✓Webhook + callback API
Growth
- ✓Unlimited render volume/month
- ✓Standard quality (1080p)
- ✓Template + custom compositions
- ✓Priority support
Scale
- ✓Unlimited render volume/month
- ✓High quality (up to 4K)
- ✓Template + custom compositions
- ✓Dedicated onboarding call
All plans include unlimited render volume per month; concurrency varies by plan.
From webhook to finished video
You post your payload, Rendofy renders the video, and your callback URL receives the result. No dashboard to configure and no SDK required.
POST /webhook/render-intake { "api_key": "your-api-key", "callback_url": "https://your-automation.example.com/hook", "payload": { "quote": "Ship it.", "author": "You" } } → { "status": "queued", "job_id": "b3f1..." } → (callback) { "status": "completed", "video_url": "https://..." }
Questions worth answering up front
The things people actually ask before wiring this into production.
What exactly does "unlimited renders" mean?
What if my JSON doesn't match a template?
Does this work with Make, not just n8n?
What resolution do I get?
How long does rendering take?
Can I test it before committing to a plan?
Ready to render from your workflow?
Send your JSON to Rendofy and get the finished MP4 back through your callback URL. Pricing is a fixed monthly fee, so there's no per-render bill to watch.