Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
HOMER vs Jitsi
A side-by-side editorial comparison of HOMER and Jitsi — release velocity, themes, recent moves, and the top alternatives to consider.
HOMER vs Jitsi: 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 Jitsi?
Jitsi rebuilds its transcription stack and keeps investing in large-call performance.
Jitsi (Jitsi Meet plus its open-source backend) is an engineering-led project whose blog doubles as its changelog. Recent posts mix genuine infrastructure work, a rebuilt transcription architecture, receiver audio subscriptions, AV1 codec adoption, with community items like Google Summer of Code cohorts.
HOMER vs Jitsi: 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.
Jitsi
5.0MEETINGS
Jitsi rebuilds its transcription stack and keeps investing in large-call performance.
◆ Current state
Jitsi (Jitsi Meet plus its open-source backend) is an engineering-led project whose blog doubles as its changelog. Recent posts mix genuine infrastructure work, a rebuilt transcription architecture, receiver audio subscriptions, AV1 codec adoption, with community items like Google Summer of Code cohorts.
◆ Where it's heading
The technical arc is toward scaling and modernizing the media stack: selective audio subscriptions, SSRC rewriting, AV1, and now a from-scratch transcription architecture replacing the decade-old Jigasi approach. Jitsi is steadily shedding legacy components in favor of architecture that handles large calls and real-time features more efficiently.
◆ Prediction
The new transcription architecture likely lands broader real-time features (live captions, translation hooks) over the coming releases; expect continued media-pipeline optimization for large meetings.
Alternatives to HOMER and Jitsi
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 Jitsi.
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 Jitsi
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
- 1mo agoJitsiA new architecture for transcription (and more)
- 1mo agoJitsiGoogle Summer of Code 2026 – Meet This Year’s Projects!!
- 10mo agoJitsiIntroducing Receiver Audio Subscriptions
- 1y agoJitsiGSoC 2025, let’s do this!
- 1y agoJitsiAV1 and more … how does Jitsi Meet pick video codecs?
- 2y agoJitsiConnecting anything to everything via SIP
Frequently asked questions
What is the difference between HOMER and Jitsi?
They serve adjacent needs but don't currently overlap on shipped themes. HOMER and Jitsi are shipping at a similar cadence (velocity 5.0 vs 5.0, 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.
Is HOMER better than Jitsi?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HOMER and Jitsi are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 Jitsi?
Top Jitsi alternatives in Meetings are ranked by recent ship velocity. Browse the "Jitsi alternatives" section above for the current picks, or visit /alternatives/jitsi for the full list with editorial commentary on each.