Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
A side-by-side editorial comparison of BigBlueButton and PeerJS — release velocity, themes, recent moves, and the top alternatives to consider.
BigBlueButton is polishing the 4.0 beta it already committed to LiveKit, while 3.0 stays the production line.
The 4.0 beta series is in its fifth iteration and the hard architectural decisions are behind it — LiveKit became the default media stack in beta.4 with the legacy SIP.js bridge deleted, BlockNote became the default shared notes engine, and the JVM moved to Java 21. Beta.5 is consolidation: a mobile layout overhaul with paginated webcams and landscape side-by-side camera and presentation, automatic light/dark switching, a dedicated Audio settings tab with push-to-talk, and better BBB-to-LiveKit state reconciliation on reconnect. Packaging gained a bbbctl admin tool and a bbb-coturn package, with bbb-etherpad and bbb-pads now optional. The project still recommends 3.0.x for production.
PeerJS keeps publishing release candidates that restate the same two fixes.
Every entry in PeerJS's feed is a release candidate, and each one repeats the bug list of the one before it — the unreliable close event and the data channel ordering fix appear in all four, spanning fourteen months. The genuinely new content per release is thin: a CSP fix removing the need for unsafe-eval, Blob support inside nested objects, and dependency updates. The most recent publication is from April 2024.
The 4.0 beta series is in its fifth iteration and the hard architectural decisions are behind it — LiveKit became the default media stack in beta.4 with the legacy SIP.js bridge deleted, BlockNote became the default shared notes engine, and the JVM moved to Java 21. Beta.5 is consolidation: a mobile layout overhaul with paginated webcams and landscape side-by-side camera and presentation, automatic light/dark switching, a dedicated Audio settings tab with push-to-talk, and better BBB-to-LiveKit state reconciliation on reconnect. Packaging gained a bbbctl admin tool and a bbb-coturn package, with bbb-etherpad and bbb-pads now optional. The project still recommends 3.0.x for production.
The 4.0 line is converging toward a release candidate, and the work has shifted from replacing subsystems to making the new ones survive real conditions — reconnects, phones, and administrator tooling. Making etherpad and pads optional alongside a security advisory that urges API secret rotation points at shrinking the default install's attack surface. The parallel 3.0.x train continues shipping security patches, so the ecosystem is carrying two branches until 4.0 stabilises.
Expect beta.6 or a release candidate to focus on the LiveKit reconnection and mobile paths that beta.5 only started, since those are the areas where a self-hosted media migration typically breaks. The optional-package work suggests a slimmer default deployment is being prepared for the 4.0 release.
Every entry in PeerJS's feed is a release candidate, and each one repeats the bug list of the one before it — the unreliable close event and the data channel ordering fix appear in all four, spanning fourteen months. The genuinely new content per release is thin: a CSP fix removing the need for unsafe-eval, Blob support inside nested objects, and dependency updates. The most recent publication is from April 2024.
The changelog reads as a project maintained rather than developed, and one that never quite finishes a release cycle — candidates accumulate, notes carry forward, and stable releases do not appear in this feed. For a WebRTC wrapper this is a specific kind of risk: the browser layer underneath moves regardless, and the fixes that do land here are reactions to it, such as dropping unsafe-eval so the library survives strict Content Security Policies.
There is no signal in these entries about what comes next, and no publication in roughly two years; the honest read is that the release cadence has stopped rather than that a particular change is pending.
Other Meetings products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either BigBlueButton or PeerJS.
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Homer's storage churn pauses long enough to ship a catalog backup CLI.
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
See all BigBlueButton alternatives → · See all PeerJS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. BigBlueButton is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BigBlueButton is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top BigBlueButton alternatives in Meetings are ranked by recent ship velocity. Browse the "BigBlueButton alternatives" section above for the current picks, or visit /alternatives/bigbluebutton for the full list with editorial commentary on each.
Top PeerJS alternatives in Meetings are ranked by recent ship velocity. Browse the "PeerJS alternatives" section above for the current picks, or visit /alternatives/peerjs for the full list with editorial commentary on each.