One plane of control,
three ways to hold it.
Watch it on the dashboard, explore it in data views, codify it as tests — the same instruments, the same live data, three levels of rigor.
Every instrument on one live surface
The moment the rack pairs, every instrument it found appears as a panel: channels streaming live, setpoints you can type into, outputs you can toggle, captures you can arm — from any browser on the LAN.
Hardware abort limits stand armed underneath everything. Cross a threshold and the rig de-energizes itself — the watchdog doesn't care whether a test or a human was driving.
Every value lands, every window is explorable
Everything that streams also persists. Data views replay any time window: overlay channels, zoom into a transient, and hover to read exact values at any instant. Test runs paint the timeline green and red, so you can see at a glance where things passed and where they didn't.
Scope captures pin to the timeline where they happened, attached to the run that produced them. Underneath it's plain Postgres on your box — psql, pandas, and Grafana all work.
Procedures become code, results become records
A test is a Python file: phases, measurements, pass/fail limits. Guppi derives the plan from your code, shows it for approval, then drives the same instruments the dashboard does — sweeps, operator prompts, safety guards included.
Every run is a permanent record: measurements against limits, waveforms, logs, and the DUT it ran against — reopenable in seconds.