Buttondown
A twenty-item day, and most of it is the import path finally behaving.
A side-by-side editorial comparison of MailPoet and Pimcore — release velocity, themes, recent moves, and the top alternatives to consider.
MailPoet's feed is near-dormant: one 2026 post, and it's about consent-gating open tracking.
This feed has almost stopped. Six of the last ten entries predate 2025, and the only substantive recent activity is a July 2026 post on French and Italian regulators deciding that email open-tracking pixels require consent — which notes MailPoet now ships controls for it. Apart from an April 2026 review-request explainer, there is no visible release cadence to read.
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.
This feed has almost stopped. Six of the last ten entries predate 2025, and the only substantive recent activity is a July 2026 post on French and Italian regulators deciding that email open-tracking pixels require consent — which notes MailPoet now ships controls for it. Apart from an April 2026 review-request explainer, there is no visible release cadence to read.
What signal exists points at compliance rather than product ambition: sender-requirement explainers in 2024, tracking-pixel consent controls in 2026. The older entries show a product that once announced features here — custom automation triggers, segmentation, automation analytics — but that stream stopped years ago. Whether development continues on another surface is not something this feed can answer.
There is not enough recent activity to forecast a next move; one product-relevant post in over a year cannot support a prediction. If consent-gated open tracking spreads past France and Italy, more compliance controls are the likeliest thing to appear.
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 MailPoet 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 MailPoet 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. Pimcore 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. Pimcore 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 MailPoet alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "MailPoet alternatives" section above for the current picks, or visit /alternatives/mailpoet 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.