Sulu
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
A side-by-side editorial comparison of Craft CMS and Pimcore — release velocity, themes, recent moves, and the top alternatives to consider.
Craft 6 is being rebuilt on Laravel in public, one alpha at a time
Craft CMS is running its 6.0 line through rapid alphas, and each one moves another subsystem onto Laravel. Blade views can now be loaded inside Twig templates with Craft registering Blade directives for near parity; asset I/O resolves through Laravel filesystem disks; queue jobs resolve dependencies through the service container; user elements implement Illuminate's HasLocalePreference. SQLite is now a supported database, login is rate limited, and accounts can connect to Socialite providers.
Nearly every release in this window carries security hardening — Pimcore is working through an injection sweep.
Pimcore maintains two calendar-versioned lines in parallel, 2026.2.x and 2026.1.x, with fixes landing on the newer line and selectively backported. The content is dominated by input-validation work: explicit field allowlists on Custom Report updates, an ORDER BY column allowlist for redirect listings, rejection of unwhitelisted filter properties, escaped field names in DataObject JOIN conditions, hardened unserialize paths, and CSV exports bound to the requesting user. Feature work is thin by comparison — a CDN integration and a TemplateProviderInterface extension point in 2026.2.1.
Craft CMS is running its 6.0 line through rapid alphas, and each one moves another subsystem onto Laravel. Blade views can now be loaded inside Twig templates with Craft registering Blade directives for near parity; asset I/O resolves through Laravel filesystem disks; queue jobs resolve dependencies through the service container; user elements implement Illuminate's HasLocalePreference. SQLite is now a supported database, login is rate limited, and accounts can connect to Socialite providers.
This is a framework transplant carried out in the open. The alphas move from templating and storage (alpha.10) through identity and asset handling (alpha.11, alpha.12) to session, queue and control-panel internals (alpha.13, alpha.14) — each step replacing a Yii-era mechanism with its Laravel equivalent. alpha.14 makes the cost explicit for the ecosystem: plugins must stop declaring extra.laravel.providers and lose automatic trait lifecycle hooks, while a new first-party control-panel component library (Button, ButtonGroup, Callout, Checkbox) arrives to replace ad-hoc markup.
Expect further alphas to continue converting Yii-era subsystems and to keep breaking the plugin contract until the component library and provider model settle; a beta is unlikely before plugin authors have a stable API to target.
Pimcore maintains two calendar-versioned lines in parallel, 2026.2.x and 2026.1.x, with fixes landing on the newer line and selectively backported. The content is dominated by input-validation work: explicit field allowlists on Custom Report updates, an ORDER BY column allowlist for redirect listings, rejection of unwhitelisted filter properties, escaped field names in DataObject JOIN conditions, hardened unserialize paths, and CSV exports bound to the requesting user. Feature work is thin by comparison — a CDN integration and a TemplateProviderInterface extension point in 2026.2.1.
The pattern is a systematic pass over places where user input reaches SQL or deserialization, spread across releases rather than bundled into one advisory — Custom Reports alone are touched in three separate releases. Alongside it runs a slower cleanup of the v11 era: admin functions removed, admin translations deprecated, v11-specific workflows refactored to v12. A task in the most recent release adds backward-compatibility break detection to the project's own code review tooling, which reads as an attempt to keep that cleanup from breaking integrators unannounced.
Expect the hardening sweep to keep producing small paired releases on both lines, with Custom Reports and listing filters the likely remaining targets, and further admin-layer removals as the v12 cleanup continues.
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.
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
The v4 canary line is being renamed Build Awesome while 3.x is kept on pure maintenance.
Steady feature-then-patch cadence, with security reports rising because AI tools are finding them
Measurement gets granular while the API quietly opens ClickFunnels up to outside agents
n8n's daily patch train hides the real work: hardening its MCP server into a proper auth resource.
OneSignal is arguing a new category into existence before showing the product behind it.
See all Craft CMS alternatives → · See all Pimcore 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 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.