Buttondown
A twenty-item day, and most of it is the import path finally behaving.
A side-by-side editorial comparison of Moosend and Pimcore — release velocity, themes, recent moves, and the top alternatives to consider.
Moosend's feed is an SEO content mill; no product release is visible anywhere in it.
The window is entirely search-optimised marketing articles, most of them stamped with the year in the headline: competitor pricing breakdowns, inbound versus outbound explainers, automation how-tos, compliance guides and UGC template roundups. The most recent entry is a pricing analysis of Mailgun, a competitor. Nothing here describes a change to Moosend itself.
A patch of seven fixes, one of which stops the log tables growing forever.
2026.2.11 is a maintenance patch with no new function. The notable item is an application log archive table that grew on every maintenance run — an unbounded growth bug rather than a cosmetic one. The rest is DataObject and editor correctness: parent query-table data no longer copied into fields that do not support inheritance, empty language permission strings normalised to null in the workspace, UrlSlug edit-mode data accepted in associative form, a workflow note field that threw when not submitted, and an orphaned rel=noopener fragment leaking into WYSIWYG text.
The window is entirely search-optimised marketing articles, most of them stamped with the year in the headline: competitor pricing breakdowns, inbound versus outbound explainers, automation how-tos, compliance guides and UGC template roundups. The most recent entry is a pricing analysis of Mailgun, a competitor. Nothing here describes a change to Moosend itself.
The publishing strategy is aimed at capturing search traffic on category and competitor terms rather than documenting the product. Any real Moosend release would need to be read from a different source, because this feed does not carry release notes at all.
Expect more year-stamped category and competitor-comparison articles at the same cadence; the feed gives no basis for a product prediction.
2026.2.11 is a maintenance patch with no new function. The notable item is an application log archive table that grew on every maintenance run — an unbounded growth bug rather than a cosmetic one. The rest is DataObject and editor correctness: parent query-table data no longer copied into fields that do not support inheritance, empty language permission strings normalised to null in the workspace, UrlSlug edit-mode data accepted in associative form, a workflow note field that threw when not submitted, and an orphaned rel=noopener fragment leaking into WYSIWYG text.
The 2026.2 line has been shipping weekly, and the previous three patches all carried some function alongside their fixes. This one does not, which reads as the line settling rather than slowing — the reports it answers are concentrated in DataObject inheritance and workspace permissions, the areas the recent releases touched. Thumbnail clipping failures moving from info to error logging is the same instinct: make the existing behaviour observable before changing it.
Weekly patches on the 2026.2 line have been consistent, so 2026.2.12 within the week is the expectation. Whether it returns to carrying features depends on the DataObject reports, and the notes do not say.
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 Moosend or Pimcore.
A twenty-item day, and most of it is the import path finally behaving.
n8n's patch stream is now mostly AI-builder work wearing bug-fix labels
SalesBlink is making agents first-class clients, and just broke API-key MCP connections to do it
Postscript is handing SMS marketing to an agent that decides each subscriber's next message
Systeme.io's feed sells the consolidation story, one customer at a time.
Mailtrap pulls cross-client render testing into the sandbox that already holds the mail.
See all Moosend alternatives → · See all Pimcore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Moosend and Pimcore are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Moosend and Pimcore are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top Moosend alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Moosend alternatives" section above for the current picks, or visit /alternatives/moosend for the full list with editorial commentary on each.
Top Pimcore alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Pimcore alternatives" section above for the current picks, or visit /alternatives/pimcore for the full list with editorial commentary on each.