Livestreaming
Native company livestreaming for town halls, all-hands, leadership Q&A, training and safety briefings — broadcast in-app, auto-recorded for on-demand playback, and metered per broadcast minute.
MangoApps
Overview
Livestreaming keeps a broadcast inside the same workspace as everyone's calendar, internal comms, and news feed, instead of handing the room to a separate webinar tool. Hosts point any RTMPS encoder — OBS, Wirecast, Zoom, or Teams — at MangoApps and go live; employees watch on web or mobile, with live chat, upvote-Q&A, and polls updating for everyone instantly.
Because the stream is a native object, what happens around it doesn't need a manual follow-up: a scheduled stream can mirror onto the company calendar, going live can draft a "we're live" post for an admin to publish, and a finished recording can land in the News Feed on its own. AI helps with the surrounding grind too — clustering duplicate audience questions for the host, and recapping what a late joiner missed — only when a person asks for it.
Highlights
Capabilities
Broadcast & recording
-
RTMPS encoder ingest (OBS / Wirecast / Zoom / Teams)
-
In-app HLS player on web and /m/ mobile
-
Host console — ingest URL, stream key, go-live / end controls
-
Live viewer count from heartbeat presence
-
Auto-record broadcast to on-demand VOD playback
-
Signed, short-lived playback tokens (access-controlled) Falls back to public playback when no signing key is configured
Live audience engagement
-
Live chat with Turbo Streams fan-out
-
Upvote-Q&A (ask, one vote per viewer)
-
Host moderation — mark answered / dismiss questions
-
Moderator soft-remove of chat (audit-preserving)
-
In-stream polls — launch, vote, close, live tally
-
Cross-viewer live fan-out of Q&A and polls
AI assist
-
"Catch me up" AI recap for late joiners Throttled per viewer to control LLM spend
-
AI Q&A clustering / dedup for hosts
-
AI post-event recap (summary, highlights, questions)
-
Auto-captioning of recordings (Mux ASR) When auto-transcribe is on
Connected apps & comms
-
Mirror scheduled streams onto the company Calendar
-
Draft a 'We're live' Broadcast on go-live Posts as a draft for an admin to publish
-
Auto-post recordings to the News Feed
-
In-app / push 'go live' notification
Admin, access & metering
-
Who-can-host setting (admins only / any user)
-
Per-event manage gating (host, creator, or admin)
-
Enterprise bring-your-own provider via Integrations Mux; configured under Admin → Integrations
-
Per-tenant recording & transcription defaults
-
Sample / demo data — load and clear
Limits & Specs
-
Metering unit: Broadcast minutes — stream wall-clock, audience-independent
-
Billing model: Pay-as-you-go, per broadcast minute (no floor)
-
Streaming provider: Mux (managed) or enterprise bring-your-own
-
RTMPS ingest endpoint: rtmps://global-live.mux.com:443/app
-
Signed playback token TTL: 6 hours
-
Live-viewer heartbeat window: 2 minutes
-
Chat message length: 500 characters
-
Question length: 1,000 characters
Use cases
FAQ
Livestreaming is pay-as-you-go, metered by broadcast minute — the stream's wall-clock duration, rounded up to the next minute when the stream ends. Metering is audience-independent, so how many employees watch never changes the bill, and there is no monthly floor.
Point any RTMPS encoder — OBS, Wirecast, Zoom or Teams — at the ingest URL and stream key shown in the host console, then click Go live. Browser-native broadcasting (no encoder) is on the roadmap.
By default streams auto-record to on-demand playback, and recordings are AI-captioned when auto-transcribe is on. If recording is turned off for an event, the auto-created recording is deleted at the provider so nothing is stored.
On the in-app watch page (web and /m/ mobile) viewers get live chat, upvote-Q&A — anyone can ask, one vote per viewer, so the questions people care about rise to the top — and in-stream polls they vote in. New questions and poll results fan out to every viewer live over Turbo Streams, with no page reload.
A late joiner can tap "Catch me up" for an AI recap of what they missed (throttled to about one request a minute per viewer since each call is LLM spend). Hosts get AI clustering that groups the flood of audience questions into themes, and a post-event AI recap summarizing the session, highlights and top questions.
When the matching options are enabled, a scheduled stream is mirrored onto the company Calendar, going live sends an in-app/push "we're live" notification and drafts a Broadcast for an admin to publish, and the finished recording can auto-post to the News Feed so people who missed it can catch up.
A tenant setting controls who can schedule and host — admins only, or any user; admins and app-admins can always host. Managing or moderating a specific stream (edit, end, answer/dismiss Q&A, remove chat) is limited to that stream's host, its creator, or an admin, not to anyone who merely has the hosting capability.
Streams use signed, short-lived playback tokens (about a 6-hour TTL) so a leaked URL can't be watched from outside your organization; when no signing key is configured playback falls back to public. Enterprise tenants can bring their own Mux account by configuring it under Admin → Integrations; otherwise streaming runs on the managed account.
Livestreaming is one-to-many live video — a host broadcasts a town hall or training from an encoder and the whole company watches an HLS player with live chat and Q&A. Broadcast is targeted text/media announcements (no live video) pushed to specific recipient groups. Live Assist is small-group WebRTC video — a remote expert joins a worker's phone-camera POV to guide a fix — not a company-wide broadcast.
