Generative work on IP that can't leave the building.
Studio and brand contracts increasingly forbid sending client material to public AI services. nooodles runs open models where you choose — so the work you currently have to decline becomes work you can bid.
The constraint is the contract, not the craft.
It runs where you choose
Hosted by default, so nobody needs a GPU to start. On your own hardware when the contract demands it — the model runs next to the material instead of the material travelling to the model. Unreleased product, an unannounced identity, a campaign still under embargo: none of it makes the trip.
Content security is becoming a vendor prerequisite
Major studio partner programmes and the MPA and TPN content security standards are the reason your clients now ask where the material goes and whether anything trains on it. Those are their standards, not a nooodles certification — we're not claiming one. The point is narrower and useful: a tool that can run inside your own secured environment is answerable to that review, and a cloud-only tool structurally isn't.
Otherwise it's a capital decision, not a project one
The usual alternative is standing up private GPU infrastructure yourself — hardware, racking, someone to run it, and a bet on which models matter in eighteen months. That's a board conversation with a payback period. Deciding per project, on the jobs that actually carry the constraint, is a different kind of decision entirely.
The graph is documented creative direction
A prompt is a wish. A graph is a set of decisions you made, written down, with the human choices legible — composition, timing, materials, what generation was allowed to touch and what it wasn't. US law protects human-authored expression (D.C. Cir. 2025; cert denied 2026), and an explicit authored graph is the strongest authorship position AI-assisted work can hold. It isn't a guarantee of ownership, and we won't pretend otherwise — take the specifics to your own counsel.
Art-directable and repeatable, not a slot machine
Generation is one operator wired into the thing it feeds — a texture pass on a model, a background behind a plate, a variation set under a director's note. Parameters, seeds and inputs are explicit, so a note like "same, but the light comes from the left" is a change you make rather than a prompt you re-roll and hope.
Same brief, two shapes.
Today
The brief has a generative component and an NDA that forbids public AI services. You have two options: turn the work down, or commit to building private infrastructure before you know whether the work is repeatable. Most studios pick the first and don't put it in the deck.
With nooodles
It's a project decision. The same graph runs hosted for the jobs that allow it, and inside your own environment for the ones that don't. You bid the work, and where the models run is a line in the technical response rather than a reason to pass.
The same graph pitches the work, not just frames.
Frames, boards, title variants and reels are a workflow — material your team cuts and places. But the same graph can also emit a scene: a live piece the client opens in the browser and moves through themselves.
Previs a sequence they can scrub. Send a look-dev comparison they can toggle. Pitch an interactive idea as the thing itself instead of forty slides describing it. Same source, same art direction — one output is files for you, the other is something they use.
The delivery
Frames, boards, title sets and cuts — files your team takes into the edit.
- Mode
- Workflow
- Who opens it
- You and your team
The pitch and previs
A live link the client opens and drives — options, timing, look, in the browser.
- Mode
- Scene
- Who opens it
- Your client, in the room
Start from something that already works.
These ship with the beta — open them, run them, or take them apart.
Private Pipeline
WorkflowRun generation inside the client's own environment. An offering we're defining with early customers — not something you can buy off this page yet.
by Jacques ParysSequence Frames
WorkflowHold look and character consistent across a sequence.
by Jacques ParysConfigurable Reel
SceneReorder a showreel per viewer or brief.
by Jacques ParysTitle Set
WorkflowProduce motion titles across durations and ratios.
by Jacques ParysWhat pipeline leads ask first.
What exactly runs locally?
The editor is a browser application and the engine cooks on your machine — geometry, materials, motion, compositing and the document itself are local already. The part that has a choice is generative inference: on free and Individual it runs hosted, and on Studio and Enterprise it can run against open models on hardware you control, so the weights stay put and the client material never leaves your network. Which specific models, on which hardware, is a setup conversation — that's the piece we're defining with early customers.
Do you train on our work?
Three honest answers, because they're different. On the hosted tiers we may use graph structure — how nodes are wired, not your source material — to improve the built-in assistant, and that's disclosed in the terms. A contractual no-training guarantee is available for enterprise. And on a local or self-hosted setup the question is settled by construction: nothing phones home, because there's nowhere for it to go.
Can we get it through our security review?
We'll do the work with you. The shape that usually passes is the local one: the material stays inside your environment, the models run on your hardware, and the data-flow answer is "it doesn't leave." We can't hand you a certification — we don't hold one, and any vendor who tells you their certification satisfies your client's audit is skipping a step. We can hand you an architecture you can put in front of a reviewer, and answer their questions directly.
Which models can we run?
Open models, and the next one. We deliberately don't build the product around a fixed list — generation is a node with inputs and parameters, so a model is something you point it at rather than something the tool is made of. That matters more than which name is fashionable this quarter, because the list changes every few months and your graph shouldn't have to.
Do we need to buy GPUs?
Not to start. Hosted generation is included on the paid tiers and most work never needs anything else. You'd only put hardware in the building for the jobs whose contracts require it — and the argument for nooodles is precisely that this stops being an all-or-nothing infrastructure bet and becomes a per-project decision.
Bid the work you're turning down.
Free to start, nothing to install. Or tell us what your contracts require and we'll walk through what running it inside your environment would actually look like.
Working with a team?
Tell us where to reach you and we'll set up a walkthrough.
No spam. A real reply from a human.