OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
Comparison · Mkt Auto
Craft CMS vs Customer.io
A side-by-side editorial comparison of Craft CMS and Customer.io — release velocity, themes, recent moves, and the top alternatives to consider.
Craft CMS vs Customer.io: at a glance
| Feature | Craft CMS | Customer.io |
|---|---|---|
| Sector | Mkt Auto | Mkt Auto |
| Velocity score | 6.3 | 7.5 |
| Sparks · 30d | 1 | 2 |
| Top themes | cms, laravel, plugin-api, inertia | geofencing, llm-actions, multi-channel-messaging, delivery-controls |
| Last editorial update | 4h ago | 4d ago |
| Website | Visit → | — |
What is Craft CMS?
Craft 6's alphas keep converting the plugin API, one removal at a time
Craft is running two lines with very different energy. The 5.10 maintenance branch ships one-bug releases hours apart and nothing else. Craft 6 is in its seventeenth alpha, still migrating onto Laravel: alpha 17 removes Plugin::settingsHtml() in favour of a settingsForm() built on the Control Panel Form system, replaces the Pane.vue component with a craft-pane web component, and moves another management command onto Laravel's schema API.
What is Customer.io?
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.
Craft CMS vs Customer.io: editorial side-by-side
Craft CMS
6.3MKT AUTO
Craft 6's alphas keep converting the plugin API, one removal at a time
◆ Current state
Craft is running two lines with very different energy. The 5.10 maintenance branch ships one-bug releases hours apart and nothing else. Craft 6 is in its seventeenth alpha, still migrating onto Laravel: alpha 17 removes Plugin::settingsHtml() in favour of a settingsForm() built on the Control Panel Form system, replaces the Pane.vue component with a craft-pane web component, and moves another management command onto Laravel's schema API.
◆ Where it's heading
The pattern established at alpha 14 has not changed shape, only advanced: every alpha retires another Yii-era extension point and re-lands it on the new stack, with craftcms/yii2-adapter carrying the compatibility burden. Alpha 17 adds an Inertia-native slideout system that renders any CpScreenResponse as an in-page panel, which is the control panel moving from a legacy JavaScript layer to a genuinely Inertia/Vue one rather than wrapping it. The long fix list — stale permission trees, autosave firing on unchanged values, provisional drafts created on page open, queue jobs stuck reserved — reads as the cost of that churn being paid down alpha by alpha.
◆ Prediction
Expect further alphas that remove specific Yii-era plugin APIs with adapter fallbacks, and the 5.10 line to keep shipping single-fix patches until a Craft 6 beta absorbs the team's attention.
Customer.io
7.5MKT AUTO
Customer.io is turning messaging context — location, knowledge, carriers — into platform primitives
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Craft CMS and Customer.io
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 Craft CMS or Customer.io.
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
Mailtrap
Mailtrap is assembling a full email operations platform, one category step at a time
See all Craft CMS alternatives → · See all Customer.io alternatives →
Recent activity from Craft CMS and Customer.io
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12h agoCraft CMSAlpha 17 retires plugin settingsHtml and adds Inertia slideouts
- 5d agoCustomer.ioDesign Studio: new and improved canvas editing experience
- 13d agoCustomer.ioControl how fast your automations send messages
- 13d agoCraft CMSAlpha 16 fixes double-required migrations and a widget gap
- 13d agoCraft CMS5.10.13.2 fixes a SQL error on empty Categories fields
- 14d agoCraft CMS5.10.13.1 restores rendering of sanitized SVGs
- 14d agoCraft CMSCraft 6 swaps its image pipeline to intervention/image and libvips
- 20d agoCustomer.ioSummer release roundup indexing ten-plus features
- 20d agoCustomer.ioAdd reusable knowledge sources to LLM actions ⚡
- 20d agoCustomer.ioGeofences: message people when they enter or exit a location ⚡
- 20d agoCustomer.ioSet up SMS with Sinch, Infobip, or Vonage
- 27d agoCraft CMSCraft 6 alpha 14 breaks plugin providers and lifecycle hooks ⚡
Frequently asked questions
What is the difference between Craft CMS and Customer.io?
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.
Is Craft CMS better than Customer.io?
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.
What are the best alternatives to Craft CMS?
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.
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/customer-io for the full list with editorial commentary on each.