Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
go2rtc vs HOMER
A side-by-side editorial comparison of go2rtc and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
go2rtc vs HOMER: at a glance
What is go2rtc?
The universal camera translator keeps absorbing proprietary cloud protocols one vendor at a time.
go2rtc turns almost any camera into a stream any client can consume, and the last year of releases has been a steady march through vendor-specific cloud protocols: Tuya, then a full Xiaomi source including TUTK and cs2 transports, alongside SwitchBot, DoorBird, VIGI and UniFi Protect via ONVIF. Local capture also broadened with a V4L2 source down to MIPS builds. A dedicated security release added path allowlists and local auth to the api, exec and echo modules.
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.
go2rtc vs HOMER: editorial side-by-side
go2rtc
0.0MEETINGS
The universal camera translator keeps absorbing proprietary cloud protocols one vendor at a time.
◆ Current state
go2rtc turns almost any camera into a stream any client can consume, and the last year of releases has been a steady march through vendor-specific cloud protocols: Tuya, then a full Xiaomi source including TUTK and cs2 transports, alongside SwitchBot, DoorBird, VIGI and UniFi Protect via ONVIF. Local capture also broadened with a V4L2 source down to MIPS builds. A dedicated security release added path allowlists and local auth to the api, exec and echo modules.
◆ Where it's heading
Two expansions are running at once. Horizontally, each release reverse-engineers another walled-garden camera cloud, which is what makes go2rtc the layer Home Assistant and Frigate build on rather than a competitor to them. Vertically, the Wyoming module pushes past video into voice-assistant audio, which is a different category from streaming cameras. The security release is the counterweight — a project embedded that deeply in other people's stacks cannot keep shipping modules that execute arbitrary paths by configuration.
◆ Prediction
The Xiaomi rework was still landing device-specific fixes in the most recent release, so continued protocol and model coverage for that source is the likeliest next step. Whether Wyoming graduates from work-in-progress is the open question these notes leave.
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.
Alternatives to go2rtc 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 go2rtc or HOMER.
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
See all go2rtc alternatives → · See all HOMER alternatives →
Recent activity from go2rtc and HOMER
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
- 6mo agogo2rtcXiaomi source reworked with TUTK and cs2 transports
- 8mo agogo2rtcTuya and Xiaomi camera sources arrive; HomeKit QR code in the web UI
- 9mo agogo2rtcPath allowlists and local auth added to api, exec and echo modules
- 9mo agogo2rtcRTSP UDP transport, redirects, preload streams and secrets management
- 10mo agogo2rtcWyoming module extends go2rtc from cameras into voice audio ⚡
- 1y agogo2rtcV4L2 source adds direct local capture, down to MIPS builds
Frequently asked questions
What is the difference between go2rtc and HOMER?
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 go2rtc better than HOMER?
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 go2rtc?
Top go2rtc alternatives in Meetings are ranked by recent ship velocity. Browse the "go2rtc alternatives" section above for the current picks, or visit /alternatives/go2rtc 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.