Drip
Two-month digests that keep circling the same theme: get your data out of Drip and into your own stack.
A side-by-side editorial comparison of Kit (formerly ConvertKit) and Customer.io — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Kit (formerly ConvertKit) | Customer.io |
|---|---|---|
| Sector | Mkt Auto | Mkt Auto |
| Velocity score | 6.3 | 7.5 |
| Sparks · 30d | 1 | 2 |
| Top themes | email-marketing, mcp, landing-pages, creator-tools | geofencing, rate limiting, device surfaces, byo sms |
| Last editorial update | 11d ago | 5d ago |
| Website | Visit → | — |
Kit rebuilt its landing page editor, then handed the controls to an AI agent.
Kit's recent releases converge on one thing: giving creators a full publishing surface inside Kit rather than sending them to a third-party page builder. The landing page editor was rebuilt in June with 20+ templates and full control over layout, fonts and sections; custom favicons and the Creator profile to Newsletter site rename finished the job of making those pages feel owned rather than hosted. The newest release lets the Kit MCP build and edit those pages directly. Alongside runs an audience-intelligence thread - Subscriber Signals in early access - and network features letting creators request connections with each other.
After a summer of new send surfaces, the controls arrive: per-channel rate limits and send pacing.
Customer.io spent the summer widening where a message can land — geofence triggers, Live Activities, an in-app notification inbox, multiple mobile apps per workspace — and loosening who carries it, with Sinch, Infobip, and Vonage joining Twilio for SMS. The newest release turns to governance: per-channel rate limits on automations and API-triggered broadcasts, plus a wait-before-continuing step that holds a person in a journey until the message actually lands. The LLM layer picked up reusable knowledge sources, moving prompt context out of individual actions into a workspace-scoped library the Agent can also read.
Kit's recent releases converge on one thing: giving creators a full publishing surface inside Kit rather than sending them to a third-party page builder. The landing page editor was rebuilt in June with 20+ templates and full control over layout, fonts and sections; custom favicons and the Creator profile to Newsletter site rename finished the job of making those pages feel owned rather than hosted. The newest release lets the Kit MCP build and edit those pages directly. Alongside runs an audience-intelligence thread - Subscriber Signals in early access - and network features letting creators request connections with each other.
The Kit MCP is the axis. It arrived in May as a read-and-analyze tool - ask questions about your list, create tags or broadcasts from Claude, ChatGPT or Cursor - and has now crossed into building the actual published artifact. That sequencing is deliberate: rebuild the editor as a structured, template-driven system first, then expose it to an agent, because an agent can only assemble a page that is composed of describable parts. The rename and favicon work point the same way, toward Kit as the place a creator's web presence lives rather than just where email is sent.
Expect the MCP surface to extend from landing pages into sequences and the newsletter site itself, and Subscriber Signals to move out of early access as the data layer the agent reasons over.
Customer.io spent the summer widening where a message can land — geofence triggers, Live Activities, an in-app notification inbox, multiple mobile apps per workspace — and loosening who carries it, with Sinch, Infobip, and Vonage joining Twilio for SMS. The newest release turns to governance: per-channel rate limits on automations and API-triggered broadcasts, plus a wait-before-continuing step that holds a person in a journey until the message actually lands. The LLM layer picked up reusable knowledge sources, moving prompt context out of individual actions into a workspace-scoped library the Agent can also read.
The pattern is surface-first, control-second. Each new channel widens the blast radius, and the rate-limit release reads as the answer to customers hitting the ceiling of their own sender reputation and downstream systems. Expect reach features to keep arriving paired with the guardrails that make them safe to switch on at volume — per-channel budgets, delivery-aware waits, activity logging on every new trigger type.
The next likely move is extending rate limiting and the wait-for-delivery step from automations to the remaining send paths, and giving geofences and live notifications the segmentation and reporting depth email already has.
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 Kit (formerly ConvertKit) or Customer.io.
Two-month digests that keep circling the same theme: get your data out of Drip and into your own stack.
The forms plugin just opened its data to AI agents through an MCP adapter.
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
Three release lines running in parallel, all of them shipping nothing but fixes this week
OpnForm is turning its V2 platform into an automation surface, one integration at a time.
Zoho Social opens its management surface to AI assistants via MCP.
See all Kit (formerly ConvertKit) alternatives → · See all Customer.io 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 Kit (formerly ConvertKit) alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Kit (formerly ConvertKit) alternatives" section above for the current picks, or visit /alternatives/convertkit for the full list with editorial commentary on each.
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.