OBS / encoder ingest
Create a channel in the dashboard, open OBS → Settings → Stream → Custom, use the OA RTMP server shown in Encoder Setup, and paste the private stream key. Use H.264 video, AAC audio, CBR and a 2-second keyframe interval.
Operator guide
Focused documentation for WebRTC, OBS, RTMP ingest, simultaneous relays and website playback.
Create a channel in the dashboard, open OBS → Settings → Stream → Custom, use the OA RTMP server shown in Encoder Setup, and paste the private stream key. Use H.264 video, AAC audio, CBR and a 2-second keyframe interval.
Open Browser Studio, select a channel, allow camera/microphone access and choose Go Live. Browser publishing uses WHIP/WebRTC into the same OA media core as your encoder workflow.
Open Destinations, add the RTMP/RTMPS server URL and stream key supplied by each platform, enable the destinations you want, then start relays after your source is live.
Open Embed Player, select a channel and copy the iframe code. Viewers connect to the public WHEP/WebRTC player without seeing your private ingest key.
Treat OA ingest keys and social stream keys as passwords. Rotate an OA ingest key immediately if it is exposed. Social destination keys are encrypted at rest in the local database.
RTMP ingest uses TCP 1935. WebRTC media uses UDP 8189. The dashboard uses HTTP/HTTPS through Nginx. For production browser camera access, attach a domain and enable HTTPS.