The canvas, the camera move and the timeline.
Each scene is a node with its own prompt, an approved frame and a named camera move — orbit, dolly, crane and the rest. The clips then sit on a multi-clip timeline. The same workspace connects an MCP server, a developer API, signed webhooks and automations.
Dashboard promo in panels. Made in Reigniter.
What you walk away with.
The last mile in the browser
Trim, reorder, join and re-cut before export, without another tool.
Adverts as a step in a workflow
Start a render from a trigger, an agent or your own code, and send the result on.
Your assets, where you need them
Stock footage in the canvas and every render in one project library.
Everything in editor.
A node canvas for the scenes, a named camera move on each one, a timeline for the clips, and your renders wired into the rest of your stack.
Three steps, then it is yours.
- 1
Make it on the canvas
Each scene is a node: prompt, approved frame and a named camera move.
- 2
Finish it in the editor
Trim, reorder and join clips on a real timeline.
- 3
Send it on
A webhook tells your server when the render finishes or a scheduled post goes out. An agent can start the render and check its status. It does not publish.
Start from one of these.
Every example came out of Reigniter. Hover to play, open one to start from it.
Before you start.
And everything else it makes.
Every area shares the same brand kit, the same canvas and the same credits. Add the rest whenever you need it.
Run automated ad campaigns. Grow your ROI.
Open Explore, put your product and logo on the canvas, approve the frames. Every Generate shows its credit cost before you spend.