OpnForm
OpnForm's V2 bet: import your Typeform, generate the PDF, self-host the lot.
Comparison · Mkt Auto
Buttondown vs Customer.io
A side-by-side editorial comparison of Buttondown and Customer.io — release velocity, themes, recent moves, and the top alternatives to consider.
Buttondown vs Customer.io: at a glance
| Feature | Buttondown | Customer.io |
|---|---|---|
| Sector | Mkt Auto | Mkt Auto |
| Velocity score | 5.0 | 7.5 |
| Sparks · 30d | 0 | 2 |
| Top themes | email newsletters, incremental fixes, accessibility, segmentation | geofencing, llm knowledge, byo sms, live notifications |
| Last editorial update | 6h ago | 4h ago |
| Website | Visit → | — |
What is Buttondown?
Buttondown ships something almost every day, and most of it is somebody's bug report.
Buttondown publishes a dated entry nearly every day, and the mix is dominated by small fixes credited to named users. The feature work in this window is narrow but real: filtered blocks for audience-specific email sections, Mermaid diagram rendering, and enhanced Bluesky link cards. Nothing here changes the product's shape.
What is Customer.io?
Location becomes a trigger, Twilio stops being the only SMS path, and the LLM layer gets a memory
The summer window widens both ends of the automation graph. On the input side, geofences turn physical entry and exit into workflow triggers and date triggers now read attributes off custom objects; on the output side, SMS opens to Sinch, Infobip, and Vonage instead of Twilio alone, and live notifications add a persistent, continuously updating message format on iOS and Android. The LLM side gains a workspace-scoped Knowledge Library that both LLM actions and the Agent can read, replacing per-prompt copy-paste. Channel-based message limits and unsubscribe-preserving profile merges tighten the send-side guardrails underneath all of it.
Buttondown vs Customer.io: editorial side-by-side
Buttondown
5.0MKT AUTO
Buttondown ships something almost every day, and most of it is somebody's bug report.
◆ Current state
Buttondown publishes a dated entry nearly every day, and the mix is dominated by small fixes credited to named users. The feature work in this window is narrow but real: filtered blocks for audience-specific email sections, Mermaid diagram rendering, and enhanced Bluesky link cards. Nothing here changes the product's shape.
◆ Where it's heading
The cadence is the strategy - a steady stream of small corrections keeps the surface tidy rather than betting on a large release. Recent additions cluster around how a publication looks off-platform: Bluesky cards, archive fonts, recognized social links, image handling. Segmentation is the one direction with real room to grow, and filtered blocks is its first visible step.
◆ Prediction
Filtered blocks is the piece most likely to expand, since per-audience content inside a single send invites conditional logic beyond one block type. The daily fix cadence should continue at its current rate.
Customer.io
7.5MKT AUTO
Location becomes a trigger, Twilio stops being the only SMS path, and the LLM layer gets a memory
◆ Current state
The summer window widens both ends of the automation graph. On the input side, geofences turn physical entry and exit into workflow triggers and date triggers now read attributes off custom objects; on the output side, SMS opens to Sinch, Infobip, and Vonage instead of Twilio alone, and live notifications add a persistent, continuously updating message format on iOS and Android. The LLM side gains a workspace-scoped Knowledge Library that both LLM actions and the Agent can read, replacing per-prompt copy-paste. Channel-based message limits and unsubscribe-preserving profile merges tighten the send-side guardrails underneath all of it.
◆ Where it's heading
Customer.io is systematically loosening the assumptions its automation graph was built on: one workspace one app, one SMS vendor, one blunt frequency cap, prompts as the only place LLM context can live. Each release swaps a hardcoded shape for a configurable one, which is what a platform does when its largest accounts have outgrown the original model. The AI work follows the same instinct — not a chatbot bolted on, but retrieval and context turned into workspace-level objects that the rest of the system can reference.
◆ Prediction
Expect the Knowledge Library to spread past LLM actions into more of the Agent's surface, and the per-channel controls to keep filling in — the release notes name WhatsApp and SMS capping outside Twilio as a live gap, which is an odd thing to leave open right after opening SMS to three new vendors.
Alternatives to Buttondown 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 Buttondown or Customer.io.
Craft CMS
Craft 6 is being rebuilt on Laravel in public, one alpha at a time
Joomla
Three release lines in parallel, and changelogs that publish checksums instead of changes
Systeme.io
Systeme.io's feed is an unbroken run of customer success stories, not a changelog.
Customer.io
Customer.io's summer wave pushes messaging into location triggers and live device surfaces.
Mautic
Mautic is patching three supported branches at once while 7.2 grinds through release candidates.
See all Buttondown alternatives → · See all Customer.io alternatives →
Recent activity from Buttondown and Customer.io
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 14h agoButtondownFiltered blocks show email sections to one audience only
- 1d agoButtondownFix: share image picker scroll arrows after preview load
- 1d agoCustomer.ioAdd reusable knowledge sources to LLM actions ⚡
- 1d agoCustomer.ioSet up SMS with Sinch, Infobip, or Vonage
- 1d agoCustomer.ioSummer recap: geofences, live notifications, inbox, SMS providers
- 1d agoCustomer.ioGeofences: message people when they enter or exit a location ⚡
- 2d agoButtondownShare image picker gains scroll arrows and arrow-key nav
- 2d agoCustomer.ioSend push notifications to multiple mobile apps in one workspace
- 3d agoButtondownBluesky archive links render as enhanced link cards
- 4d agoButtondownAccessibility fix for settings links; API key date fix
- 6d agoButtondownButtondown renders Mermaid diagrams in emails and archives
- 7d agoCustomer.ioLive notifications: real-time updates without opening your app
Frequently asked questions
What is the difference between Buttondown 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 5.0), 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.
Is Buttondown 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 5.0), 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.
What are the best alternatives to Buttondown?
Top Buttondown alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Buttondown alternatives" section above for the current picks, or visit /alternatives/buttondown 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.