OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Craft CMS and Pimcore — 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.
Pimcore is shipping a security advisory almost every week.
Pimcore releases on a weekly-to-fortnightly patch cadence across two supported lines - 2026.2.x and the older 12.3.x - and the defining feature of the last two months is the volume of security work. Nearly every release carries at least one GHSA: WebDAV rename permissions, ImageGallery hotspot unserialize, Classificationstore field-name validation, blind SSRF via email test-send, Custom Report field allowlisting. Around it sits ordinary bug fixing in workflows, thumbnails, and data object handling.
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.
Pimcore releases on a weekly-to-fortnightly patch cadence across two supported lines - 2026.2.x and the older 12.3.x - and the defining feature of the last two months is the volume of security work. Nearly every release carries at least one GHSA: WebDAV rename permissions, ImageGallery hotspot unserialize, Classificationstore field-name validation, blind SSRF via email test-send, Custom Report field allowlisting. Around it sits ordinary bug fixing in workflows, thumbnails, and data object handling.
The advisories are not scattered; they cluster on the surfaces where Pimcore accepts structured input from an authenticated user - custom reports, classification stores, WebDAV, grid configuration. The fixes follow a consistent method of allowlisting fields, enforcing permissions at the operation rather than the screen, and refusing to echo raw database errors. Read together, this is a deliberate audit of the admin surface rather than a run of unrelated reports, and it is being done in public one patch at a time.
The audit pattern points at the remaining input-accepting admin surfaces - imports, grid and filter parsers, WebDAV operations beyond MOVE - so expect more advisories of the same shape before the cadence slows.
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 Pimcore.
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 Pimcore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — cms — within Mkt Auto. Craft CMS 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. Craft CMS 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 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 Pimcore alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Pimcore alternatives" section above for the current picks, or visit /alternatives/pimcore for the full list with editorial commentary on each.