Gumloop
The reporting layer arrives, and it counts what agents did and what they cost.
A side-by-side editorial comparison of Buttondown and listmonk — release velocity, themes, recent moves, and the top alternatives to consider.
Buttondown documents its events API, opening dashboard analytics to anyone who wants to pull them
The changelog is a near-daily log of two to four items, overwhelmingly fixes, many crediting the reporter by name. The newest entry breaks that shape: the events API is now documented, so deliveries, opens and clicks can be pulled programmatically at the same granularity the dashboard shows. Around it is the usual queue work — an RSS-to-email rollup bug traced to a 2023 kludge, duplicate subscribe-form options removed as a footgun, a change_email_address automation taught to skip cleanly when the address is already taken.
Only signal in window is an automated nightly build — no curated release to read
The single recent entry is an automated nightly build from the master branch, flagged as potentially unstable. It carries no curated changelog, so there's no user-facing signal to interpret.
The changelog is a near-daily log of two to four items, overwhelmingly fixes, many crediting the reporter by name. The newest entry breaks that shape: the events API is now documented, so deliveries, opens and clicks can be pulled programmatically at the same granularity the dashboard shows. Around it is the usual queue work — an RSS-to-email rollup bug traced to a 2023 kludge, duplicate subscribe-form options removed as a footgun, a change_email_address automation taught to skip cleanly when the address is already taken.
The through-line has been converting quiet-wrong behaviour into loud-correct behaviour: automations that skipped sends silently, resubscribes that changed state without saying so, cross-posts marked failed after they published. Documenting the events API is the same instinct pointed outward — data the product already had, made reachable instead of implied. The editor still generates the largest share of reported bugs, and that has not changed.
Expect the API surface to keep getting documented rather than expanded, since the events endpoint already existed, and the editor to keep producing the bulk of the fix queue at the current near-daily cadence.
The single recent entry is an automated nightly build from the master branch, flagged as potentially unstable. It carries no curated changelog, so there's no user-facing signal to interpret.
A lone nightly build provides no directional information. listmonk's substantive changes surface in versioned stable releases, none of which fall in this window.
Unclear from a nightly build alone; the next meaningful signal would be a tagged stable release with an actual changelog.
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 listmonk.
The reporting layer arrives, and it counts what agents did and what they cost.
The AI agent moves into Slack, so operating Customer.io no longer means opening it.
Four release lines in parallel, and nearly every patch lands on the agent builder.
AWeber keeps moving email marketing out of its own console and into whatever tool you already have open.
Three ways to drive SalesBlink without opening it: API, MCP, and now a CLI.
OttoKit keeps widening its WordPress trigger surface one plugin at a time
See all Buttondown alternatives → · See all listmonk 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 2.5), 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 2.5), 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 listmonk alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "listmonk alternatives" section above for the current picks, or visit /alternatives/listmonk for the full list with editorial commentary on each.