Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
HOMER vs PJSIP
A side-by-side editorial comparison of HOMER and PJSIP — release velocity, themes, recent moves, and the top alternatives to consider.
HOMER vs PJSIP: at a glance
What is HOMER?
Homer's storage churn pauses long enough to ship a catalog backup CLI.
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held and told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog and added hours as a retention unit. 11.0.323 is the first quiet release in the run — a QoS chart axis fix for dashboard timezones, plus the catalog backup and restore CLI that shipped untagged in 11.0.322. Around these sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, and two inline GHSA fixes hardening node /query auth.
What is PJSIP?
A mature SIP stack turns its attention to concurrency correctness and AI voice endpoints
PJSIP remains the reference open-source SIP and media stack for embedded and mobile softphones, shipping roughly one feature release a year. Version 2.17 pairs asynchronous client authentication with a documented real-time AI speech connectivity path, alongside ten separate deadlock fixes. The cadence is slow, but each drop carries a backward-incompatibility section integrators have to read before upgrading.
HOMER vs PJSIP: editorial side-by-side
HOMER
5.0MEETINGS
Homer's storage churn pauses long enough to ship a catalog backup CLI.
◆ Current state
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held and told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog and added hours as a retention unit. 11.0.323 is the first quiet release in the run — a QoS chart axis fix for dashboard timezones, plus the catalog backup and restore CLI that shipped untagged in 11.0.322. Around these sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, and two inline GHSA fixes hardening node /query auth.
◆ Where it's heading
Homer is stabilizing a storage rewrite by moving work out of DuckDB rather than tuning it further — native compaction merges in Go, outside DuckDB's memory_limit, and lets DuckLake alone allocate snapshot and file IDs, the exact behavior that corrupted catalogs before. A backup and restore path for the catalog is the logical next admission that the catalog is the thing most likely to break, and shipping it inside another release rather than tagging it separately fits a project releasing several times a week. Defaults stay conservative while each escape hatch is proven.
◆ Prediction
If native compaction holds up in the field, expect it to become the default engine and the DuckDB compaction path to be deprecated; the near-term releases will likely keep closing memory and catalog-locking edges around it.
PJSIP
0.0MEETINGS
A mature SIP stack turns its attention to concurrency correctness and AI voice endpoints
◆ Current state
PJSIP remains the reference open-source SIP and media stack for embedded and mobile softphones, shipping roughly one feature release a year. Version 2.17 pairs asynchronous client authentication with a documented real-time AI speech connectivity path, alongside ten separate deadlock fixes. The cadence is slow, but each drop carries a backward-incompatibility section integrators have to read before upgrading.
◆ Where it's heading
The arc from 2.14 to 2.17 moves away from platform and codec breadth — IPv6 dual stack, a Metal renderer, Lyra, a Schannel TLS backend — and toward the harder problem of concurrency inside the media core: async conference bridge operations, then parallel bridging, then async authentication and systematic deadlock elimination. AI speech connectivity in 2.17 is the first indication the project treats voice agents, not only human callers, as a target workload. The growing list of API breaks suggests the maintainers will trade source compatibility for cleaner threading semantics.
◆ Prediction
Expect the next release to widen the AI speech path with more transport and codec options while continuing to convert blocking media-core calls to asynchronous ones.
Alternatives to HOMER and PJSIP
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 PJSIP.
mediasoup
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
Mux
Every manual control Mux ships now arrives with a Robots workflow that does it for you
Recent activity from HOMER and PJSIP
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3h agoHOMERCatalog backup/restore CLI ships; QoS axes follow dashboard timezone
- 1d agoHOMERNative compaction made safe for live catalogs; retention in hours
- 2d agoHOMERCompaction merge bounded after silent OOM kills on live catalogs
- 4d agoHOMERAlerts store the firing query and replay it in search
- 5d agoHOMERDuckDB memory caps raised so high ingest stops killing the engine
- 5d agoHOMERPer-user dashboard IDs unblock multi-user installs
- 3mo agoPJSIPPJSIP 2.17 adds async SIP auth and AI speech connectivity ⚡
- 8mo agoPJSIPPJSIP 2.16 brings real-time text and a parallel conference bridge
- 1y agoPJSIPPJSIP 2.15 adds Metal rendering, Schannel TLS and the Lyra codec
- 1y agoPJSIPPJSIP 2.15.1 fixes auth and async conference bridge bugs
- 2y agoPJSIPPJSIP 2.14.1 fixes an ICE deadlock and re-INVITE handling
- 2y agoPJSIPPJSIP 2.14 adds dual-stack IPv6 and mobile sample apps
Frequently asked questions
What is the difference between HOMER and PJSIP?
They serve adjacent needs but don't currently overlap on shipped themes. HOMER is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 PJSIP?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HOMER is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 PJSIP?
Top PJSIP alternatives in Meetings are ranked by recent ship velocity. Browse the "PJSIP alternatives" section above for the current picks, or visit /alternatives/pjsip for the full list with editorial commentary on each.