OpnForm
OpnForm's V2 bet: import your Typeform, generate the PDF, self-host the lot.
A side-by-side editorial comparison of Customer.io and Craft CMS — 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.
Craft 6 is being rebuilt on Laravel in public, one alpha at a time
Craft CMS is running its 6.0 line through rapid alphas, and each one moves another subsystem onto Laravel. Blade views can now be loaded inside Twig templates with Craft registering Blade directives for near parity; asset I/O resolves through Laravel filesystem disks; queue jobs resolve dependencies through the service container; user elements implement Illuminate's HasLocalePreference. SQLite is now a supported database, login is rate limited, and accounts can connect to Socialite providers.
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.
Craft CMS is running its 6.0 line through rapid alphas, and each one moves another subsystem onto Laravel. Blade views can now be loaded inside Twig templates with Craft registering Blade directives for near parity; asset I/O resolves through Laravel filesystem disks; queue jobs resolve dependencies through the service container; user elements implement Illuminate's HasLocalePreference. SQLite is now a supported database, login is rate limited, and accounts can connect to Socialite providers.
This is a framework transplant carried out in the open. The alphas move from templating and storage (alpha.10) through identity and asset handling (alpha.11, alpha.12) to session, queue and control-panel internals (alpha.13, alpha.14) — each step replacing a Yii-era mechanism with its Laravel equivalent. alpha.14 makes the cost explicit for the ecosystem: plugins must stop declaring extra.laravel.providers and lose automatic trait lifecycle hooks, while a new first-party control-panel component library (Button, ButtonGroup, Callout, Checkbox) arrives to replace ad-hoc markup.
Expect further alphas to continue converting Yii-era subsystems and to keep breaking the plugin contract until the component library and provider model settle; a beta is unlikely before plugin authors have a stable API to target.
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 Craft CMS.
OpnForm's V2 bet: import your Typeform, generate the PDF, self-host the lot.
Three release lines in parallel, and changelogs that publish checksums instead of changes
Location becomes a trigger, Twilio stops being the only SMS path, and the LLM layer gets a memory
Buttondown ships something almost every day, and most of it is somebody's bug report.
Systeme.io's feed is an unbroken run of customer success stories, not a changelog.
Mautic is patching three supported branches at once while 7.2 grinds through release candidates.
See all Customer.io alternatives → · See all Craft CMS 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 6.3), with 2 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 7.5 vs 6.3), with 2 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/customerio for the full list with editorial commentary on each.
Top Craft CMS alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Craft CMS alternatives" section above for the current picks, or visit /alternatives/craft-cms for the full list with editorial commentary on each.