Choosing between Webex and BigBlueButton for teaching and training
If your renewal is driven by teaching, workshops or presenter-led sessions that need slides, whiteboard, polling and breakout rooms, BigBlueButton fits that work best when you run it in your own infrastructure. Webex fits broader meeting use across the whole organization, delivered as a cloud-managed service with Video Mesh nodes that stay registered to the Webex cloud. The choice turns less on feature checklists and more on four things: how your meetings split between teaching and general collaboration, whether a learning management system must embed the room, how sign-in must work, and whether you have staff and server capacity to run a virtual classroom platform yourself.
Start with the meeting mix. Count how many sessions are structured (a lecturer or trainer presenting, students annotating, polls run during the session, small groups sent to breakout rooms) and how many are ad hoc calls between colleagues. BigBlueButton's strength is the first group. Ad hoc calls, large internal town halls and room-device scenarios need a separate check against your Webex contract and hardware. Next, confirm your LMS. BigBlueButton is embedded in several learning management systems, so verify that your version and integration path are supported before you commit. For sign-in, Greenlight v3 can use OpenID Connect configured through environment variables, and the project suggests Keycloak as a broker for other login methods. Confirm that your identity provider can act as that broker. Finally, size the operation honestly. A BigBlueButton 4.0 server needs at least 16 GB of RAM with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings (50 GB without recording) and 250 Mbit/s symmetrical bandwidth, and it must be a clean install because direct upgrades from earlier branches are not supported. Ask who will patch, back up and scale that server, and how much recording retention you need. Webex hands these tasks to Cisco, while your team or an implementation partner owns them under BigBlueButton.
Which platform fits which meeting scenario
This table compares Webex Meetings with Video Mesh against a self-hosted BigBlueButton server across the meeting types most organizations run. Read each row for the better fit and the reason, then check the Video Mesh column for where media still depends on the Webex cloud and Control Hub. The main takeaway is that BigBlueButton fits structured teaching and training well, while on-premises media with Webex keeps a cloud dependency.
| Scenario | Better fit | Reason and what to confirm |
|---|---|---|
| LMS-embedded classes | BigBlueButton | BigBlueButton is embedded in Canvas, Moodle, Sakai, D2L and Schoology, so sessions open from the course. Confirm your LMS version and LTI setup with your administrator. |
| Internal training with slides and polls | BigBlueButton | Slides with annotations, polling, a multi-user whiteboard, shared notes and breakout rooms are built into the session. Webex can cover much of this, but the set is tuned for presenter-led sessions. |
| Ad hoc peer meetings | Webex or Jitsi Meet | BigBlueButton expects scheduled rooms managed through Greenlight or an LMS. Quick one-off calls are simpler in Webex or in self-hosted Jitsi Meet, which needs no room setup for guests. |
| External calls with many guests | Webex, or a load-tested platform | Guest sign-in and joining from outside your directory is smoother in Webex. For BigBlueButton, confirm guest access rules, capacity per server and whether you need a load balancer such as Scalelite. |
| On-premises media, with Webex | Webex Video Mesh | Video Mesh keeps media local, but the node is software on a Cisco UCS server that stays registered to the Webex cloud and is managed in Control Hub. Meetings still need that cloud connection to run. |
| On-premises media, with BigBlueButton | BigBlueButton | The server runs entirely in your network with no vendor cloud registration. Plan for at least 16 GB RAM, 8 CPU cores, 500 GB disk for recordings and 250 Mbit/s symmetrical bandwidth, per the install documentation. |
Where meeting data and media live under each option
Under BigBlueButton, media, recordings and identity sit on servers and accounts the organization controls. Under Webex, the on-premises part is a media node that still answers to the Webex cloud, so the data path has more than one owner. The cards below cover where each piece lives and what the organization must prepare itself.
BigBlueButton media and recordings
A BigBlueButton 4.0 server runs audio, video, slides and chat on hardware or cloud instances the organization provisions, and recordings are written to its own disk. The install guide calls for 500 GB of disk for recordings, or 50 GB without recording, so storage planning is part of the data decision. Confirm where backups of that disk are kept and who can retrieve them.
Webex Video Mesh control plane
Video Mesh is software on an on-premises Cisco UCS server, but it stays registered to the Webex cloud and is managed in Control Hub. Meetings stay local while capacity lasts and overflow to the cloud when it runs out. Ask Cisco which signaling, metadata and administrative data still leave the site, and document that boundary before the data residency review.
Identity through OpenID Connect
Greenlight v3 accepts external sign-in through OpenID Connect, configured with environment variables. The project suggests Keycloak to add Google, Microsoft, SAML and other login methods, which keeps identity records in the organization's own directory instead of a vendor tenant. Decide which identity provider is the source of truth for staff and learners, and confirm how account deprovisioning reaches Greenlight rooms.
API checksum secrets
Every BigBlueButton API call carries a checksum computed with a secret shared with the server, and the documentation warns never to embed that secret in a web page. Integrations from an LMS or intranet must compute checksums on the server side. Store the shared secret in a secrets manager, plan rotation, and review any page template that might expose it.
Hybrid cloud and bandwidth boundaries
A BigBlueButton server needs UDP ports 16384 to 32768 reachable and 250 Mbit/s symmetrical bandwidth, and a TURN server is recommended for users behind restrictive firewalls. Where that TURN relay or the server runs matters for which network path media takes. Map each media path to a hosting location and record it in the data flow diagram.
Compliance evidence to prepare
Auditors will ask where recordings, chat and identity records are stored, who can access them and how changes are logged. DeployOpen prepares systems, controls and evidence for assessments, but independent auditors issue any report or attestation. Gather the Video Mesh data processing terms from Cisco, the retention settings you configure on BigBlueButton, and access review records before the assessment starts.
How BigBlueButton 4.0 server sizing differs from Video Mesh nodes
Sizing a BigBlueButton 4.0 server is a decision you make and then own, because the requirements are published and the capacity planning is yours. The install documentation calls for at least 16 GB of RAM with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings (or 50 GB if you turn recording off) and 250 Mbit/s of symmetrical bandwidth. Ask your team to confirm each figure against the install docs for the exact release you plan to run, and to test the server under a realistic class size before the cutover. Network requirements are equally concrete: TCP ports 80 and 443 and UDP ports 16384 to 32768 must be reachable, the server needs a valid hostname for SSL, and Docker must be present so LibreOffice document conversion runs in a sandbox. A TURN server is recommended for users behind restrictive firewalls, and that is one more component to size and patch.
Video Mesh works differently. Webex Video Mesh is software installed on an on-premises Cisco UCS server, registered to the Webex cloud and managed in Control Hub, and it overflows to the cloud when local capacity runs out. The hardware specification and placement are still your responsibility, but the software lifecycle, enrollment and the policy for when meetings leave the premises sit in Control Hub. With BigBlueButton, the same questions are answered on your own servers. The install documentation covers a single server, and if you need more concurrent sessions, Scalelite is the open-source load balancer that distributes meetings across several BigBlueButton servers. Plan for it early, because the front end, the shared recording storage and the health checks change how you design the cluster.
Capacity planning, operating system updates, BigBlueButton point releases and security patches are all tasks for your operations team, or for a partner you hire under a written scope. The BigBlueButton project does not run your servers. Note also that BigBlueButton 4.0 does not support direct upgrades from 2.6, 2.7 or 3.0, so the install docs recommend a clean server installation. Before you commit, decide who owns on-call response, who applies the 3.0 maintenance releases while you migrate, and how you will test each update against a copy of your classroom workload.
What each option costs over time
What does a Webex subscription cost compared with running BigBlueButton?
Webex is a recurring subscription, so its cost repeats for every licensed user or host for as long as you keep the contract, and your Webex agreement or order form sets the exact figures. BigBlueButton carries no license fee because it is LGPL-3.0 licensed, so its recurring costs are the servers, bandwidth, storage, certificates and the people who run the platform. Ask your Webex account team for the subscription terms in writing, including renewal uplift, and compare them with a line-by-line estimate of your own infrastructure and staff time.
Do Webex Video Mesh nodes still carry hardware and licensing costs?
Yes. Webex Video Mesh runs on an on-premises Cisco UCS server, so you buy or lease that hardware and pay for the Webex entitlements that let the node register to the cloud and be managed in Control Hub. Those costs stay even when the media stays local, because the node depends on the Webex cloud. Ask Cisco or your reseller which hardware model, support contract and entitlements a Video Mesh design requires for your user count, and whether the cloud-side fees change when the node is idle.
How much server capacity does a BigBlueButton deployment need?
The published minimum for a BigBlueButton 4.0 server is 16 GB of RAM with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings (50 GB without recording) and 250 Mbit/s symmetrical bandwidth, according to the BigBlueButton install documentation. Real capacity depends on concurrent sessions, the number of webcams and screen shares, and how many recordings you keep, so most organizations size for peak concurrency and then add headroom. Ask your team or implementation partner to test with your actual session profile before buying hardware or cloud instances, and to confirm whether a second server or a scaling layer such as Scalelite is needed.
What drives bandwidth and storage costs for self-hosted BigBlueButton?
Bandwidth scales with concurrent participants and the video they send, and the documented baseline is 250 Mbit/s symmetrical. Recording volume drives storage: 500 GB of disk is the documented figure when recording is enabled, and retention policy decides whether that grows into a recurring cost. Cloud egress, if you host in a public cloud, is billed by the provider and can recur every month, so check the provider's pricing for the region and your expected session hours. Ask for a monthly bandwidth and storage forecast based on your retention rules, and confirm whether recordings must be archived off the primary server.
What do TURN servers, certificates and hostnames cost to run?
These are small but recurring items. BigBlueButton needs a valid hostname for SSL, and the install documentation recommends a TURN server for users behind restrictive firewalls, so you need a domain, a certificate and a TURN service that stays reachable on UDP and TCP. Certificates are often free through public certificate authorities, but a TURN relay carries media and adds bandwidth and host capacity. Ask for the certificate renewal process, the TURN host sizing and who monitors expiry dates.
What does identity integration cost for Greenlight with OpenID Connect?
Greenlight v3 supports external authentication through OpenID Connect, configured with environment variables, so the core setup is a one-time configuration task. The recurring cost comes from running the identity provider you connect to, for example Keycloak, which the Greenlight docs suggest for adding Google, Microsoft and SAML login. If you already run an identity provider, the marginal cost is low; if you do not, budget for hosting, patching and access reviews. Ask who owns the OIDC client registration, how user provisioning is handled and what changes when staff leave.
What staff time and upgrades does self-hosted BigBlueButton require?
Staff time is usually the largest recurring cost and is easy to underestimate. Each year the work includes applying maintenance releases on the branch you run, planning major upgrades, monitoring server health, managing recordings, handling LMS integration changes and answering user support. BigBlueButton 4.0 does not support direct upgrades from 2.6, 2.7 or 3.0, so moving between major versions means a clean install and migration work, which is a one-time cost. Ask your team to estimate hours per month for operations and to name who is on call during teaching hours.
When does paid support from BigBlueButton Inc. or DeployOpen make sense?
Support is optional, and the cost depends on the scope you need. BigBlueButton Inc. offers hosting and commercial support through bigbluebutton.com, and DeployOpen offers implementation, hardening, backup, upgrade and support work, with ongoing support and upgrades available as retainers. Most engagements are fixed-scope with written deliverables agreed before work starts, and DeployOpen does not publish a price list, so a quote follows from the written scope. Ask each provider for response times, covered versions, what happens during an upgrade and whether backups and restore tests are included.
What moving from Webex to BigBlueButton involves
The sequence turns a Webex meeting and training estate into a clean BigBlueButton server with identity, a proven pilot, archived recordings and a cutover that teachers and presenters can follow. Each step ends with a check that tells you whether to move on.
Inventory Webex use and LMS integrations
Start by listing what your Webex site does for teaching, training and structured sessions: which courses, teams and webinars use it, how people schedule and join, which recordings must be kept, and where Webex is already embedded in a learning management system such as Canvas, Moodle, D2L or Schoology. Your LMS administrator and the owners of each course or training program should confirm the list. The step is complete when every recurring session has an owner and a named replacement path, including any integration that needs an LTI connection to BigBlueButton. Ask your Webex administrator which Video Mesh nodes or hybrid components are involved, since those dependencies do not move with the meetings.
Build a clean BigBlueButton 4.0 server
Install BigBlueButton 4.0 on a new Ubuntu 24.04 64-bit server using the bbb-install.sh script, rather than upgrading an existing server. The BigBlueButton install documentation states that direct upgrades from 2.6, 2.7 or 3.0 are not supported, so a clean installation is the recommended path. Confirm the server meets the published minimums of 16 GB of RAM with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings and 250 Mbit/s symmetrical bandwidth, and that UDP ports 16384 to 32768 are reachable. The step is complete when a test meeting runs with audio, video and screen sharing from a network outside your own. Your infrastructure or hosting team owns this step, with DeployOpen or another implementation partner if you choose one.
Set up Greenlight, identity and API access
Deploy Greenlight, BigBlueButton's room manager, on the same server or a separate one, then connect it to your identity provider. Greenlight v3 supports external authentication through OpenID Connect configured with environment variables, and the documentation suggests Keycloak if you need additional login methods such as SAML or social sign-in. Set up room ownership, moderator roles and any LTI connection your LMS requires. Keep the BigBlueButton shared secret off web pages, because all API calls depend on it. The step is complete when a staff member signs in with corporate credentials, creates a room, and a learner joins it from the LMS without a separate password.
Pilot with one course or team
Choose one course, training program or team whose sessions use slides, whiteboard, polling and breakout rooms, and run its next cycle of sessions on BigBlueButton while keeping Webex available as a fallback. Record a sample of sessions to confirm playback, and have the presenters test polling, shared notes and breakout rooms against their usual material. Collect feedback on join times, audio quality on the networks your learners use, and whether the LMS embedding behaves as expected. The step is complete when the pilot group has run its sessions end to end and the open issues are logged with owners and a decision on whether each one blocks cutover.
Export recordings and archive them from Webex
Before the Webex contract ends, move the recordings your organization must keep out of Webex, following the export approach described in the Webex data export guidance. Download recordings individually or in batches through the recordings API, store them on storage you control, and check that each file plays and that its metadata, such as date, host and course, is recorded in an index. Messaging data and anything that cannot move to a self-hosted platform should be listed separately so the business owner can accept the gap in writing. The step is complete when a sample of exported recordings has been opened by someone outside the meeting and the archive index matches the Webex recordings list.
Retrain presenters and moderators
Run short sessions for presenters, moderators and course administrators covering the BigBlueButton room, presentation upload, annotation, polling, breakout rooms, recording start and stop, and how to find recordings in the LMS or Greenlight. Give each group a one-page guide that replaces the Webex instructions they currently use. Because the interface differs from Webex, plan for the first few sessions to need more moderation support. The step is complete when each presenter has run a rehearsal session on the new server without help from the pilot team, and the support contact for the first weeks is published to users.
Cut over and retire Webex scheduling
Switch new course and training sessions to BigBlueButton, update LMS links, calendar invitations and any Webex links in onboarding material, and confirm that no live sessions still depend on Webex scheduling. Keep the Webex site readable for the agreed period so people can find older recordings, and monitor server load, bandwidth and support tickets during the first live weeks. Decide on the Webex retirement date with the contract owner, and confirm that any Video Mesh nodes are removed from the network once no meetings use them. The step is complete when all scheduled sessions run on BigBlueButton, support volume has settled to an agreed level, and the cutover record is signed off by the business owner.
Questions buyers ask before choosing BigBlueButton
Can our team install BigBlueButton without outside help?
Yes, if your team has Linux server administration skills and time to work through the setup, but the install is not a single click. BigBlueButton 4.0 installs with the bbb-install.sh script on Ubuntu 24.04 64-bit, and the install docs recommend a clean server rather than an upgrade from 2.6, 2.7 or 3.0. The server must have a valid hostname for SSL, TCP ports 80 and 443 and UDP ports 16384 to 32768 reachable, and Docker for sandboxed document conversion. A TURN server is recommended for users behind restrictive firewalls. Teams without this experience usually hire outside help for the first install, the hardening and the upgrade plan, and should confirm the scope of that help in writing before work starts.
What server capacity does BigBlueButton need?
The install docs set a minimum for a single 4.0 server: at least 16 GB of RAM with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings (50 GB without recording) and 250 Mbit/s symmetrical bandwidth. Capacity planning then depends on how many concurrent sessions you run, how many participants join each one, whether you record, and how long you keep recordings. Recording drives disk use most. Ask your engineers to test a representative class size on the target hardware before you commit, and check the BigBlueButton documentation for multi-server guidance such as the Scalelite project if concurrent load grows.
How much staff time does self-hosting BigBlueButton take?
The staff time depends mainly on how many servers you run, how often you upgrade, how much you customize, and whether you need around-the-clock support for live classes. Each cost component is different: the hardware or cloud instances, the bandwidth, the storage for recordings, the engineers who install and patch the servers, the people who manage Greenlight rooms and LMS integration, and the support you buy if you want one. Hardware and bandwidth recur monthly or yearly, while the initial install and integration are largely one-time work. Ask any quote to split one-time and recurring costs, name who performs each task, and state the upgrade path to the next major release.
What does a migration from Webex to BigBlueButton involve, and how long does it take?
The duration depends on scope and cannot be quoted without knowing your facts. The main drivers are the number of meeting types you run, the number of users and rooms, the LMS or portal systems you connect, the identity source you want to use for sign-in, whether you keep existing recordings, and how many training courses or scheduled sessions must move. Webex Video Mesh nodes stay registered to the Webex cloud, so a Webex-to-BigBlueButton plan also needs a decision on the existing Video Mesh estate. Ask for a written scope that lists these items, a cutover plan with a parallel run, and the acceptance tests each side must pass before timelines are agreed.
Does BigBlueButton need extra work to connect to our learning management system?
BigBlueButton is embedded in learning management systems including Canvas, Moodle Cloud, Sakai, Jenzabar, D2L and Schoology, according to the project. Integration effort depends on which LMS you run, whether it is hosted or self-managed, and how you want rooms, roles and grades to flow. The install script can add Greenlight or LTI support on the same server, so some connections need configuration rather than custom code. Confirm with your LMS vendor which BigBlueButton integration they support, which BigBlueButton version it expects, and who owns the LTI credentials and their rotation.
Can we keep meeting recordings and user sign-in under our own control?
Yes, when BigBlueButton runs on servers you control, recordings are stored on your disk and user accounts can be handled through your own identity provider. Greenlight v3 supports external authentication through OpenID Connect, configured with environment variables, and the Greenlight documentation suggests Keycloak to add Google, Microsoft, SAML and other login methods. Confirm the retention period, backup location and access controls for recordings with your compliance team. Protect the API shared secret, because the API docs warn never to embed it in a web page, and make sure the checksum algorithm meets your policy.
Does Webex Video Mesh keep meetings fully local the way self-hosted BigBlueButton does?
Not in the same way. Webex Video Mesh is software installed on an on-premises Cisco UCS server that keeps meetings local and overflows to the cloud when on-premises capacity runs out, and it stays registered to the Webex cloud and managed in Control Hub. A self-hosted BigBlueButton server has no such registration, so the operator controls the software, the servers and the data path. Confirm with Cisco which Webex services still need the cloud for your tenant, because that determines whether your data residency and continuity needs are met.
How DeployOpen helps evaluate and implement BigBlueButton
DeployOpen is a Chainscore Labs company that plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside the client's own cloud accounts, data centers or air-gapped networks. For a Webex to BigBlueButton move, that work usually starts with a written scope that names the decisions first: which teaching formats move, how many concurrent rooms the school or training team needs, whether recordings are kept, and which LMS or Greenlight front end users will reach. Most engagements are fixed-scope, so scope, deliverables and timelines are agreed in writing before any server is built. Ongoing support, upgrades and continuous testing are available as retainers, which matters because BigBlueButton releases move on their own schedule and the 4.0 line requires a clean server installation rather than an in-place upgrade.
A useful evaluation covers the parts that differ most from Webex: the server sizing against the stated BigBlueButton install docs, the UDP media range, the TURN planning for users behind restrictive firewalls, the Greenlight v3 sign-in through OpenID Connect, and the API checksum secret that must stay on the server side. DeployOpen can run a proof of concept in a test environment, check whether the target hardware and bandwidth match the requirements, and document the results so your architecture and security teams can review them. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports, attestations or certifications. Independent auditors and certification bodies do that work, and your own compliance team should confirm which evidence they will accept.
DeployOpen does not publish a price list. A quote follows from the written scope, so ask for line items that separate discovery and design, installation and hardening, LMS and identity integration, backup and recovery setup, documentation, and any retainer for upgrades and support. Ask the provider to state which items are one-time and which recur, who carries the hardware and bandwidth costs, and what changes the price if the scope grows. Treat the scope document as the working contract: it should name the rooms, users, recordings and integrations covered, so that a decision such as adding Keycloak for Microsoft or SAML sign-in is priced as a change rather than absorbed silently.
