Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
HOMER vs Lark
A side-by-side editorial comparison of HOMER and Lark — release velocity, themes, recent moves, and the top alternatives to consider.
HOMER vs Lark: 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 Lark?
Lark concentrates monthly updates on Base — automation branching, mobile dashboards, layout reset — while the collaboration suite holds steady.
Lark's monthly update cadence is centered on Lark Base, the suite's no-code data tool. V7.65 adds advanced formatting and branch settings to Base automations; V7.64 makes dashboard charts interactive on the mobile app; V7.62 ships one-click reset for custom Base record detail page layouts; V7.63 introduces AHA PC Doctor as an in-app self-service troubleshooter. V7.60 polishes image highlights in comments and V7.59 expands message-sending options in Base automated workflows.
HOMER vs Lark: 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.
Lark
0.0MEETINGS
Lark concentrates monthly updates on Base — automation branching, mobile dashboards, layout reset — while the collaboration suite holds steady.
◆ Current state
Lark's monthly update cadence is centered on Lark Base, the suite's no-code data tool. V7.65 adds advanced formatting and branch settings to Base automations; V7.64 makes dashboard charts interactive on the mobile app; V7.62 ships one-click reset for custom Base record detail page layouts; V7.63 introduces AHA PC Doctor as an in-app self-service troubleshooter. V7.60 polishes image highlights in comments and V7.59 expands message-sending options in Base automated workflows.
◆ Where it's heading
Lark is investing heavily in Base's automation depth and admin ergonomics — branch settings, granular automation triggers, mobile-first dashboard interaction, layout management. Earlier versions in the index (V7.51 AI in Base, V7.55 new workspaces, V7.58 condition-group permissions) confirm Base as the consistent center of feature work. The broader collaboration suite (chat, docs, calendar) is held steady while Base evolves.
◆ Prediction
Expect more agentic AI inside Base (extending the V7.51 thread), continued mobile parity with desktop dashboards, and deeper automation features — multi-step branching with conditions, more third-party connectors. Self-service support (PC Doctor) is likely to expand to mobile and Mac.
Alternatives to HOMER and Lark
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 Lark.
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 Lark
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
- 4mo agoLark• V7.65 More advanced formatting and branch settings for Base automations!
- 4mo agoLark• V7.64 Interact with dashboard charts on the mobile app!
- 5mo agoLark• V7.62 Reset layout for custom Base record details pages in one click
- 5mo agoLark• V7.63 AHA PC Doctor is now available to help you resolve common issues easily!
- 6mo agoLark• V7.60 Eliminate confusion with image highlights in comments!
- 7mo agoLark• V7.59 More advanced options for sending messages using automated workflows in Base
Frequently asked questions
What is the difference between HOMER and Lark?
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 Lark?
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 Lark?
Top Lark alternatives in Meetings are ranked by recent ship velocity. Browse the "Lark alternatives" section above for the current picks, or visit /alternatives/lark for the full list with editorial commentary on each.