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 Customer.io and Hugo — release velocity, themes, recent moves, and the top alternatives to consider.
Customer.io's summer wave pushes messaging into location triggers and live device surfaces.
Customer.io shipped a dense summer release: geofence-based triggers, live notifications that render as iOS Live Activities and Android 16 Live Updates, an in-app notification inbox, and support for bringing your own SMS provider via Sinch, Infobip, or Vonage. Alongside the headline channels are workflow-level fixes that matter operationally — channel-based message frequency limits, date triggers on custom objects, and multiple mobile apps per workspace. LLM actions gained reusable knowledge sources so prompts can reference a file or Drive doc instead of repeating pasted text.
Steady feature-then-patch cadence, with security reports rising because AI tools are finding them
Hugo is running its usual rhythm: a feature minor followed by a short run of patches. v0.164.0 added dark/light pairs for Chroma highlighter styles with matching flags on `hugo gen chromastyles`, new encoding.HexEncode, encoding.HexDecode and crypto.Hash template functions, an rst syntax-highlight option, Pandoc citation support, and sub-path support in layouts passed to Page.Render. Before it, v0.163.0 was largely a correction pass on the AVIF handling introduced in 0.162.0 — default quality dropped to 60 on the finding that JPEG and WebP at 75 are comparable, with per-format and per-image quality now configurable.
Customer.io shipped a dense summer release: geofence-based triggers, live notifications that render as iOS Live Activities and Android 16 Live Updates, an in-app notification inbox, and support for bringing your own SMS provider via Sinch, Infobip, or Vonage. Alongside the headline channels are workflow-level fixes that matter operationally — channel-based message frequency limits, date triggers on custom objects, and multiple mobile apps per workspace. LLM actions gained reusable knowledge sources so prompts can reference a file or Drive doc instead of repeating pasted text.
The direction is toward owning more of the device surface rather than more of the inbox. Live Activities, the notification inbox, and geofences all move triggering and rendering closer to where the customer physically is, which is a different competitive axis than email deliverability. At the same time, BYO SMS providers and channel-level frequency caps loosen delivery lock-in and hand rate control to the operator — a platform posture, not a messaging-tool one.
Expect the remaining device-native surfaces to fill in — richer inbox and Live Activity templating — and expect LLM actions to keep absorbing workflow context now that knowledge sources are reusable.
Hugo is running its usual rhythm: a feature minor followed by a short run of patches. v0.164.0 added dark/light pairs for Chroma highlighter styles with matching flags on `hugo gen chromastyles`, new encoding.HexEncode, encoding.HexDecode and crypto.Hash template functions, an rst syntax-highlight option, Pandoc citation support, and sub-path support in layouts passed to Page.Render. Before it, v0.163.0 was largely a correction pass on the AVIF handling introduced in 0.162.0 — default quality dropped to 60 on the finding that JPEG and WebP at 75 are comparable, with per-format and per-image quality now configurable.
The work in this window is refinement rather than expansion: image encoding defaults tuned after real-world use, template function surface extended one primitive at a time, external converter behaviour standardized. The most notable observation comes from the maintainer in v0.163.1, who attributes a rise in security reports to new AI tooling being pointed at the codebase rather than to any decline in the code — and that release, plus the code-block language escaping fix in 0.163.3, is where those reports land.
The pattern across this window points to another patch run consolidating 0.164.0 before the next minor. If the reported uptick in AI-assisted security findings continues, more of those patches will be security-driven, as 0.163.1 already was.
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 Hugo.
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.
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.
OneSignal is arguing a new category into existence before showing the product behind it.
See all Customer.io alternatives → · See all Hugo 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 2.5), 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 2.5), 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/customerio for the full list with editorial commentary on each.
Top Hugo alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Hugo alternatives" section above for the current picks, or visit /alternatives/hugo for the full list with editorial commentary on each.