A unified visual interface for deep testing, media stream inspection, and load verification of WebRTC, TURN, SFU, and signaling servers directly from your browser without writing client code.
From STUN checks and writing hashes to Redis to spawning dozens of live video calls - all diagnostic tools are packed into a single Go binary.
From installing the inspector to launching dozens of simultaneous relayed video sessions with Redis and ICE Restart verification - in under 1 minute.
Interface architecture, supported verification modes, internal APIs, and deployment parameters.
Answers to common technical questions from engineers and QA specialists on visual testing of WebRTC applications, TURN, SFU, and Signaling servers.
Deploying and maintaining your own real-time infrastructure - whether it is a TURN/STUN relay, a selective forwarding unit (SFU), or a signaling server - always comes with the challenge of end-to-end verification. Console socket checks only show that a port is open, without answering an engineer's core questions: does actual browser video and audio flow through the relay, does Redis authentication work properly, does a call survive an ICE Restart procedure, and how much bandwidth can a node handle when dozens of user pairs are connected simultaneously. Slyber Inspector was built to solve these exact problems.
Typically, verifying a new TURN server requires developers to spin up a test web application, configure signaling exchange, manually generate database credentials, and open multiple browser windows. Slyber Inspector combines all of these components into a single compact Go binary, slyber_test, that deploys in 30 seconds:
Spawn pairs button creates the specified number of independent RTCPeerConnection pairs directly inside your browser tab. The built-in /ws signaling channel immediately exchanges SDP Offer/Answer messages and ICE candidates. Selecting the relay only (force turn) policy blocks direct connections and forces every byte of video and audio through your external TURN server over UDP, TCP, or TLS./api/provision endpoint handles all cryptography. In secret mode, it either computes temporary HMAC-SHA1 tokens locally or requests them from the TURN server's HTTP API (/api/turn-credentials). In redis mode, the inspector automatically connects to your specified Redis instance, calculates the 32-character RFC 5389 MD5 hash, and writes keys matching turn/realm/<REALM>/user/<USERNAME>/key with the required TTL.Revoke redis key button that deletes a specific participant's key from Redis mid-call, letting you verify how your infrastructure reacts to revoked permissions. The Ice restart button triggers session renegotiation via createOffer({ iceRestart: true }) and visually demonstrates seamless switching of allocated UDP relay ports without stopping video playback.IndexedDB database, while all connection settings and the selected tab are saved in localStorage. Even after a page reload, your testbed is ready for action. And when you need to quickly verify a server from a clean machine without video files, the built-in generator creates 4 distinct synthetic streams powered by Canvas and the Web Audio API.Forget about manually building test WebRTC clients and guessing when debugging network issues. Deploy the single Slyber Inspector binary with a built-in video pair spawner, Redis key inspection, and live telemetry right now.