Ghost
Ghost is quietly turning its newsletter into a lifecycle marketing engine.
A side-by-side editorial comparison of AcyMailing and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
AcyMailing spent its 11.0 cycle on privacy plumbing and a security rewrite, not features.
AcyMailing crossed into 11.0 at the end of July, and the release carried a reworked codebase aimed at security plus a GDPR-driven option for handling pixel tracking. The two follow-up patches since have been almost entirely corrective — automations display, followup creation, multilingual campaigns, and restoring the pot file that custom translations depend on. The 10.11 line before it patched an SQL injection and added toggles for IP collection and a statistics recording delay.
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.
AcyMailing crossed into 11.0 at the end of July, and the release carried a reworked codebase aimed at security plus a GDPR-driven option for handling pixel tracking. The two follow-up patches since have been almost entirely corrective — automations display, followup creation, multilingual campaigns, and restoring the pot file that custom translations depend on. The 10.11 line before it patched an SQL injection and added toggles for IP collection and a statistics recording delay.
This is a mature self-hosted mailer working through compliance and hardening rather than chasing capability. The consistent thread across both version lines is giving administrators switches for data they previously collected by default — open-tracking pixels, IP addresses on subscription, statistics timing. The rapid 11.0.1 and 11.0.2 patches suggest the codebase rework shook loose regressions the major release did not catch.
Expect the 11.0.x patch stream to continue for a few more releases as rework regressions surface, before any new functionality appears. The entries give no signal about what the next feature cycle targets.
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 AcyMailing or Pushwoosh.
Ghost is quietly turning its newsletter into a lifecycle marketing engine.
Pimcore is spending 2026 hardening its data layer, one allowlist at a time.
MailBeez hardens its big 'V5' rewrite with PHP 8.x compatibility and up-to-10x page-load gains.
Two n8n release trains running in lockstep, both carrying only bug fixes this week.
OneSignal is arguing marketers should stop building journeys, and shipping agents to prove it
A near-daily fix stream, with flexible monthly RSS scheduling the only real addition.
See all AcyMailing 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 AcyMailing alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "AcyMailing alternatives" section above for the current picks, or visit /alternatives/acymailing 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.