OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Bloomreach and Joomla — release velocity, themes, recent moves, and the top alternatives to consider.
A fortnightly version train spending its releases on governance, compliance and Loomi accuracy
Bloomreach Engagement ships on a numbered version train, roughly one release per fortnight, each bundling a few platform changes with a standing mobile SDK update. The last five versions (1.308-1.312) cover a link-shortener pattern change, faster Performance dashboards, an approval workflow for scenarios, accuracy work across Loomi Analytics, and a message archive for compliance. Each release note is a short summary tied to an explicit release window rather than an itemised changelog.
Two security releases ship the same day, and 6.2 finally clears alpha
Joomla is running three branches at once: 5.4.x as the maintenance line, 6.1.x as the current series, and 6.2.0 now in beta. On 18 August both maintenance branches shipped security releases hours apart — 5.4.8 with 32 merged PRs and 6.1.3 with four — each carrying the same 'install as soon as possible' banner. The release bodies remain download tables and SHA-256 checksums with the merged-PR list at the very end, so the actual change set is only readable from the tail.
Bloomreach Engagement ships on a numbered version train, roughly one release per fortnight, each bundling a few platform changes with a standing mobile SDK update. The last five versions (1.308-1.312) cover a link-shortener pattern change, faster Performance dashboards, an approval workflow for scenarios, accuracy work across Loomi Analytics, and a message archive for compliance. Each release note is a short summary tied to an explicit release window rather than an itemised changelog.
The recent run is less about new surface area and more about making the existing platform safe to operate at scale: approvals gate campaign automation, the message archive answers compliance and support requests, and the Loomi work targets correctness of analyses and running aggregates rather than new analysis types. Mobile SDK updates appear in four of the five releases, which reads as a continuous maintenance obligation rather than a push. The cadence itself is the most consistent signal - versions land every two to three weeks with no visible major-version break.
Expect the train to continue at the same fortnightly cadence with further Loomi Analytics refinement and incremental mobile SDK work. Note the feed shows nothing after the 1.312 window closed on 29 June 2026, so whether that cadence held through July is not visible in these entries.
Joomla is running three branches at once: 5.4.x as the maintenance line, 6.1.x as the current series, and 6.2.0 now in beta. On 18 August both maintenance branches shipped security releases hours apart — 5.4.8 with 32 merged PRs and 6.1.3 with four — each carrying the same 'install as soon as possible' banner. The release bodies remain download tables and SHA-256 checksums with the merged-PR list at the very end, so the actual change set is only readable from the tail.
The paired-branch pattern that defined the last month has now completed a full cycle: rc1 on 11 August, rc2 on 15 August, finals on 18 August, both branches in lockstep. The fix content is defensive rather than additive — path-traversal checks in com_templates, an ACL check before exposing the user edit link, division-by-zero guards in ListModel and subforms, Smart Search memory limits. Meanwhile 6.2.0 moved from Alpha 3 to Beta 1 after four static weeks, pulling in 19 PRs that include a security flag for updates, secure article preview without frontend login, and a language fallback chain for the AI subsystem.
Expect 6.2.0 to run a second beta before a release candidate, and the 5.4.x/6.1.x pair to resume their coupled patch cadence with the next rc pair a few weeks out.
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 Bloomreach or Joomla.
OttoKit keeps widening its WordPress trigger surface one plugin at a time
Craft 6's alphas keep converting the plugin API, one removal at a time
Buttondown ships almost daily, and most of it is someone else's bug report closed.
Flodesk just moved its analytics out of the dashboard and into Claude and ChatGPT.
Formidable widens MCP compatibility and locks down signature files
Mailtrap is assembling a full email operations platform, one category step at a time
See all Bloomreach alternatives → · See all Joomla alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Joomla is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. Joomla is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Bloomreach alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Bloomreach alternatives" section above for the current picks, or visit /alternatives/bloomreach for the full list with editorial commentary on each.
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.