Hey Product Hunt! 👋

I’m Erkin, the creator of Slyber Inspector.

Anyone who has built a WebRTC app knows that testing NAT traversal and TURN server infrastructure is painful. Usually, you end up squinting at raw webrtc internals dumps, using an outdated Trickle ICE page that only checks basic candidate gathering, or writing custom scripts just to see if your media relay actually holds up under load.

I built Slyber Inspector to give developers and DevOps engineers a complete, visual WebRTC and TURN/STUN testing workbench that deploys in seconds via Docker or a single binary.

What you can test inside the Web UI:

Network Connectivity & Relay Allocation: Verify UDP, TCP, and TLS transport layers and confirm your STUN/TURN server allocates relay candidates properly.
Two User Live Video Streaming: Spin up a real two peer video call right in your browser to inspect media stream integrity, bitrate, packet loss, and jitter over the relay.
HMAC-SHA1 & Redis Authentication: Validate both static shared secrets (COTURN/Slyber style) and dynamic credentials stored in Redis.
Real Time Redis Key Revocation: Test active session termination on the fly to verify that your TURN server drops unauthorized streams the millisecond a key is revoked.
ICE Restart & Path Switching: Simulate network changes and trigger ICE restarts directly from the UI to ensure calls survive connection drops.
Infrastructure Load Testing: Stress test your TURN server with concurrent allocations and synthetic media traffic before going to production.

Slyber Inspector works with any standard TURN server, and pairs seamlessly with our companion Slyber TURN Server (a high performance, single binary TURN/STUN server in Go).

Both tools are free and open source:

Slyber Inspector: https://slyber.com/slyber-inspector
Slyber TURN Server: https://slyber.com/turn-server

Would love to hear how you currently test your WebRTC infrastructure and what diagnostic metrics you'd like to see added next!