Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
Google Meet vs HOMER
A side-by-side editorial comparison of Google Meet and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
Google Meet vs HOMER: at a glance
What is Google Meet?
Meet is bolting consent controls onto the AI features it spent the last year adding.
The recent stream splits between AI meeting assistance and conventional conferencing work. Administrators can now require explicit participant consent before note-taking, recording or transcription begins, while 'Take notes for me' gains detail-level customization and a reworked Decisions section.
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.
Google Meet vs HOMER: editorial side-by-side
Google Meet
0.0MEETINGSCOMMS
Meet is bolting consent controls onto the AI features it spent the last year adding.
◆ Current state
The recent stream splits between AI meeting assistance and conventional conferencing work. Administrators can now require explicit participant consent before note-taking, recording or transcription begins, while 'Take notes for me' gains detail-level customization and a reworked Decisions section.
◆ Where it's heading
Google is filling in the governance and reach gaps around features already shipped rather than announcing new ones. Consent enforcement, speech translation reaching mobile, higher-resolution video and certified BYOD switchers all extend the usefulness of capabilities that already exist.
◆ Prediction
Expect the consent controls to become more granular per artifact type and eventually default on, following the pattern of admin controls that ship off and tighten later.
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 Google Meet 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 Google Meet 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 Google Meet alternatives → · See all HOMER alternatives →
Recent activity from Google Meet 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
- 3mo agoGoogle MeetRequire explicit consent for Take Notes with Gemini, recordings, and transcripts in Google Meet
- 3mo agoGoogle MeetNew ways to customize AI-generated meeting notes
- 4mo agoGoogle MeetImproved video quality on high-resolution displays in Google Meet
- 4mo agoGoogle MeetAdditional BYOD peripheral switchers certified for Google Meet in ChromeOS touch controller rooms
- 4mo agoGoogle MeetSpeech translation in Google Meet is now rolling out to mobile devices
- 4mo agoGoogle MeetGoogle Meet is now available on CarPlay
Frequently asked questions
What is the difference between Google Meet 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 Google Meet 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 Google Meet?
Top Google Meet alternatives in Meetings are ranked by recent ship velocity. Browse the "Google Meet alternatives" section above for the current picks, or visit /alternatives/google-meet 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.