Step 1
Pip Planner
Reads your description and screenshots, then plans the scenes: what each one says, what it shows and how long it runs.
“4 scenes. No filler.”
Scene planHow it works
You describe your product and drop in screenshots. Four agents pass the work down the line while you watch, and a launch-ready video comes out the other end. Every frame is code, so it comes out sharp and the same every time.
Step 1
Reads your description and screenshots, then plans the scenes: what each one says, what it shows and how long it runs.
“4 scenes. No filler.”
Scene planStep 2
Takes the colors from your logo, picks the type and decides how things move.
“Stole your logo's colors.”
Palette + typeStep 3
Writes the video as code: HTML and animation timelines, one block per scene, with your screenshots inside.
“Built. Zero bugs. Probably.”
Video codeStep 4
Checks the build against the plan and the rules, flags anything off at an exact timestamp and sends fixes back.
“Hmm. Fine. Approved.”
Notes + approvalResult
Preview right away. MP4 when it's rendered.
Nib doesn't paint pixels. It writes a composition: plain HTML with timed scenes and seekable animation timelines. A real browser engine draws each frame exactly, then the frames are encoded into a video.
Estimate for a 10-second video. Real numbers get posted once the render workers are live.
| Agents (four model passes) | $0.40 – $0.90 |
|---|---|
| Render to MP4 on a cloud worker | under $0.05 |
| Storage and delivery | under $0.01 |
| Per video | about $0.50 – $1.00 |
No. The agents write code and the code is rendered. No model paints pixels, which is why text and UI stay sharp.
A browser and a couple of lines about your product. Screenshots and a logo make the video yours.
Run it again with a changed description, or download the source and edit it.
You do. Post them anywhere.