OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
Comparison · Mkt Auto
Customer.io vs Hugo
A side-by-side editorial comparison of Customer.io and Hugo — release velocity, themes, recent moves, and the top alternatives to consider.
Customer.io vs Hugo: at a glance
What is Customer.io?
Customer.io spent the summer pushing messaging off the screen and into location, time, and the lock screen
The summer release cycle put more than ten features into the product, and the coherent ones are about context rather than content: geofences trigger workflows when someone enters or leaves a physical location, live notifications render as iOS Live Activities and Android Live Updates, date triggers now read attributes on custom objects, and a notification inbox retains pushes. Around that sits infrastructure work — SMS via Sinch, Infobip and Vonage, multiple mobile apps per platform in one workspace, send-rate controls on automations — and an LLM actions surface where knowledge sources can be attached once and reused across prompts. The most recent entry is editor ergonomics in Design Studio.
What is Hugo?
Hugo's releases are almost entirely asset pipeline work now: AVIF, Chroma, and import resolution.
Hugo's recent line is dominated by the asset pipeline and the markup layer rather than the site model. 0.165.0 adds css.ChromaStyles for generating highlighter stylesheets and an importContext option that makes in-memory resources resolvable from CSS @import statements across css.Build, js.Build, css.Sass, css.PostCSS and css.TailwindCSS. The releases before it tuned AVIF encoding defaults, added dark/light Chroma pairs, and closed a batch of security reports in the file and URL handling.
Customer.io vs Hugo: editorial side-by-side
Customer.io
7.5MKT AUTO
Customer.io spent the summer pushing messaging off the screen and into location, time, and the lock screen
◆ Current state
The summer release cycle put more than ten features into the product, and the coherent ones are about context rather than content: geofences trigger workflows when someone enters or leaves a physical location, live notifications render as iOS Live Activities and Android Live Updates, date triggers now read attributes on custom objects, and a notification inbox retains pushes. Around that sits infrastructure work — SMS via Sinch, Infobip and Vonage, multiple mobile apps per platform in one workspace, send-rate controls on automations — and an LLM actions surface where knowledge sources can be attached once and reused across prompts. The most recent entry is editor ergonomics in Design Studio.
◆ Where it's heading
The platform is expanding the set of things that can start a message and the set of places one can land, which is a different axis from the segmentation-and-copy tooling most of this category competes on. Geofences and live notifications both take work that previously required a specialist vendor or custom device code and make it a workflow primitive. The LLM actions work is following the same instinct — reusable knowledge sources are the beginning of prompt infrastructure rather than a prompt box — but it is the least developed of the threads. Meanwhile send-rate control and multi-app support read as enterprise deployment blockers being cleared.
◆ Prediction
Expect the location and live notification surfaces to gain the operational controls that continuous device features require, and the LLM actions path to keep accreting reusable pieces. Design Studio is receiving steady editor polish, so a broader component authoring release is plausible.
Hugo
2.5MKT AUTO
Hugo's releases are almost entirely asset pipeline work now: AVIF, Chroma, and import resolution.
◆ Current state
Hugo's recent line is dominated by the asset pipeline and the markup layer rather than the site model. 0.165.0 adds css.ChromaStyles for generating highlighter stylesheets and an importContext option that makes in-memory resources resolvable from CSS @import statements across css.Build, js.Build, css.Sass, css.PostCSS and css.TailwindCSS. The releases before it tuned AVIF encoding defaults, added dark/light Chroma pairs, and closed a batch of security reports in the file and URL handling.
◆ Where it's heading
The through-line is making Hugo's build pipeline self-sufficient — resources generated at build time can now feed the CSS and JS bundlers directly, and highlighter themes are generated rather than vendored. In parallel the project keeps tightening its security model: 0.163.1 normalized integer IPv4 host encodings and dropped symlinks from the os.* template functions, and 0.165.0 removes tailwindcss from the default security.exec.allow list, moving toward explicit opt-in for external binaries.
◆ Prediction
Expect the importContext mechanism to spread to the remaining resource transformers and further deprecations to land, given resources.PostProcess was already deprecated in favor of templates.Defer. Sites relying on the implicit tailwindcss exec permission will need to add it to their config explicitly.
Alternatives to Customer.io and Hugo
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.
Craft CMS
Craft 6's alphas keep converting the plugin API, one removal at a time
Joomla
Two security releases ship the same day, and 6.2 finally clears alpha
Buttondown
Buttondown ships almost daily, and most of it is someone else's bug report closed.
Flodesk
Flodesk just moved its analytics out of the dashboard and into Claude and ChatGPT.
Formidable Forms
Formidable widens MCP compatibility and locks down signature files
See all Customer.io alternatives → · See all Hugo alternatives →
Recent activity from Customer.io and Hugo
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoCustomer.ioDesign Studio: new and improved canvas editing experience
- 6d agoHugoHugo 0.165 adds importContext and css.ChromaStyles
- 13d agoCustomer.ioControl how fast your automations send messages
- 20d agoCustomer.ioGeofences: message people when they enter or exit a location ⚡
- 20d agoCustomer.ioSet up SMS with Sinch, Infobip, or Vonage
- 20d agoCustomer.ioAdd reusable knowledge sources to LLM actions
- 20d agoCustomer.ioCustomer.io’s Summer Release: Meet your customers where they are
- 1mo agoHugoHugo 0.164 adds Pandoc citations, crypto.Hash and dark/light Chroma pairs
- 2mo agoHugoHugo 0.163.3 fixes code block lang escaping and postcss config variants
- 2mo agoHugoHugo 0.163.2 fixes Node resolver and missing external converters
- 2mo agoHugoHugo 0.163.1 hardens URL and filesystem handling after security reports
- 2mo agoHugoHugo 0.163 retunes AVIF quality and adds per-format encoding hints
Frequently asked questions
What is the difference between Customer.io and Hugo?
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 1 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.
Is Customer.io better than Hugo?
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 1 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.
What are the best alternatives to Customer.io?
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.
What are the best alternatives to Hugo?
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.