OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Bloomreach and Craft CMS — release velocity, themes, recent moves, and the top alternatives to consider.
A fortnightly version train spending its releases on governance, compliance and Loomi accuracy
Bloomreach Engagement ships on a numbered version train, roughly one release per fortnight, each bundling a few platform changes with a standing mobile SDK update. The last five versions (1.308-1.312) cover a link-shortener pattern change, faster Performance dashboards, an approval workflow for scenarios, accuracy work across Loomi Analytics, and a message archive for compliance. Each release note is a short summary tied to an explicit release window rather than an itemised changelog.
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.
Bloomreach Engagement ships on a numbered version train, roughly one release per fortnight, each bundling a few platform changes with a standing mobile SDK update. The last five versions (1.308-1.312) cover a link-shortener pattern change, faster Performance dashboards, an approval workflow for scenarios, accuracy work across Loomi Analytics, and a message archive for compliance. Each release note is a short summary tied to an explicit release window rather than an itemised changelog.
The recent run is less about new surface area and more about making the existing platform safe to operate at scale: approvals gate campaign automation, the message archive answers compliance and support requests, and the Loomi work targets correctness of analyses and running aggregates rather than new analysis types. Mobile SDK updates appear in four of the five releases, which reads as a continuous maintenance obligation rather than a push. The cadence itself is the most consistent signal - versions land every two to three weeks with no visible major-version break.
Expect the train to continue at the same fortnightly cadence with further Loomi Analytics refinement and incremental mobile SDK work. Note the feed shows nothing after the 1.312 window closed on 29 June 2026, so whether that cadence held through July is not visible in these entries.
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.
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 Bloomreach or Craft CMS.
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 Bloomreach alternatives → · See all Craft CMS 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 is currently shipping more aggressively (velocity 6.3 vs 0.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. Craft CMS is currently shipping more aggressively (velocity 6.3 vs 0.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 Bloomreach alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Bloomreach alternatives" section above for the current picks, or visit /alternatives/bloomreach for the full list with editorial commentary on each.
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.