Make the assets. Build what people use.
A browser-native node graph where AI is a node. Run a workflow and get every asset a campaign needs. Build a scene and get an interactive experience you ship as a link.
Early access · free to start · nothing to install
Build it yourself
A real node graph — 3D, motion, generative AI, data and the document itself. Author it in the browser, ship it as a link.
See what you'd build →Run it without a programmer
One person authors the graph. Everyone else operates a surface they can't break — new product, new market, new format, same setup.
See how the hand-off works →Walkthrough — coming shortly
A workflow makes the material. A scene is the thing someone opens.
Same engine, same graph — you choose what comes out. Most tools in this space only do the first one.
Workflow
Every ratio, every locale, every cut. It runs, it finishes, and it hands your team files to place wherever they're going.
- Output
- Assets — stills, video, renders, variant sets
- Who opens it
- You and your team, then you place it
- Ships as
- Files
Scene
Not material at all — the thing itself. A page someone browses, a configurator they play with, an installation they walk up to.
- Output
- An interactive experience
- Who opens it
- Your audience, and they use it
- Ships as
- A URL, an embed, an installation
The campaign and the thing it points at come out of one graph.
A node graph for the web.
A procedural engine built for the browser — where generative AI is a node in the graph, not a panel bolted to the side. You build by connecting nodes, and there are ten kinds, each with its own colour and job.
Three bets the desktop tools can't make.
It builds the web itself
Most tools draw graphics onto a page. nooodles builds the page — real layouts and interfaces, not 3D pasted on top. Projects that don't need 3D stay light and load fast.
Not a panel on the side
Generation sits in the graph, wired to the thing it feeds. Describe what you want and the built-in assistant builds it with you — using only what nooodles really has, so it never invents nodes that don't exist.
Ship as a URL
A finished scene compiles to an ordinary web page — quick to load, easy to find, carrying only the parts it actually needs. Share it, embed it, send the link.
Find the job you're actually doing.
Every capability page shows the workflow that makes the assets — and the scene it can become.
Built by one. Run by everyone.
A nooodles graph exposes exactly the controls its author chose — a text field, a colourway, an upload, a slider. The rest is locked, on brand, and correct by construction. Whoever sets it up stops being a bottleneck and becomes leverage.
Sees a form, not a graph
A coordinator or producer swaps copy, picks a market, uploads an image — within the limits the author set, without a programmer in the loop.
Just opens the link
A finished scene goes live as a web link — any device, no install, no account. They simply use the thing you made.
When something works, save it and run it again.
Any workflow or scene can be saved as a Recipe — a piece of work you re-run on the next brief, hand to a teammate, or open and take apart to see how it was built. These ship with the beta.
Colourway Runner
WorkflowRender every colourway and angle from one product.
by Jacques ParysAspect Fan-out
WorkflowReframe one master into every ratio and placement.
by Jacques ParysLaunch Page
SceneShip a live, localised product page with a countdown.
by Jacques ParysProduct Configurator
SceneSpin it, swap it, configure it — in the browser.
by Jacques ParysOpen it and see.
nooodles is in early access — free to start, nothing to install, and things are still moving fast. The best way to judge it is to open a tab and build something.
Working with a team?
Tell us where to reach you and we'll set up a walkthrough of the author/operator hand-off with your own work.
No spam. A real reply from a human. Unsubscribe anytime.