Fourwaves
Fourwaves adds custom domain support for event websites, removing the hosted-subdomain constraint for conference organizers
Comparison · Meetings
Jitsi vs HOMER
A side-by-side editorial comparison of Jitsi and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:open-sourceobservability
Jitsi vs HOMER: at a glance
What is Jitsi?
Jitsi rearchitects transcription and adds Document PiP as GSoC 2026 projects ship
Jitsi is modernizing its core infrastructure through Google Summer of Code 2026 contributions: distributed tracing now spans backend components, transcription has been rearchitected after nearly a decade on the Jigasi-based system, and Document Picture-in-Picture is available in browser meetings. The product is absorbing substantive capability work through its open-source contributor pipeline rather than a dedicated product team.
What is HOMER?
HOMER patches a SQL injection in /exec and stabilizes Azure and DuckDB storage in 11.0.x
HOMER is an open-source VoIP call capture and observability platform running a rapid 11.0.x patch cadence. The 11.0.342 release closed a SQL injection vulnerability in the POST /exec endpoint by parameterizing the query, accompanied by security dependency bumps across hono, js-yaml, and gRPC. The storage layer has received parallel stability work: OTLP tables now participate in compaction and retention discovery, DuckDB temp directory configuration is pinned for tiering reliability, and Azure managed-identity orphan records are cleaned up.
Jitsi vs HOMER: editorial side-by-side
Jitsi
5.0MEETINGS
Jitsi rearchitects transcription and adds Document PiP as GSoC 2026 projects ship
◆ Current state
Jitsi is modernizing its core infrastructure through Google Summer of Code 2026 contributions: distributed tracing now spans backend components, transcription has been rearchitected after nearly a decade on the Jigasi-based system, and Document Picture-in-Picture is available in browser meetings. The product is absorbing substantive capability work through its open-source contributor pipeline rather than a dedicated product team.
◆ Where it's heading
The transcription rearchitecture and distributed tracing suggest Jitsi is investing in the backend foundations needed to scale or extend to new use cases — potentially AI-assisted meeting features that require more reliable speech input. Document PiP extends the multi-window collaboration surface. The GSoC model means capabilities arrive in bursts aligned with academic timelines.
◆ Prediction
AI transcription or summarization features are a likely application of the new transcription architecture, given the investment in rebuilding it from scratch and the AI-meeting category trend.
HOMER
5.0MEETINGS
HOMER patches a SQL injection in /exec and stabilizes Azure and DuckDB storage in 11.0.x
◆ Current state
HOMER is an open-source VoIP call capture and observability platform running a rapid 11.0.x patch cadence. The 11.0.342 release closed a SQL injection vulnerability in the POST /exec endpoint by parameterizing the query, accompanied by security dependency bumps across hono, js-yaml, and gRPC. The storage layer has received parallel stability work: OTLP tables now participate in compaction and retention discovery, DuckDB temp directory configuration is pinned for tiering reliability, and Azure managed-identity orphan records are cleaned up.
◆ Where it's heading
The Azure Blob Storage DuckLake backend added in 11.0.334 extends HOMER's tiering from S3-only to multi-cloud, and the subsequent Azure patches show that path is being actively maintained. The overall posture across this window is incremental hardening—security patching, dependency governance, and infrastructure reliability—rather than new user-facing features. The DuckLake integration (DuckDB + S3/Azure tiering) appears to be HOMER's infrastructure bet for handling high-volume VoIP capture at scale.
◆ Prediction
The next meaningful move is likely formal documentation and operator onboarding for the DuckLake multi-cloud storage tier; the backend is functionally in place for both S3 and Azure, and the stability patches suggest it is approaching production readiness.
Alternatives to Jitsi and HOMER
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 Jitsi or HOMER.
BigBlueButton
BigBlueButton 4.0 enters release candidate with LiveKit fully replacing the legacy audio stack.
JW Player
JW Player automates CMAF rendition ladders and sharpens ad attribution by player and placement
Nextcloud Talk Desktop
Nextcloud Talk Desktop is approaching Talk v25 stable while its July managed-config feature unlocks enterprise mass deployment for the first time.
Nextcloud Talk
Nextcloud Talk v25 adds classified conversations and an owner role, targeting regulated enterprise deployments.
Element Call
Element Call is removing its legacy architecture — the federated multi-SFU model is now the only option.
Recent activity from Jitsi and HOMER
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5h agoHOMER11.0.345
- 1d agoHOMER11.0.344
- 4d agoHOMER11.0.343
- 6d agoHOMER11.0.342
- 7d agoHOMER11.0.341
- 7d agoHOMER11.0.340
- 13d agoJitsiIntroducing Document PiP for browser meetings
- 27d agoJitsiTracing calls through backend components
- 2mo agoJitsiA new architecture for transcription (and more)
- 2mo agoJitsiGoogle Summer of Code 2026 – Meet This Year’s Projects!!
- 11mo agoJitsiIntroducing Receiver Audio Subscriptions
- 1y agoJitsiGSoC 2025, let’s do this!
Frequently asked questions
What is the difference between Jitsi and HOMER?
Both compete on the same themes — open-source, observability — within Meetings. Jitsi and HOMER 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 Jitsi better than HOMER?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Jitsi and HOMER 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 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.
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.