Buttondown
A twenty-item day, and most of it is the import path finally behaving.
A side-by-side editorial comparison of Pimcore and Postscript — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Postscript is handing SMS marketing to an agent that decides each subscriber's next message
Postscript is an SMS and RCS platform for Shopify merchants, and this archive shows it working two fronts at once. On acquisition it has multiplied the places a subscriber can opt in — embedded forms droppable on any page, standalone landing pages built on the popup editor, and Onsite Opt-in at Shoptin checkout. On messaging it is building Shopper, a conversational AI layer that now answers, analyses and increasingly initiates. The feed carries no publication dates, so this is an archive rather than a timeline.
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.
Postscript is an SMS and RCS platform for Shopify merchants, and this archive shows it working two fronts at once. On acquisition it has multiplied the places a subscriber can opt in — embedded forms droppable on any page, standalone landing pages built on the popup editor, and Onsite Opt-in at Shoptin checkout. On messaging it is building Shopper, a conversational AI layer that now answers, analyses and increasingly initiates. The feed carries no publication dates, so this is an archive rather than a timeline.
The centre of gravity is shifting from campaign tooling to per-subscriber decisioning. Shopper began as a responder, then gained a research surface over its own conversations, and now decides send timing and content for each individual. Alongside that, RCS is the delivery-side bet: webviews, dynamic product photos and tappable suggested replies all work to make the message thread the destination rather than a pointer to the storefront. Experimentation is being pushed into more of the journey rather than confined to campaign sends.
Expect the remaining hand-built primitives — static flows and manual segments — to be folded into Shopper's decisioning, and each new RCS capability to keep shipping with an automatic MMS or browser fallback so merchants can adopt it without maintaining a second path.
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 Pimcore or Postscript.
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
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.
Gumloop's agent triggers pick up the generic case: any webhook can start a run.
See all Pimcore alternatives → · See all Postscript 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 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. Pimcore 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 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.
Top Postscript alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Postscript alternatives" section above for the current picks, or visit /alternatives/postscript for the full list with editorial commentary on each.