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 Joomla and OneSignal — release velocity, themes, recent moves, and the top alternatives to consider.
Three release lines in parallel, and changelogs that publish checksums instead of changes
Joomla is running three lines at once: 5.4.x maintenance, 6.1.x stable, and a 6.2 alpha. The GitHub release feed is the only signal captured here and it carries no feature detail — every entry repeats the same template of contributor counts, merged-PR counts, download links and SHA-256 checksums, with user-facing notes deferred to an off-site release page. Volume is the only thing that distinguishes them: 5.4.7 merged 43+ pull requests where the 6.1.2 candidates carry one apiece.
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.
Joomla is running three lines at once: 5.4.x maintenance, 6.1.x stable, and a 6.2 alpha. The GitHub release feed is the only signal captured here and it carries no feature detail — every entry repeats the same template of contributor counts, merged-PR counts, download links and SHA-256 checksums, with user-facing notes deferred to an off-site release page. Volume is the only thing that distinguishes them: 5.4.7 merged 43+ pull requests where the 6.1.2 candidates carry one apiece.
The pattern is a CMS mid-transition, keeping the 5.x line on a heavy maintenance drip while 6.1 stabilises and 6.2 opens in alpha. Every release links a new migration guide and new developer documentation, which suggests the 5-to-6 upgrade path remains the project's central concern. Where the capability surface is heading isn't determinable from this feed — that information simply isn't published in it.
Expect continued parallel maintenance on 5.4.x and 6.1.x with 6.2 progressing through further alphas; the entries give no basis for calling what 6.2 will actually contain.
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.
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 Joomla or OneSignal.
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
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.
See all Joomla alternatives → · See all OneSignal alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Joomla and OneSignal 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. Joomla and OneSignal 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 Joomla alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Joomla alternatives" section above for the current picks, or visit /alternatives/joomla for the full list with editorial commentary on each.
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.