Switcher Studio
Switcher Studio's tracked feed is search-driven streaming education, not product news.
Comparison · Meetings
HOMER vs FreeSWITCH
A side-by-side editorial comparison of HOMER and FreeSWITCH — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:security-hardening
HOMER vs FreeSWITCH: at a glance
What is HOMER?
Three security advisories in three days as HOMER locks down the query layer it just opened up.
HOMER ships multiple patch releases per day against a single 11.0.x line, and the work is overwhelmingly corrective rather than additive. Two long-running threads dominate: unifying HEP capture identity (node_id, node_name, "Capture ID") across the results table, filters and Prometheus labels, and keeping DuckDB/DuckLake storage honest. In the first week of August a third thread took over — three separate GHSA advisories closed in 11.0.309, and 11.0.313.
What is FreeSWITCH?
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.
HOMER vs FreeSWITCH: editorial side-by-side
HOMER
5.0MEETINGS
Three security advisories in three days as HOMER locks down the query layer it just opened up.
◆ Current state
HOMER ships multiple patch releases per day against a single 11.0.x line, and the work is overwhelmingly corrective rather than additive. Two long-running threads dominate: unifying HEP capture identity (node_id, node_name, "Capture ID") across the results table, filters and Prometheus labels, and keeping DuckDB/DuckLake storage honest. In the first week of August a third thread took over — three separate GHSA advisories closed in 11.0.309, and 11.0.313.
◆ Where it's heading
The security run is not incidental: each advisory lands on surface area the project recently added. The node query endpoint and DuckDB's external scanners are exactly the pieces that make HOMER queryable beyond its own UI, and they are now being fenced with token auth and a stricter SQL validator. Expect the identity-unification work to keep filling patch releases while the query layer hardens around it, since both are prerequisites for anyone building on captured data rather than just reading it.
◆ Prediction
The next releases likely continue tightening ValidateRawSQL and the node auth path, since two of the three August advisories came from that one surface. Whether the MCP natural-language parser seen in 11.0.308 grows past instrumentation is not yet visible in these entries.
FreeSWITCH
2.5MEETINGS
With the legacy purge done, FreeSWITCH spent 1.11.2 bounds-checking everything that parses bytes
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to HOMER and FreeSWITCH
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 HOMER or FreeSWITCH.
Asterisk
Four parallel branches, one fix set — Asterisk's changelog is a backport ledger, not a feature list.
3CX
3CX is bolting AI onto the PBX and rewriting its licensing to match
CallHippo
CallHippo is arguing that compliance, not features, is what sells business calling.
Intermedia
A UCaaS marketing blog split between buyer education and channel-partner enablement.
Restream
Restream is pushing past creator multistreaming into webinars and agent control.
See all HOMER alternatives → · See all FreeSWITCH alternatives →
Recent activity from HOMER and FreeSWITCH
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 16h agoFreeSWITCHInterface allowlist lands with a broad memory-safety sweep
- 1d agoHOMERNode query API gains token auth; DuckDB external scanners blocked
- 3d agoHOMERHEP node names reach search, results and Prometheus labels
- 3d agoHOMERDuckDB reconnects on catalog refresh
- 3d agoHOMERAdmin-role self-escalation blocked in the users API
- 3d agoHOMERCall flow consolidates messages by Capture ID
- 4d agoHOMERResults columns relabel node_id as Capture ID
- 2mo agoFreeSWITCHHot TLS certificate reloads and SIP 603 passthrough
- 3mo agoFreeSWITCHPCRE2, OpenSSL 3 on Windows, and thirty legacy modules removed ⚡
- 2y agoFreeSWITCHARM64 support arrives, Debian 10 and CentOS dropped
- 2y agoFreeSWITCHCoverity fixes and a sofia-sip version bump
- 2y agoFreeSWITCHDebian 12, OpenSSL 3 and FFmpeg 5 support
Frequently asked questions
What is the difference between HOMER and FreeSWITCH?
Both compete on the same themes — security-hardening — within Meetings. HOMER is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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.
Is HOMER better than FreeSWITCH?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HOMER is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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.
What are the best alternatives to HOMER?
Top HOMER alternatives in Meetings are ranked by recent ship velocity. Browse the "HOMER alternatives" section above for the current picks, or visit /alternatives/homer-voip for the full list with editorial commentary on each.
What are the best alternatives to FreeSWITCH?
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.