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 SalesBlink — 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.
Cold-email tooling that wants you to skip its own dashboard.
SalesBlink runs cold email sequences — sending, deliverability, replies, and booking. The past few months added an agent layer on top of that: an MCP server in April, an OpenClaw integration in May for autonomous outreach, and in July an AI Copilot inside the dashboard that creates and manages sequences from a prompt. The conventional product kept moving in parallel — a rebuilt meeting scheduler with whitelabel support, email security gateway detection that skips leads whose employers block cold mail, and a July roundup whose headline item is reply detection dropping from hours to seconds.
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.
SalesBlink runs cold email sequences — sending, deliverability, replies, and booking. The past few months added an agent layer on top of that: an MCP server in April, an OpenClaw integration in May for autonomous outreach, and in July an AI Copilot inside the dashboard that creates and manages sequences from a prompt. The conventional product kept moving in parallel — a rebuilt meeting scheduler with whitelabel support, email security gateway detection that skips leads whose employers block cold mail, and a July roundup whose headline item is reply detection dropping from hours to seconds.
Two threads, and they point the same way. The deliverability work treats sending capacity as the scarce resource — detecting gateways that would swallow the message, testing inbox placement, selling pre-configured mailboxes with DNS and DMARC handled — so that no send is wasted. The agent work attacks the other cost, the operator's time in the interface. Announcing an MCP server with "ditch the dashboard" and then shipping a Copilot inside the dashboard is the same bet placed twice: sequences described rather than assembled.
The AI credits framing that arrived with the Copilot is the thing to watch — a usage-metered agent sitting on top of a seat-priced outreach tool is a pricing question the entries raise but do not settle.
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 SalesBlink.
Nearly every release in this window carries security hardening — Pimcore is working through an injection sweep.
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 Sulu alternatives → · See all SalesBlink alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. SalesBlink 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. SalesBlink 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 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 SalesBlink alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "SalesBlink alternatives" section above for the current picks, or visit /alternatives/salesblink for the full list with editorial commentary on each.