Signal LabA test lab for OSC and network protocols

Send and watch the traffic your gear and services speak, stand in for the device or API that is not there yet, break the network on purpose — then run the same checks again from the app, a script or CI.

Get started

Download

Every protocol on the rack

OSC with typed arguments, raw UDP and TCP, HTTP with Basic, Bearer and Digest authentication, WebSocket and MQTT 3.1.1 — plus broadcast, multicast, subnet sweeps and a discovery listener.

One Inspector for everything

Every frame the tools send and receive, in one timeline, decoded and with its bytes. Filter it, export it, and replay a captured frame byte for byte.

A library of signals

Name the message that worked, file it in a folder and fire it again from anywhere with Ctrl+K — OSC, raw UDP, an HTTP request or an MQTT publish.

Emulators

Play the other side — a mock HTTP API, an OSC, UDP or TCP device, an MQTT broker — with rules, sequences, delays, faults and outages on a schedule.

Network impairment

A relay between a client and its target that adds latency, jitter, loss, duplicates, reordering or a bandwidth limit, or resets TCP connections — seeded, so the same traffic meets the same fate.

Experiments

Visual test flows — send, wait for the reply, check it, branch, loop, run branches in parallel — with parameters, profiles, secrets and a report for every run.

Load testing

Put an HTTP request under a constant rate, a ramp, steps, a spike or random arrivals, measure p50 to p99, errors and the rate achieved, and fail the run on thresholds.

Automation

Run experiments headless with the signallab command line — exit codes, JUnit reports, a GitHub Action — or hand them to an AI assistant over MCP.

Server and API

The same interface in a browser and the same engine on a lab PC or in Docker, signed in with a token — and an HTTP API for every command and run.

Signal Lab runs as a desktop app on Windows and Linux, or as a server you open in a browser. New to it? Read what Signal Lab is, install it, then take the first steps: a message sent and received, a signal saved, an emulated API answering, and a small experiment run — all on this computer.