Pimcore
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
A side-by-side editorial comparison of Craft CMS and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
Craft 6 is being rebuilt on Laravel, and the alphas are breaking plugins to get there.
Craft runs two trains at once: a 6.0.0 alpha series rearchitecting the CMS, and 5.10.x patches that are single-bug fixes shipped within hours of each other. The alphas carry the work — queue jobs and dependency resolution moved onto Laravel's service container, control-panel serialization switched to Illuminate helpers, the imagine image library replaced with intervention/image, and a first-party control-panel component library added. Alpha 14 shipped with an explicit breaking-changes notice for plugin authors.
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.
Craft runs two trains at once: a 6.0.0 alpha series rearchitecting the CMS, and 5.10.x patches that are single-bug fixes shipped within hours of each other. The alphas carry the work — queue jobs and dependency resolution moved onto Laravel's service container, control-panel serialization switched to Illuminate helpers, the imagine image library replaced with intervention/image, and a first-party control-panel component library added. Alpha 14 shipped with an explicit breaking-changes notice for plugin authors.
The direction is a Laravel-native Craft: Artisan command discovery, container-resolved queue jobs, Illuminate helpers, and plugins that no longer register through composer extra fields or automatic trait lifecycle hooks. The image pipeline swap brings libvips and formats like HEIC, JPEG XL and TIFF along with it. Meanwhile 5.10 receives nothing but same-day bug fixes, which is what a maintenance branch looks like once the team's attention has moved.
Expect further alphas to keep narrowing the plugin API surface ahead of a beta, with the 5.10 line continuing at one or two same-day patch releases a week.
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 Craft CMS 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 Craft CMS 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. Craft CMS and Pushwoosh are shipping at a similar cadence (velocity 6.3 vs 6.3, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Craft CMS and Pushwoosh are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top Craft CMS alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Craft CMS alternatives" section above for the current picks, or visit /alternatives/craft-cms 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.