OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Joomla and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
Two security releases ship the same day, and 6.2 finally clears alpha
Joomla is running three branches at once: 5.4.x as the maintenance line, 6.1.x as the current series, and 6.2.0 now in beta. On 18 August both maintenance branches shipped security releases hours apart — 5.4.8 with 32 merged PRs and 6.1.3 with four — each carrying the same 'install as soon as possible' banner. The release bodies remain download tables and SHA-256 checksums with the merged-PR list at the very end, so the actual change set is only readable from the tail.
Pushwoosh journeys can now read what a webhook says back and act on it mid-run.
The current release batch is broad but coherent. Journeys gained the ability to consume webhook response data and use returned values to personalize later steps in the same run. Messaging coverage evened out across channels, with PW_SMSSent and PW_WhatsAppSent events matching what email already emitted, and one-time WhatsApp sends no longer requiring a journey. On the web side, subscription forms can be dropped into any popup as lead capture, form field labels are editable without code, and the popup editor and targeting both got more room to work.
Joomla is running three branches at once: 5.4.x as the maintenance line, 6.1.x as the current series, and 6.2.0 now in beta. On 18 August both maintenance branches shipped security releases hours apart — 5.4.8 with 32 merged PRs and 6.1.3 with four — each carrying the same 'install as soon as possible' banner. The release bodies remain download tables and SHA-256 checksums with the merged-PR list at the very end, so the actual change set is only readable from the tail.
The paired-branch pattern that defined the last month has now completed a full cycle: rc1 on 11 August, rc2 on 15 August, finals on 18 August, both branches in lockstep. The fix content is defensive rather than additive — path-traversal checks in com_templates, an ACL check before exposing the user edit link, division-by-zero guards in ListModel and subforms, Smart Search memory limits. Meanwhile 6.2.0 moved from Alpha 3 to Beta 1 after four static weeks, pulling in 19 PRs that include a security flag for updates, secure article preview without frontend login, and a language fallback chain for the AI subsystem.
Expect 6.2.0 to run a second beta before a release candidate, and the 5.4.x/6.1.x pair to resume their coupled patch cadence with the next rc pair a few weeks out.
The current release batch is broad but coherent. Journeys gained the ability to consume webhook response data and use returned values to personalize later steps in the same run. Messaging coverage evened out across channels, with PW_SMSSent and PW_WhatsAppSent events matching what email already emitted, and one-time WhatsApp sends no longer requiring a journey. On the web side, subscription forms can be dropped into any popup as lead capture, form field labels are editable without code, and the popup editor and targeting both got more room to work.
Two things are being closed at once. The channel gap is narrowing — SMS and WhatsApp are being given the same event surface and standalone send path email has had, which makes them first-class for segmentation and triggering rather than journey-only endpoints. The bigger change is that journeys are becoming stateful against the outside world: a webhook step that can return a value into the run turns the journey builder from a sequencer into something closer to orchestration.
Now that webhook responses can feed a running journey, the natural extension is branching on those values and handling failure paths when the external call does not answer as expected. Expect the remaining email-only capabilities to keep arriving for SMS and WhatsApp until channel parity is complete.
Other Mkt Auto 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 Joomla or Pushwoosh.
OttoKit keeps widening its WordPress trigger surface one plugin at a time
Craft 6's alphas keep converting the plugin API, one removal at a time
Buttondown ships almost daily, and most of it is someone else's bug report closed.
Flodesk just moved its analytics out of the dashboard and into Claude and ChatGPT.
Formidable widens MCP compatibility and locks down signature files
Mailtrap is assembling a full email operations platform, one category step at a time
See all Joomla alternatives → · See all Pushwoosh alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Pushwoosh is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pushwoosh is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top Joomla alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Joomla alternatives" section above for the current picks, or visit /alternatives/joomla for the full list with editorial commentary on each.
Top Pushwoosh alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Pushwoosh alternatives" section above for the current picks, or visit /alternatives/pushwoosh for the full list with editorial commentary on each.