Webex
The feed is a marketing blog; the actual GA announcements arrive between the thought leadership
A side-by-side editorial comparison of FreeSWITCH and Whereby — release velocity, themes, recent moves, and the top alternatives to consider.
With the legacy purge done, FreeSWITCH spent 1.11.2 bounds-checking everything that parses bytes
FreeSWITCH shipped 1.11.2 in August 2026, three months after the 1.11.0 branch cut that removed roughly thirty modules and migrated the regex engine to PCRE2. Where 1.11.0 was about deleting surface area, 1.11.2 is about auditing what remains: nearly every bug line is a bounds or length check in a parser — STUN attributes, base64 decode, XML entity decoding, RTMP H.264 NAL units, XML-RPC WebSocket frames, MSRP body lengths. Alongside the fixes it adds an interface allowlist and turns on DTLS client-certificate verification against the SDP fingerprint plus opt-in STUN MESSAGE-INTEGRITY checks on inbound ICE. The build system continues moving off self-hosted infrastructure onto GitHub-published artifacts and upstream packages.
Whereby ships monthly digests aimed squarely at the embedding developer, not the meeting host.
The feed is a run of monthly SDK and product round-ups, consistently framed around developer experience rather than end-user features. The specifics that do surface are embedding-side: session ratings for call quality feedback, session insights, stronger authentication options, and a native iOS SDK that left beta earlier in the year.
FreeSWITCH shipped 1.11.2 in August 2026, three months after the 1.11.0 branch cut that removed roughly thirty modules and migrated the regex engine to PCRE2. Where 1.11.0 was about deleting surface area, 1.11.2 is about auditing what remains: nearly every bug line is a bounds or length check in a parser — STUN attributes, base64 decode, XML entity decoding, RTMP H.264 NAL units, XML-RPC WebSocket frames, MSRP body lengths. Alongside the fixes it adds an interface allowlist and turns on DTLS client-certificate verification against the SDP fingerprint plus opt-in STUN MESSAGE-INTEGRITY checks on inbound ICE. The build system continues moving off self-hosted infrastructure onto GitHub-published artifacts and upstream packages.
The 1.11.x line reads as a deliberate two-step: cut the maintenance surface, then harden what is left. Having removed thirty modules, the project can now afford to audit the media and signaling paths line by line, and the pattern of fixes — untrusted length fields reaching memory writes — suggests a systematic pass rather than incremental reports. The parallel thread is dependency modernization: mod_v8 moved from a custom v8-6.1 fork to upstream libnode, SpanDSP and libvpx were bumped, and Windows builds now pull pre-compiled FFmpeg and libcodec2 rather than building them. Both threads point the same direction — less bespoke code to own.
Expect the hardening pass to continue into the remaining parsers, with the opt-in STUN MESSAGE-INTEGRITY check becoming default once operators have shipped through a release. The build-system migration off files.freeswitch.org appears partway done, so the next release likely finishes moving the remaining assets to GitHub-hosted artifacts.
The feed is a run of monthly SDK and product round-ups, consistently framed around developer experience rather than end-user features. The specifics that do surface are embedding-side: session ratings for call quality feedback, session insights, stronger authentication options, and a native iOS SDK that left beta earlier in the year.
Whereby is a video product sold to developers who embed it, and the cadence reflects that: incremental SDK work, quality telemetry and authentication rather than the in-meeting AI features that dominate the conferencing category. The digest format itself is the notable pattern, since it bundles a month of changes behind a generic headline and makes individual releases hard to assess from the feed alone.
Expect continued monthly SDK round-ups with quality and telemetry themes; the entries carry too little detail to predict a specific capability with confidence.
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 FreeSWITCH or Whereby.
The feed is a marketing blog; the actual GA announcements arrive between the thought leadership
HOMER 11's DuckLake rearchitecture is in its hardening phase, shipping near-daily.
mediasoup's Rust line is shipping subchannel fixes every few days and nothing else
One real release is buried in a feed that is mostly captured page furniture.
A daily drip of conference-platform polish, with finance filtering and attendee self-service leading.
Broadcast playout server reaches for HDR and sets a hardware floor to get there
See all FreeSWITCH alternatives → · See all Whereby alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. FreeSWITCH and Whereby are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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. FreeSWITCH and Whereby are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top FreeSWITCH alternatives in Meetings are ranked by recent ship velocity. Browse the "FreeSWITCH alternatives" section above for the current picks, or visit /alternatives/freeswitch for the full list with editorial commentary on each.
Top Whereby alternatives in Meetings are ranked by recent ship velocity. Browse the "Whereby alternatives" section above for the current picks, or visit /alternatives/whereby for the full list with editorial commentary on each.