Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
HOMER vs Pexip
A side-by-side editorial comparison of HOMER and Pexip — release velocity, themes, recent moves, and the top alternatives to consider.
HOMER vs Pexip: 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 Pexip?
Pexip Infinity v40 lands as a maintenance-grade release.
The recent feed is dominated by the Pexip Infinity v40 release notes — upgrade procedure, changelog, resolved issues, known limitations — alongside the prior v39.1 release. The v40 release itself notes 'no significant changes' in functionality, suggesting this is a stability/security cut rather than a feature push.
HOMER vs Pexip: 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.
Pexip
5.0MEETINGS
Pexip Infinity v40 lands as a maintenance-grade release.
◆ Current state
The recent feed is dominated by the Pexip Infinity v40 release notes — upgrade procedure, changelog, resolved issues, known limitations — alongside the prior v39.1 release. The v40 release itself notes 'no significant changes' in functionality, suggesting this is a stability/security cut rather than a feature push.
◆ Where it's heading
Pexip is operating in classic enterprise-on-prem mode: regular versioned releases with multi-step upgrade paths, security bulletins, and detailed end-of-life announcements. There is no visible AI or cloud-native pivot in the current notes. The product is being maintained for the install base it already has, not reshaped for a new buyer.
◆ Prediction
Expect a v40.x point release within 4–6 weeks addressing v40 known limitations, and continued biannual major versions. The next directional signal would be either an AI-meeting feature inside the web app or a cloud-managed deployment option — neither is hinted at in this batch.
Alternatives to HOMER and Pexip
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 Pexip.
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 Pexip
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 agoPexipPexip Infinity v40 upgrade guide published
- 4mo agoPexipv40 ships with no significant functional changes
- 4mo agoPexipInstallation guide updated for v40
- 4mo agoPexipResolved issues in v40
- 4mo agoPexipv40 known limitations published
- 4mo agoPexipPexip Infinity v39.1 release notes
Frequently asked questions
What is the difference between HOMER and Pexip?
They serve adjacent needs but don't currently overlap on shipped themes. HOMER and Pexip 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 Pexip?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HOMER and Pexip 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 Pexip?
Top Pexip alternatives in Meetings are ranked by recent ship velocity. Browse the "Pexip alternatives" section above for the current picks, or visit /alternatives/pexip for the full list with editorial commentary on each.