n8n
n8n ships 2.40.0 with AI builder hardening while laying v3 storage migration groundwork
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 | 8.8 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | journey-builder, conditional-logic, ai-agent, messaging-channels | cms, php, security, multilingual |
| Last editorial update | 20d ago | 12d ago |
| Website | — | Visit → |
Customer.io is widening what a journey can express and where its agent can be reached.
Two threads run side by side. The automation engine keeps gaining expressiveness: per-channel rate limits in early August, and now a Wait Until block that accepts multiple delays, time windows, and And/Or/nested condition groups. Separately the AI agent moved into Slack, while messaging reach grew with transactional WhatsApp and support for multiple mobile apps in one workspace.
Joomla 6.2 enters beta with AI language fallback, XOAuth2, and a revamped TinyMCE — three tracks shipping in parallel.
Joomla is maintaining three active release tracks simultaneously: 5.4.x receives security patches, 6.1.x gets maintenance updates, and 6.2.0 is now in beta. The 6.2 beta cycle has introduced an AI-assisted language fallback chain, a generic XOAuth2 implementation, an Enum form field type, TinyMCE link selector and native readmore, and secure article preview without requiring a frontend login. A path traversal vulnerability in com_templates was patched across both 5.4.8 and 6.1.3 as simultaneous security releases.
Two threads run side by side. The automation engine keeps gaining expressiveness: per-channel rate limits in early August, and now a Wait Until block that accepts multiple delays, time windows, and And/Or/nested condition groups. Separately the AI agent moved into Slack, while messaging reach grew with transactional WhatsApp and support for multiple mobile apps in one workspace.
The Wait Until change is the clearest read on where the builder is heading: logic that previously needed a chain of wait steps now collapses into one block, which makes journeys shorter and harder to misread. Paired with rate limits and the wait-before-continuing option, timing and pacing are becoming first-class controls rather than things you assemble from primitives. The agent work runs on a separate track, pushing the product into tools people already sit in.
Expect the nested And/Or condition model to spread from Wait Until into other branching actions, since the release describes grouping as a property of the path rather than of that single block.
Joomla is maintaining three active release tracks simultaneously: 5.4.x receives security patches, 6.1.x gets maintenance updates, and 6.2.0 is now in beta. The 6.2 beta cycle has introduced an AI-assisted language fallback chain, a generic XOAuth2 implementation, an Enum form field type, TinyMCE link selector and native readmore, and secure article preview without requiring a frontend login. A path traversal vulnerability in com_templates was patched across both 5.4.8 and 6.1.3 as simultaneous security releases.
The '6.2 beta' label is doing real work: the release cycle is disciplined, with two betas already out and a feature set that has mostly stabilized. The AI-prefixed items in the changelogs (language fallback chain, login module configuration) suggest a push to make content delivery smarter across multilingual sites — though the scope is narrow so far. The three-track release model is a deliberate trade-off between stability for existing installs and forward development.
Joomla 6.2.0 stable should ship within 4-6 weeks given the beta pace. The AI-prefix features will likely expand in 6.3, particularly around content personalization and multilingual workflows. A fourth track (6.2.x security) will open once 6.2.0 ships.
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.
n8n ships 2.40.0 with AI builder hardening while laying v3 storage migration groundwork
Buttondown gives publishers granular AI-crawler controls as daily fixes continue
Gumloop ships Gumball, background subagents, and a model router in two weeks—each one changes how agents work.
Formidable Forms adds form abandonment analytics and deepens its multilingual and add-on ecosystem.
Pimcore's 2026.2 branch is in steady bug-fix mode, targeting storage races, workflow correctness, and image processing.
Moosend's only visible signal is blog content—no public product changelog available
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 8.8 vs 6.3), with 1 editorial sparks in the last 30 days against 1. 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 8.8 vs 6.3), with 1 editorial sparks in the last 30 days against 1. 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.