OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Buttondown and Vero — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Buttondown | Vero |
|---|---|---|
| Sector | Mkt Auto | Mkt Auto |
| Velocity score | 5.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | newsletters, email-marketing, bug-fixes, editor | marketing-automation, journeys, platform-migration, email |
| Last editorial update | 13h ago | 19d ago |
| Website | Visit → | — |
Buttondown ships almost daily, and most of it is someone else's bug report closed.
The changelog is a near-daily log of two to four items, overwhelmingly fixes, many crediting the customer who reported them by name. The editor accounts for a disproportionate share — pasted Word documents locking it, cursors that would not sit between stacked tables, blank lines above tables that could not be deleted. Feature work is smaller and steadier: multi-select subscribe form fields, a searchable font specimen panel, Bluesky link cards that re-sync themselves.
Marketing automation mid-migration, rebuilding Journeys branching on the 2.0 platform
Vero is running two platforms at once and the changelog reads that way. Vero 2.0 gained True/False and Exit nodes in Journeys — real conditional branching that routes customers on behavior, properties and actions — plus an SMS node, a Cmd+K command palette, Forms, and project-level reporting on the homepage summarizing messages sent, open, click and delivery rates. CC on emails shipped to Vero 1.0 campaigns with 2.0 support described as coming.
The changelog is a near-daily log of two to four items, overwhelmingly fixes, many crediting the customer who reported them by name. The editor accounts for a disproportionate share — pasted Word documents locking it, cursors that would not sit between stacked tables, blank lines above tables that could not be deleted. Feature work is smaller and steadier: multi-select subscribe form fields, a searchable font specimen panel, Bluesky link cards that re-sync themselves.
The pattern is a small team working a public queue in the open, and the fixes cluster where newsletter software actually breaks: rich-text editing, subscriber state transitions, and cross-posting to social platforms. Several recent items concern silent failures specifically — automations skipping sends without saying so, cross-posts marked failed after publishing, resubscribes quietly changing subscriber state. Correcting quiet-wrong behaviour into loud-correct behaviour is the through-line, and it matters more in a product where a mistake reaches someone's whole list.
Expect the cadence to hold and the editor to keep generating items, since that is where the reported bugs concentrate. The entries are day-stamped batches, so individual releases carry no version or theme to read direction from.
Vero is running two platforms at once and the changelog reads that way. Vero 2.0 gained True/False and Exit nodes in Journeys — real conditional branching that routes customers on behavior, properties and actions — plus an SMS node, a Cmd+K command palette, Forms, and project-level reporting on the homepage summarizing messages sent, open, click and delivery rates. CC on emails shipped to Vero 1.0 campaigns with 2.0 support described as coming.
The work is about reaching parity and then passing it. Branching and exit nodes are table stakes for a journey builder, so shipping them in 2.0 marks the point where the new platform becomes usable for real lifecycle programs rather than linear sends. The CC entry shows the migration's awkward middle — a feature landing on the old platform first. Project-level reporting suggests the next concern is proving programs work, not just building them.
Expect CC and the remaining 1.0-only capabilities to close out on 2.0, since the entries explicitly flag that gap, and reporting to deepen now that a project-level summary exists.
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 Vero.
OttoKit keeps widening its WordPress trigger surface one plugin at a time
Craft 6's alphas keep converting the plugin API, one removal at a time
Two security releases ship the same day, and 6.2 finally clears alpha
Flodesk just moved its analytics out of the dashboard and into Claude and ChatGPT.
Formidable widens MCP compatibility and locks down signature files
Mailtrap is assembling a full email operations platform, one category step at a time
See all Buttondown alternatives → · See all Vero alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Buttondown is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Buttondown is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
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.
Top Vero alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Vero alternatives" section above for the current picks, or visit /alternatives/vero for the full list with editorial commentary on each.