OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Customer.io and Joomla — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Customer.io | Joomla |
|---|---|---|
| Sector | Mkt Auto | Mkt Auto |
| Velocity score | 7.5 | 5.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | geofencing, llm-actions, multi-channel-messaging, delivery-controls | cms, security-release, parallel-branches, backports |
| Last editorial update | 4d ago | 4h ago |
| Website | — | Visit → |
Customer.io is turning messaging context — location, knowledge, carriers — into platform primitives
Customer.io came out of a summer wave carrying more than ten features, and the ones that matter reshape what a message can be triggered by and what it can know. Geofences make physical location a native trigger, reusable knowledge sources give LLM actions a workspace-scoped context layer, and SMS opens to Sinch, Infobip, and Vonage alongside Twilio. The most recent entries turn to control and craft: per-channel rate limits, and a rebuilt Design Studio canvas.
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.
Customer.io came out of a summer wave carrying more than ten features, and the ones that matter reshape what a message can be triggered by and what it can know. Geofences make physical location a native trigger, reusable knowledge sources give LLM actions a workspace-scoped context layer, and SMS opens to Sinch, Infobip, and Vonage alongside Twilio. The most recent entries turn to control and craft: per-channel rate limits, and a rebuilt Design Studio canvas.
The pattern is absorbing things customers previously bolted on — third-party geofencing, per-prompt context pasting, a single mandated SMS carrier — and making each a configurable primitive inside the platform. Delivery control is following the same path, with rate limits and wait-before-continuing giving operators throttles they would otherwise build around. Each move reduces the surface where an integration or a workaround was required.
Expect the knowledge layer and the Agent to converge further, since knowledge sources were already extended to the Agent on release, and expect more delivery-side controls now that rate limiting exists per channel. The plan gating on geofences suggests newer primitives will keep landing on Premium and Enterprise first.
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 Customer.io 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 Customer.io 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. Customer.io is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 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. Customer.io is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 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 Customer.io alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Customer.io alternatives" section above for the current picks, or visit /alternatives/customer-io 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.