LOCAL · ON THE PULSEBOX
Real-time render. Hardware I/O. Cockpit. DMX, MIDI, projection. Offline-tolerant — the show keeps running when the internet drops.
pulsebox.local
PULSE CLOUD · MISSION CONTROL
Live.
Every PulseBox in your fleet, every active installation, every cue as it fires — on one surface.
DEVICE FLEET · live telemetry from your paired boxes
Your PulseBoxes, right now.
No PulseBoxes connected yet
This is your live fleet view. Each paired PulseBox reports its scene, BPM and signal here automatically — nothing is paired to this account yet.
PROJECTION PREVIEW · what each PulseBox is rendering right now
Wall of outputs.
No outputs to preview
Output previews stream from PulseBoxes that are online. Pair a box and connect a display to see its wall here.
ACTIVE INSTALLATIONS
What's on the walls.
No installations yet
A venue appears here once a PulseBox is paired to it and assigned a scene.
THE TWO HALVES
How Pulse runs.
CLOUD · THIS SURFACE
Monitoring, sync, scenes, and remote orchestration across every PulseBox in your fleet. The mission-control half.
pulse.wozuberlin.pro
Local control happens on the PulseBox. Cloud control is for monitoring, sync, scenes, and remote orchestration.
SIGNAL BUS
Live across the fleet.
Fleet BPM avg 0
60 ··· 180 BPM
Audio bus 0%
−∞ ··· 0 dB
Cloud heartbeat 0%
last 30s rolling
MIDI bus 0%
CC traffic across fleet
CUE ENGINE · LIVE FEED
Recent cues.
No cues fired yet
Every cue a PulseBox executes is logged here with its layer and timestamp. The log fills once a box is paired and a scene is running.
← Pulse Cloud
Pairing API + WebSocket sync land with the next PulseBox firmware release. Until then this surface shows only what is genuinely connected — which, until you pair a box, is nothing.