OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Craft CMS and n8n — 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.
Four release trains running at once, and the top of the feed is all patch traffic.
n8n maintains at least four concurrent lines - 2.35, 2.34, 2.33 and the 1.123 LTS - and publishes each patch as its own changelog entry, so the visible top of the feed is dominated by single-fix releases and their backports. The substantive work in this window sits in 2.35.0, which carried the agent builder test runs, HITL in those test runs, Discord as an agent channel, MCP registry search exposed to the assistant, and instance-ai enabled by default. Everything published since has been correctness work on that foundation.
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.
n8n maintains at least four concurrent lines - 2.35, 2.34, 2.33 and the 1.123 LTS - and publishes each patch as its own changelog entry, so the visible top of the feed is dominated by single-fix releases and their backports. The substantive work in this window sits in 2.35.0, which carried the agent builder test runs, HITL in those test runs, Discord as an agent channel, MCP registry search exposed to the assistant, and instance-ai enabled by default. Everything published since has been correctness work on that foundation.
The pattern is stable and predictable: a minor release lands the agent and MCP feature batch, then a week of patches hardens it across every supported line. The fixes themselves show where the agent surface is still settling - tool result bounds, resume payload handling, credential scope detection, expression isolates - which is the ordinary cost of having made Instance AI a default rather than an opt-in. Node maintenance runs underneath it all, with the Google Ads v21-to-v25 migration shipped simultaneously on two trains.
The next 2.35 patches will keep absorbing agent-builder and MCP edge cases, and the following minor is the one to watch for the next feature batch; the parallel backporting to 2.34 and the 1.123 LTS will continue unchanged.
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 n8n.
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 n8n 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 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 n8n alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "n8n alternatives" section above for the current picks, or visit /alternatives/n8n for the full list with editorial commentary on each.