Things people walk up to and use.
Taps, touch, sensors and live data feed straight into the graph. Build the experience, put it live on-site with a web link, and skip the fragile hand-off between tools.
This is the page with no equivalent anywhere else in the category.
Every other node-based AI tool ends at a file. You run the graph, it finishes, you download what it made and put it somewhere. That is a real job and we do it too — but it is not this job. Here the output is the experience: a person walks up, touches it, and it responds. No tool in this category can end there, so none of them has this page.
A workflow makes the material. A scene is the thing someone opens. An installation is a scene in the most literal sense — a stranger, a surface, and no manual.
Input is part of the graph, not something bolted on afterwards.
Input is a first-class part of the graph
Pointer, touch, keyboard, sensors and live data arrive as operators you wire like anything else. Interaction is not a scripting layer someone adds at the end — it sits next to the geometry, the materials and the state machine, wired into what it drives.
It deploys as a plain web link
The finished piece is an ordinary web page. There is no runtime to license per machine, no engine build to keep in sync with a show file, and nothing exotic to install on the show computer beyond a browser. That is one less fragile thing to babysit at 3am on a Sunday load-in.
Drive the wall and the visitor's phone from one graph
The installation and the companion piece are two outputs of the same source, sharing state in real time. Someone changes the colour on their phone and the wall answers. The two cannot drift, because there is nothing to reconcile — they were authored together.
Real-time 3D and physics, not a video loop pretending to react
The visuals are computed as they run — real geometry, real materials, real physics responding to real input. Visitors work out very quickly whether a thing is listening to them or playing back a loop with a few triggers on top, and they stop trying once they decide it is the second one.
A producer can adjust it on-site without opening the graph
The author exposes the controls that will need to move during an install — brightness for the room's actual lighting, timing, copy, the attract-loop delay — and locks the rest. The producer on-site changes them from a panel. Nobody has to fly the technical director back out to nudge a number.
Same activation, two shapes.
Today
The wall is built in one desktop tool by the studio's technical director. The companion phone piece is a separate web build, by a separate vendor, on a separate timeline, sharing nothing but a brand guideline PDF. They drift. Reconciling them the week before the show is somebody's fortnight.
With nooodles
Both are outputs of one graph. The generative visual system, the interaction logic and the state machine are authored once; the wall and the phone read from them. Change the visual system and both change. There is one thing to test, and one thing to fix.
The same graph makes the campaign around the installation.
The installation is a scene — visitors open it and use it. But every activation also needs flat material: social cutdowns, stills for the press release, renders for the case study, a loop for the client's internal channel. That is a workflow, and it comes out of the same graph.
So the film of the wall is made by the thing that makes the wall, not re-created in an editing suite from a phone video shot on site. When the visual system changes in tech rehearsal, the case-study renders are not quietly wrong.
The installation
The wall, the kiosk, the companion piece — the thing a visitor walks up to and uses.
- Mode
- Scene
- Who opens it
- Your audience
The campaign material
Social cutdowns, stills, case-study renders — files your team and the client place.
- Mode
- Workflow
- Who opens it
- You and your team
Start from something that already works.
These ship with the beta — open them, run them, or take them apart.
Touch Wall
SceneDrive an installation surface from touch and gesture.
by Jacques ParysCompanion Piece
SceneShare the installation's state with the visitor's phone.
by Jacques ParysLive Data Board
SceneBind a scene to a live feed and let it run.
by Jacques ParysFrame Extractor
WorkflowPull graded stills and cutdowns out of the live piece, for the case study.
by Jacques ParysWhat producers ask first.
Does it need special hardware?
It needs a machine that runs a current browser with hardware acceleration — the same class of machine you would already be putting behind a screen. Heavier scenes want a real GPU, the way any real-time work does. There is no dongle and no per-machine runtime licence.
What happens if the network drops?
A scene is a web page: once it has loaded, it runs in the browser on the show machine, so a dropped connection does not stop what is already playing. Anything bound to a live feed holds its last value until the feed returns. For a venue with unreliable connectivity, serve the page from a machine on-site and keep the network out of the critical path entirely.
Can it drive a projector or an LED wall?
Yes. To a projector or an LED processor it is a display output like any other — full-screen the page on the show machine and send the signal on. Because layout is computed rather than fixed, you can author to the wall's real pixel dimensions instead of making a 16:9 comp and hoping it maps.
How do visitors get it on their phone?
A link — usually behind a QR code on the plinth or the wall itself. They open it in the browser they already have. No app, no store, no install, nothing to download while standing in a queue.
Can it react to live data?
Yes — a feed is an input to the graph like touch or time. Ticket sales, a scoreboard, weather, sensor readings, a queue of visitor submissions. The visual is computed each frame from whatever the data currently says, so it stays current without anyone re-rendering anything.
Build the show and the thing they take home.
Free to start, nothing to install. Or tell us about the activation you're scoping and we'll walk through it with your own work.
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.