Fourwaves vs Hyprnote

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.

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.

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.