OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Flodesk and Pimcore — release velocity, themes, recent moves, and the top alternatives to consider.
Flodesk just moved its analytics out of the dashboard and into Claude and ChatGPT.
Flodesk ships one clearly-scoped feature at a time, roughly twice a month, and the recent run has been list hygiene and account security: a self-maintaining unengaged-subscriber segment, reversible archiving, subject-line A/B testing, calendar view, and multi-factor authentication. The newest release breaks that pattern — a connector that lets members query their own email, subscriber, form and sales data from inside Claude or ChatGPT, read-only, at no extra cost.
Pimcore is shipping a security advisory almost every week.
Pimcore releases on a weekly-to-fortnightly patch cadence across two supported lines - 2026.2.x and the older 12.3.x - and the defining feature of the last two months is the volume of security work. Nearly every release carries at least one GHSA: WebDAV rename permissions, ImageGallery hotspot unserialize, Classificationstore field-name validation, blind SSRF via email test-send, Custom Report field allowlisting. Around it sits ordinary bug fixing in workflows, thumbnails, and data object handling.
Flodesk ships one clearly-scoped feature at a time, roughly twice a month, and the recent run has been list hygiene and account security: a self-maintaining unengaged-subscriber segment, reversible archiving, subject-line A/B testing, calendar view, and multi-factor authentication. The newest release breaks that pattern — a connector that lets members query their own email, subscriber, form and sales data from inside Claude or ChatGPT, read-only, at no extra cost.
Everything before this was about removing work inside the product; the connector removes the product from the interaction entirely for the questions people ask most. Flodesk states this is phase one, with audience segmentation and subscriber management to follow, which would turn a read-only connector into a place the account is actually operated. The security work — MFA extended to third-party API authorizations — reads in hindsight as the prerequisite that had to land first.
The stated roadmap points to write access next, starting with segmentation and subscriber management, which is where a read-only connector becomes an operating surface. What is unclear from the entries is whether campaign creation and sending follow, since that is where an external agent acting on a member's list gets genuinely consequential.
Pimcore releases on a weekly-to-fortnightly patch cadence across two supported lines - 2026.2.x and the older 12.3.x - and the defining feature of the last two months is the volume of security work. Nearly every release carries at least one GHSA: WebDAV rename permissions, ImageGallery hotspot unserialize, Classificationstore field-name validation, blind SSRF via email test-send, Custom Report field allowlisting. Around it sits ordinary bug fixing in workflows, thumbnails, and data object handling.
The advisories are not scattered; they cluster on the surfaces where Pimcore accepts structured input from an authenticated user - custom reports, classification stores, WebDAV, grid configuration. The fixes follow a consistent method of allowlisting fields, enforcing permissions at the operation rather than the screen, and refusing to echo raw database errors. Read together, this is a deliberate audit of the admin surface rather than a run of unrelated reports, and it is being done in public one patch at a time.
The audit pattern points at the remaining input-accepting admin surfaces - imports, grid and filter parsers, WebDAV operations beyond MOVE - so expect more advisories of the same shape before the cadence slows.
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 Flodesk or Pimcore.
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
Buttondown ships almost daily, and most of it is someone else's bug report closed.
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 Flodesk 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. Flodesk is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. Flodesk is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Flodesk alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Flodesk alternatives" section above for the current picks, or visit /alternatives/flodesk 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.