OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Craft CMS and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
Craft 6's alphas keep converting the plugin API, one removal at a time
Craft is running two lines with very different energy. The 5.10 maintenance branch ships one-bug releases hours apart and nothing else. Craft 6 is in its seventeenth alpha, still migrating onto Laravel: alpha 17 removes Plugin::settingsHtml() in favour of a settingsForm() built on the Control Panel Form system, replaces the Pane.vue component with a craft-pane web component, and moves another management command onto Laravel's schema API.
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 is running two lines with very different energy. The 5.10 maintenance branch ships one-bug releases hours apart and nothing else. Craft 6 is in its seventeenth alpha, still migrating onto Laravel: alpha 17 removes Plugin::settingsHtml() in favour of a settingsForm() built on the Control Panel Form system, replaces the Pane.vue component with a craft-pane web component, and moves another management command onto Laravel's schema API.
The pattern established at alpha 14 has not changed shape, only advanced: every alpha retires another Yii-era extension point and re-lands it on the new stack, with craftcms/yii2-adapter carrying the compatibility burden. Alpha 17 adds an Inertia-native slideout system that renders any CpScreenResponse as an in-page panel, which is the control panel moving from a legacy JavaScript layer to a genuinely Inertia/Vue one rather than wrapping it. The long fix list — stale permission trees, autosave firing on unchanged values, provisional drafts created on page open, queue jobs stuck reserved — reads as the cost of that churn being paid down alpha by alpha.
Expect further alphas that remove specific Yii-era plugin APIs with adapter fallbacks, and the 5.10 line to keep shipping single-fix patches until a Craft 6 beta absorbs the team's attention.
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.
OttoKit keeps widening its WordPress trigger surface one plugin at a time
Two security releases ship the same day, and 6.2 finally clears alpha
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 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.