Case Study — Production SystemsProduction

BBB Room Live

A streaming bridge that broadcasts a live BigBlueButton session over RTMP to YouTube, Facebook, Vimeo, Twitch, and other destinations, without changing how the session itself is run.

Overview

What we built

BBB Room Live sits beside an existing BigBlueButton server: it joins a live session, captures the meeting's output, and broadcasts it over RTMP to a destination the organization chooses: YouTube Live, Facebook Live, Vimeo, Twitch, LinkedIn Live, Wowza, or a private RTMP endpoint.

The Problem

BigBlueButton isn't a broadcast tool

Organizations running BigBlueButton sessions sometimes need to reach an audience beyond the meeting itself: a public keynote, a graduation ceremony, a conference session. But BigBlueButton is built for interactive virtual classrooms, not broadcast streaming, and switching to a separate streaming platform for the session itself means giving up BigBlueButton's classroom features (breakout rooms, whiteboard, polling) for the audience that actually needs to be in the room.

Requirements

What the bridge needed to do

  • Stream a live BigBlueButton session over RTMP without changing how the session is run.
  • Support common destinations: YouTube, Facebook, Vimeo, Twitch, LinkedIn Live, Wowza, and private RTMP.
  • No changes to the presenter or moderator workflow.
  • Work with a BigBlueButton server the organization already operates.

Architecture

The bridge joins a running BigBlueButton session as a participant, captures its output, encodes it for the destination's ingestion requirements, and broadcasts it. The meeting itself never changes.

BigBlueButton Session
Streaming Bridge
RTMP Encode
External Platforms
Engineering Challenges

What was actually hard

Capturing a session without touching it

The bridge joins a live BigBlueButton session and captures its actual audio, video, and screen-share output as an external participant, rather than requiring any modification to BigBlueButton itself, so it stays compatible with a BBB server an organization already runs, instead of becoming a fork to maintain.

Destination-specific stream requirements

YouTube Live, Facebook Live, Vimeo, Twitch, LinkedIn Live, Wowza, and private RTMP endpoints each expect slightly different ingestion settings and credentials. The bridge is configured per destination rather than assuming one RTMP profile fits all of them.

Keeping the moderator workflow untouched

The bridge runs in the background specifically so a moderator never has to learn a second tool mid-session. Presenters, webcams, audio, screen sharing, and presentations all continue exactly as they would in a normal BigBlueButton session.

Solution

How it fits together

The workflow is deliberately unremarkable from a presenter's point of view: schedule the BigBlueButton meeting through the LMS, Greenlight, or custom application already in use, and start the session normally. The streaming bridge joins in the background, captures the meeting's output, and prepares an RTMP feed configured for whichever destination the organization has chosen. Universities, conferences, public events, and media teams use this to reach an audience that was never going to join the BigBlueButton room directly.

Technology

What it's built on

BigBlueButtonRTMPWebRTCMulti-Destination Streaming
Production Considerations

Running it, not just building it

  • Compatibility: works alongside a BigBlueButton server an organization already operates, rather than requiring a migration.
  • Reliability: configured per destination for stable capture, output settings, and credentials rather than a generic one-size-fits-all profile.
  • Delivery: low-latency streaming to public platforms and private RTMP endpoints alike.
Related Solutions

See it in context

Need to reach an audience beyond the meeting itself?

Real-time media, streaming bridges, or anything sitting between a live system and a broadcast platform: tell us what you're building.