← Back to home
Comparison · Meetings

Element Call vs Fourwaves

A side-by-side editorial comparison of Element Call and Fourwaves — release velocity, themes, recent moves, and the top alternatives to consider.

Element Call vs Fourwaves: at a glance

FeatureElement CallFourwaves
SectorMeetingsMeetings
Velocity score5.05.0
Sparks · 30d00
Top themesmatrix, webrtc, sfu, federationconference-management, payments, multi-event-admin, attendee-experience
Last editorial update6d ago1h ago
WebsiteVisit →Visit →

What is Element Call?

Element Call now routes every participant through their own homeserver's SFU.

Element Call publishes release candidates rather than finals, and is at v0.24.0-rc.1. The structural change in this window landed in v0.21.0-rc.1, which made multi-SFU the default: each participant connects to the media server associated with their own homeserver, and subscribes read-only to streams on others. Since then the work has been media quality controls, mobile layout for voice and group calls, and a breaking removal of .well-known transport discovery.

Read the full Element Call trajectory →

What is Fourwaves?

Fourwaves is closing the gaps around its payments layer and its form editor at the same time.

Fourwaves publishes a near-daily, one-line changelog covering small changes to the conference organiser's admin surface. The August window is dominated by payments and money administration: transaction filtering by organisation and by payment gateway, the Free plan surfaced in the upgrade checkout, and Authorize.net added as a supported processor. The two newest entries move elsewhere — self-service account creation from the sign-in page, and a guard that blocks deleting fields, sections, or choices still referenced elsewhere in an event, with a warning naming what depends on them.

Read the full Fourwaves trajectory →

Element Call vs Fourwaves: editorial side-by-side

E
Element Call
MEETINGS
5.0

Element Call now routes every participant through their own homeserver's SFU.

◆ Current state

Element Call publishes release candidates rather than finals, and is at v0.24.0-rc.1. The structural change in this window landed in v0.21.0-rc.1, which made multi-SFU the default: each participant connects to the media server associated with their own homeserver, and subscribes read-only to streams on others. Since then the work has been media quality controls, mobile layout for voice and group calls, and a breaking removal of .well-known transport discovery.

◆ Where it's heading

The arc is toward removing negotiation and configuration from the connection path. Multi-SFU removed the argument over which server hosts a call; dropping .well-known transport discovery and the default server config removes guesses that were usually wrong. Alongside that, a steady mobile and widget-embedding thread continues, with React Compiler and spotlight re-render work aimed at the performance cost of running in someone else's app.

◆ Prediction

With multi-SFU now the default and legacy single-SFU still reachable through developer settings, the likely next step is retiring that legacy path rather than adding another connection mode.

F
Fourwaves
MEETINGS
5.0

Fourwaves is closing the gaps around its payments layer and its form editor at the same time.

◆ Current state

Fourwaves publishes a near-daily, one-line changelog covering small changes to the conference organiser's admin surface. The August window is dominated by payments and money administration: transaction filtering by organisation and by payment gateway, the Free plan surfaced in the upgrade checkout, and Authorize.net added as a supported processor. The two newest entries move elsewhere — self-service account creation from the sign-in page, and a guard that blocks deleting fields, sections, or choices still referenced elsewhere in an event, with a warning naming what depends on them.

◆ Where it's heading

The work is aimed at multi-event organisations rather than single-conference organisers; transaction filtering and a second payment processor only matter if you run several events through shared gateways. The referential-integrity guard on form fields points at the same maturity problem from the other side — events configured deeply enough that deleting a field silently breaks something downstream, which is a complaint you only get once customers build complex forms. Individually each change is minor; together they describe a platform being made to hold more events per customer.

◆ Prediction

Expect the payments thread to continue — further gateway options or per-organisation payment configuration are the natural next step now that transactions can be filtered by gateway. The date-stamped daily format suggests the cadence holds regardless of the size of what ships.

Alternatives to Element Call and Fourwaves

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 Element Call or Fourwaves.

See all Element Call alternatives → · See all Fourwaves alternatives →

Recent activity from Element Call and Fourwaves

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoFourwavesSelf-service account creation from the sign-in page
  2. 2d agoFourwavesReferenced form fields can no longer be deleted
  3. 6d agoFourwavesAuthorize.net added as a payment processor
  4. 7d agoFourwavesFree plan shown as a card in upgrade checkout
  5. 7d agoElement CallMedia quality settings UI; .well-known transport discovery removed
  6. 8d agoFourwavesTracks field usable as a confirmation-email variable
  7. 9d agoFourwavesFix: Website section shown to program chairs
  8. 21d agoElement CallLandscape mobile call layout fixes
  9. 1mo agoElement CallDefault gradient background and reworked mobile call design
  10. 1mo agoElement CallMulti-SFU becomes the default call topology
  11. 2mo agoElement Callmatrix_rtc_mode config option and typed connection errors
  12. 2mo agoElement CallBug fixes, older WebView polyfill and dependency bumps

Frequently asked questions

What is the difference between Element Call and Fourwaves?

They serve adjacent needs but don't currently overlap on shipped themes. Element Call and Fourwaves 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 Element Call better than Fourwaves?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Element Call and Fourwaves 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 Element Call?

Top Element Call alternatives in Meetings are ranked by recent ship velocity. Browse the "Element Call alternatives" section above for the current picks, or visit /alternatives/element-call for the full list with editorial commentary on each.

What are the best alternatives to Fourwaves?

Top Fourwaves alternatives in Meetings are ranked by recent ship velocity. Browse the "Fourwaves alternatives" section above for the current picks, or visit /alternatives/fourwaves for the full list with editorial commentary on each.