Pimcore
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
A side-by-side editorial comparison of Mautic and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
Mautic is patching three supported branches at once while 7.2 grinds through release candidates.
The project maintains 5.2, 6.0, and 7.1 simultaneously, and it showed: one coordinated security release patched SQL injection, SSRF, and server-side template injection across all three branches on the same day. Since then the visible work has been a 7.1.3 bugfix rollup — campaign restart and infinite email-resend loops, GrapesJS builder regressions — and a 7.2 release candidate line now on its second RC, tagged in late July with no compiled release notes.
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.
The project maintains 5.2, 6.0, and 7.1 simultaneously, and it showed: one coordinated security release patched SQL injection, SSRF, and server-side template injection across all three branches on the same day. Since then the visible work has been a 7.1.3 bugfix rollup — campaign restart and infinite email-resend loops, GrapesJS builder regressions — and a 7.2 release candidate line now on its second RC, tagged in late July with no compiled release notes.
This is maintenance-shaped output from a community project carrying a wide support matrix. The 7.2 RC notes are dominated by dependency bumps, refactoring, and developer-experience work rather than new marketing automation capability, and the campaign engine keeps surfacing scheduling bugs that suggest that subsystem is where the complexity sits. A second RC without notes points to stabilisation rather than late feature additions.
Expect 7.2.0 to reach stable off the current RC line, and expect any further fixes to be backported across all three supported branches as the coordinated May security release was.
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 Mautic or Pushwoosh.
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
Three release lines running in parallel, all of them shipping nothing but fixes this week
OpnForm is turning its V2 platform into an automation surface, one integration at a time.
Zoho Social opens its management surface to AI assistants via MCP.
AWeber is moving the console out of the browser and into the chat window
Building an agent-drivable outreach stack — MCP, then OpenClaw, now an in-dashboard AI copilot.
See all Mautic 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 Mautic alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Mautic alternatives" section above for the current picks, or visit /alternatives/mautic 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.