VISP

VISP sends phone and browser cameras through an authenticated relay directly to Twitch, Kick, or YouTube. OBS can optionally read the original contribution feed for monitoring, recording, scenes, alerts, and graphics.

Direct resolves the selected destination with OAuth consent only while forwarding runs. Twitch and Kick keys are held in memory; YouTube uses a newly created public broadcast and its ingest destination. Relay encoder capacity is reserved before Go Live. The optional relay-to-OBS workflow never uses the provider stream key. The dashboard starts in Simple mode with labeled copyable URLs; switch to Advanced for RTMP fallbacks, read credentials, and latency tuning. If you get stuck during setup or on the dashboard, ask Seppo for help.

Start here

• Get started — authorize Direct, publish from a phone or browser, and optionally add OBS.
• Phone and browser app — platforms, chat, stream info, and the Apple Watch companion.
• Add a video source — paste a device sending URL into OBS, Larix, Moblin, or another encoder.
• Chat bot — live, BRB, and back alerts in chat, plus commands like !bitrate.
• OBS remote control — install and pair the plugin for start, stop, and scene switching.
• Encoders and fallback — Larix/Moblin, SRT latency tuning, and Advanced Scene Switcher.

Operators

• Architecture — hosts, media authentication, hooks, and OBS control flow.
• Self-hosting — app-plus-relays production layout, MediaMTX, firewalls, and acceptance testing.
• Local development — dependencies, env files, and focused dev servers.
• Releases and updates — GitHub Release workflow and safe server updates.

What VISP does not do

The ordinary relay-to-OBS path does not transcode. VISP Native can duplicate SRT packets over Wi-Fi and cellular for resilience, but it does not combine their bandwidth. VISP does not host OBS. MediaMTX accepts one publisher per path: the first wins until it disconnects.