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 OneSignal and Pimcore — release velocity, themes, recent moves, and the top alternatives to consider.
OneSignal is arguing a new category into existence before showing the product behind it.
OneSignal's feed in this window is entirely editorial — no release notes at all. What it publishes is a positioning campaign for "autonomous lifecycle marketing": software that operates the customer lifecycle instead of marketers operating software. Around the category essays sit displacement pieces aimed at email-first tools and practical guides to mobile surfaces like Live Activities and SMS.
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.
OneSignal's feed in this window is entirely editorial — no release notes at all. What it publishes is a positioning campaign for "autonomous lifecycle marketing": software that operates the customer lifecycle instead of marketers operating software. Around the category essays sit displacement pieces aimed at email-first tools and practical guides to mobile surfaces like Live Activities and SMS.
The through-line is a category land-grab. OneSignal defines the term first, then positions its multi-channel reach — push, SMS, in-app, lock-screen — as the reason an email-first stack cannot follow it there. One post points at AI agents taking over lifecycle tasks, the first hint of product underneath the argument, but the feed carries no release detail to confirm what actually shipped.
Expect the AI-teammate framing to harden into named, documented features, because the category argument now needs a product to point at. What ships and when is not determinable from these entries.
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 OneSignal 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.
Kit rebuilt its landing page editor, then handed the controls to an AI agent.
See all OneSignal 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. OneSignal and Pimcore 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. OneSignal and Pimcore 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 OneSignal alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "OneSignal alternatives" section above for the current picks, or visit /alternatives/onesignal 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.