The show and the thing they take home.
One graph drives the installation and the visitor's phone. Build the experience, deploy it on-site as a web link, and skip the fragile hand-off between tools and vendors.
The wall and the phone stop being two projects.
Input is a first-class thing, not a bolt-on
Touch, pointer, sensors and live data arrive as operators in the graph, wired to what they drive. Interaction is authored in the same place as the visuals, so there's no bridge layer to maintain between the thing that senses and the thing that draws.
The wall and the companion piece are two outputs of one graph
Same source, same state. What a visitor does on the wall is visible on their phone, because both surfaces read the same state machine rather than two implementations of it that someone has to keep in agreement.
It deploys as a plain web link
A scene ships as a web bundle. Point a full-screen browser at it on the show machine and that's the install — no bespoke player, no licence server phoning home mid-show, nothing fragile to babysit at 2am on the night before doors.
A producer can change things mid-install
The author exposes a handful of controls — a colour, a timing, a copy line, a mode — and locks the rest. On site, that's a form, not a graph. Nobody has to find the one person who knows the patch to change a headline.
Real-time 3D and physics, not a loop pretending to react
Geometry, materials, simulation and state are live operators cooking per frame. The piece responds because it is actually computing, which is the difference between an installation and a video wall with a proximity trigger.
Same activation, two shapes.
Today
The wall is built in one desktop tool by your TD. The 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 is somebody's fortnight, and it happens in the week you have least.
With nooodles
Both come from one source. The generative system, the interaction logic and the state machine are authored once; the wall and the phone are two outputs of it. Change the behaviour once and both surfaces are already right.
There's a licensing line under this too. A loaded seat today stacks several expensive desktop licences — one for the real-time system, one for 3D, one for compositing, plus whatever the web side needs. Consolidating the ones a project actually touches is a real number on a job you're already bidding.
The same graph makes the flat deliverables too.
You already live in scenes — the thing the visitor walks up to and uses. What's usually missing is everything around the show: the stills for the campaign, the cut for the case study, the frames the client's marketing team asks for on the Monday after.
Run the same graph as a workflow and it hands you those as files — the same visual system, the same type, the same materials, at whatever ratio and duration the ask arrives in. The case-study reel isn't a re-creation of the show. It comes out of the show.
The installation
The wall, the sensors, the companion piece on the visitor's phone, sharing state.
- Mode
- Scene
- Who opens it
- Your visitors
The material around it
Campaign stills, social cuts, case-study frames — files your team places.
- 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 gesture and input.
by Jacques ParysCompanion Piece
SceneShare installation state with the visitor's phone.
by Jacques ParysLive Data Board
SceneBind a scene to a live feed and let it run.
by Jacques ParysSocial Cutdowns
WorkflowCut the show footage into every platform format, for the campaign around it.
by Jacques ParysWhat technical directors ask first.
What hardware does a show machine need?
Anything that runs a current browser with a real GPU. It's a web runtime, so the machine is a spec decision rather than a platform decision — the same scene runs on the show PC, on your laptop while you're building it, and on a visitor's phone at whatever quality that phone can hold. Test on the actual show machine before you commit to a resolution and frame rate; that part of the job hasn't changed.
What happens if the network drops on site?
A scene is a bundle of files, so it can be served from a machine on the show floor and doesn't need the internet to run. Once it's loaded, nothing has to phone home. What does need the network is anything you deliberately wired to a live feed — data, or the companion phone piece — so decide in the graph what a quiet feed means: hold the last known value, fall back to a state, or show a designed message rather than a broken one.
Can it drive a projector or an LED wall?
The picture goes out the machine's display chain, like any full-screen browser window — projector, LED processor, or a capture card downstream of a display output. Canvas size, aspect and warping-friendly geometry are parameters in the graph, so odd resolutions and non-16:9 canvases are normal rather than a fight. There's no NDI or Spout output today; if your pipeline depends on that, tell us — it's on the list and we'd rather build it against a real show.
How do visitors get the companion piece on their phone?
They open a URL — a QR code on the plinth, a short link, an NFC tag, whatever suits the space. No app, no install, no store review in your build schedule. It opens in the phone's browser and reads the same state as the wall, so what they do on one shows up on the other.
Can we run the AI parts on-premises for a brand client?
Generation runs where you choose — hosted by default, and on your own hardware when the work can't leave the building. That's the Studio and Enterprise option, and the managed version of it is an offering we're defining with early customers rather than something you can buy off a page today. If you have an activation with that constraint, it's exactly the conversation we want. See motion design studios for how the IP-bound version is set up.
Tell us about the install.
Free to start, nothing to install. Or tell us what you're building — the surfaces, the inputs, the site — and we'll walk through how it comes out of one graph.
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.