Shipped a major feature sprint — batch rendering, template variables, async callbacks
After weeks of planning and a focused weekend sprint, I just pushed the biggest feature update since launch.
What shipped:
Batch rendering — send up to 50 HTML items in one API call, get 50 images back. Partial failure support (HTTP 207 — failed items don't block successful ones). Plan-gated: Starter gets 10, Pro gets 50, Scale gets 100.
Template variables — use {{placeholders}} in HTML, pass a vars object. No more string interpolation. Available on all plans including free.
Async callbacks — callback_url parameter for fire-and-forget rendering. API returns 202 immediately, RenderPix POSTs the result when done. Pro+ feature.
waitUntil parameter — control when Chromium considers the page "ready" before capturing. load, domcontentloaded, or networkidle.
The motivation:
My only paying customer (Instagram carousel automation via n8n) was calling the API in a loop — one request per slide. Batch was the obvious solution. But instead of building just batch, I built the full automation-native feature set in one sprint.
Current state:
- MRR: $9 (1 Starter customer)
- Registered users: ~21
- n8n community node: 85+ installs
What's next:
- Landing page and docs updated to reflect the new features
- Distribution: blog posts, Reddit, Dev.to
- Outreach to current users about the new capabilities
The product is now meaningfully different from where it was a month ago. The question is whether the distribution can catch up.
This is a solid product move, especially because the feature sprint came from real usage instead of guessing.
The part I’d be careful with now is treating “distribution” as one big problem.
You already have a narrow signal: n8n installs, one paying workflow, and automation-native features. The risk is spreading the next push across blog posts, Reddit, Dev.to, and current users without deciding what signal you actually need from each.
I would not solve that loosely in the thread because the next move changes depending on whether you’re trying to prove the niche, find more of the same workflow, or move users from installs to paid usage.
If you’re open to it, share your email and I’ll put the tighter customer path together properly.
Hi, I am very new and still experimenting the moves. Please reach me out from
hello@renderpix.dev
Regards
Sent you a note by email.
I think the customer-path decision matters more than the distribution discussion right now.