Pimcore
Nearly every release in this window carries security hardening — Pimcore is working through an injection sweep.
A side-by-side editorial comparison of Sulu and Eleventy — release velocity, themes, recent moves, and the top alternatives to consider.
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
Sulu is a Symfony-based CMS for developer-built sites, and its release process is a synchronised pair: every 3.0.x patch ships within a minute of the matching 2.6.x patch, carrying largely the same pull requests. Six releases in five months — 3.0.8/2.6.25, 3.0.7/2.6.24, 3.0.6/2.6.23 — are almost entirely fixes, editor upgrades and framework compatibility work. A security advisory was patched across both branches in March.
The v4 canary line is being renamed Build Awesome while 3.x is kept on pure maintenance.
Two lines run in parallel. The 3.x branch gets dependency-only releases — 3.1.5 and 3.1.6 explicitly ship no core code changes, after 3.1.3 and 3.1.4 failed to publish and were left as immutable dead tags. The v4 alpha train, meanwhile, is where the work is: Node minimum raised to 22.15, page.inputPathDir and page.dir removed, batched incremental builds added, and a large refactor of the Nunjucks fork onto a fully-async prerelease. The releases themselves now carry the Build Awesome name and offer an @awesome.me/buildawesome install alongside @11ty/eleventy@canary.
Sulu is a Symfony-based CMS for developer-built sites, and its release process is a synchronised pair: every 3.0.x patch ships within a minute of the matching 2.6.x patch, carrying largely the same pull requests. Six releases in five months — 3.0.8/2.6.25, 3.0.7/2.6.24, 3.0.6/2.6.23 — are almost entirely fixes, editor upgrades and framework compatibility work. A security advisory was patched across both branches in March.
Three threads run through the pairs. Editor upkeep is constant, with CKEditor moving to 47 LTS and then 48 and the fallout — table widgets, webpack font builds — fixed release by release. Framework compatibility is the second: Request->get calls replaced for Symfony 8, PHPUnit 13 and PHPStan kept green on lowest dependencies. The third and most interesting is data-model cleanup on the 3.0 side, where tags migrated from names to IDs behind a newly added DoctrineMigrationsBundle, with smart-content filters reworked to match. What is not visible is any capability that exists on 3.0 and not on 2.6 — a major version that is not yet behaving like one.
Expect the paired-release rhythm to continue with more Symfony 8 preparation and CKEditor 48 fallout. The open question is when 3.0 starts receiving work that is not upmerged from 2.6; until then the major version number is not buying users anything.
Two lines run in parallel. The 3.x branch gets dependency-only releases — 3.1.5 and 3.1.6 explicitly ship no core code changes, after 3.1.3 and 3.1.4 failed to publish and were left as immutable dead tags. The v4 alpha train, meanwhile, is where the work is: Node minimum raised to 22.15, page.inputPathDir and page.dir removed, batched incremental builds added, and a large refactor of the Nunjucks fork onto a fully-async prerelease. The releases themselves now carry the Build Awesome name and offer an @awesome.me/buildawesome install alongside @11ty/eleventy@canary.
v4 is accumulating breaking changes faster than it is stabilizing — three of the entries in this window announce removals or minimum-version bumps, and alpha.10 exists only to hotfix a regression alpha.9 introduced. The Nunjucks refactor is the biggest bet: making the fork fully async removes the need for async-specific template tags, but the release notes flag it as risky for existing Nunjucks users. The naming change is proceeding on the same timeline, so users tracking canary are absorbing an identity shift and an API shift at once.
Expect more v4 alphas carrying breaking removals before any beta, with the Nunjucks async refactor generating follow-up regressions; 3.x looks likely to keep receiving dependency-only patches with no core changes.
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 Sulu or Eleventy.
Nearly every release in this window carries security hardening — Pimcore is working through an injection sweep.
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.
Kit rebuilt its landing page editor, then handed the controls to an AI agent.
See all Sulu alternatives → · See all Eleventy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Sulu and Eleventy are shipping at a similar cadence (velocity 5.0 vs 5.0, 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. Sulu and Eleventy are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top Sulu alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Sulu alternatives" section above for the current picks, or visit /alternatives/sulu for the full list with editorial commentary on each.
Top Eleventy alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Eleventy alternatives" section above for the current picks, or visit /alternatives/eleventy for the full list with editorial commentary on each.