Sulu
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
A side-by-side editorial comparison of Pimcore and Customer.io — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Pimcore | Customer.io |
|---|---|---|
| Sector | Mkt Auto | Mkt Auto |
| Velocity score | 5.0 | 7.5 |
| Sparks · 30d | 0 | 2 |
| Top themes | pim-dam, security-hardening, sql-injection, backport-branches | geofencing, llm knowledge, byo sms, live notifications |
| Last editorial update | 2h ago | 1d ago |
| Website | Visit → | — |
Nearly every release in this window carries security hardening — Pimcore is working through an injection sweep.
Pimcore maintains two calendar-versioned lines in parallel, 2026.2.x and 2026.1.x, with fixes landing on the newer line and selectively backported. The content is dominated by input-validation work: explicit field allowlists on Custom Report updates, an ORDER BY column allowlist for redirect listings, rejection of unwhitelisted filter properties, escaped field names in DataObject JOIN conditions, hardened unserialize paths, and CSV exports bound to the requesting user. Feature work is thin by comparison — a CDN integration and a TemplateProviderInterface extension point in 2026.2.1.
Location becomes a trigger, Twilio stops being the only SMS path, and the LLM layer gets a memory
The summer window widens both ends of the automation graph. On the input side, geofences turn physical entry and exit into workflow triggers and date triggers now read attributes off custom objects; on the output side, SMS opens to Sinch, Infobip, and Vonage instead of Twilio alone, and live notifications add a persistent, continuously updating message format on iOS and Android. The LLM side gains a workspace-scoped Knowledge Library that both LLM actions and the Agent can read, replacing per-prompt copy-paste. Channel-based message limits and unsubscribe-preserving profile merges tighten the send-side guardrails underneath all of it.
Pimcore maintains two calendar-versioned lines in parallel, 2026.2.x and 2026.1.x, with fixes landing on the newer line and selectively backported. The content is dominated by input-validation work: explicit field allowlists on Custom Report updates, an ORDER BY column allowlist for redirect listings, rejection of unwhitelisted filter properties, escaped field names in DataObject JOIN conditions, hardened unserialize paths, and CSV exports bound to the requesting user. Feature work is thin by comparison — a CDN integration and a TemplateProviderInterface extension point in 2026.2.1.
The pattern is a systematic pass over places where user input reaches SQL or deserialization, spread across releases rather than bundled into one advisory — Custom Reports alone are touched in three separate releases. Alongside it runs a slower cleanup of the v11 era: admin functions removed, admin translations deprecated, v11-specific workflows refactored to v12. A task in the most recent release adds backward-compatibility break detection to the project's own code review tooling, which reads as an attempt to keep that cleanup from breaking integrators unannounced.
Expect the hardening sweep to keep producing small paired releases on both lines, with Custom Reports and listing filters the likely remaining targets, and further admin-layer removals as the v12 cleanup continues.
The summer window widens both ends of the automation graph. On the input side, geofences turn physical entry and exit into workflow triggers and date triggers now read attributes off custom objects; on the output side, SMS opens to Sinch, Infobip, and Vonage instead of Twilio alone, and live notifications add a persistent, continuously updating message format on iOS and Android. The LLM side gains a workspace-scoped Knowledge Library that both LLM actions and the Agent can read, replacing per-prompt copy-paste. Channel-based message limits and unsubscribe-preserving profile merges tighten the send-side guardrails underneath all of it.
Customer.io is systematically loosening the assumptions its automation graph was built on: one workspace one app, one SMS vendor, one blunt frequency cap, prompts as the only place LLM context can live. Each release swaps a hardcoded shape for a configurable one, which is what a platform does when its largest accounts have outgrown the original model. The AI work follows the same instinct — not a chatbot bolted on, but retrieval and context turned into workspace-level objects that the rest of the system can reference.
Expect the Knowledge Library to spread past LLM actions into more of the Agent's surface, and the per-channel controls to keep filling in — the release notes name WhatsApp and SMS capping outside Twilio as a live gap, which is an odd thing to leave open right after opening SMS to three new vendors.
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 Customer.io.
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
The v4 canary line is being renamed Build Awesome while 3.x is kept on pure maintenance.
Steady feature-then-patch cadence, with security reports rising because AI tools are finding them
Measurement gets granular while the API quietly opens ClickFunnels up to outside agents
n8n's daily patch train hides the real work: hardening its MCP server into a proper auth resource.
OneSignal is arguing a new category into existence before showing the product behind it.
See all Pimcore alternatives → · See all Customer.io alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Customer.io is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 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. Customer.io is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 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 Customer.io alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Customer.io alternatives" section above for the current picks, or visit /alternatives/customer-io for the full list with editorial commentary on each.