n8n
Three release lines running in parallel, all of them shipping nothing but fixes this week
Comparison · Mkt Auto
Pimcore vs Pushwoosh
A side-by-side editorial comparison of Pimcore and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
Pimcore vs Pushwoosh: at a glance
What is Pimcore?
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
Pimcore is servicing two lines in parallel — the 2026.2.x series and the older 12.3.x branch — and nearly every release carries at least one GHSA advisory. The recent run has closed unserialize abuse in ImageGallery hotspots, a Classificationstore field-name validation bypass, a Twig sandbox escape via pimcore_file_exists, and a blind SSRF through email test-send CSS fetching. The remainder is bug fixes and internal type corrections.
What is Pushwoosh?
Pushwoosh journeys can now read what a webhook says back and act on it mid-run.
The current release batch is broad but coherent. Journeys gained the ability to consume webhook response data and use returned values to personalize later steps in the same run. Messaging coverage evened out across channels, with PW_SMSSent and PW_WhatsAppSent events matching what email already emitted, and one-time WhatsApp sends no longer requiring a journey. On the web side, subscription forms can be dropped into any popup as lead capture, form field labels are editable without code, and the popup editor and targeting both got more room to work.
Pimcore vs Pushwoosh: editorial side-by-side
Pimcore
5.0MKT AUTO
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
◆ Current state
Pimcore is servicing two lines in parallel — the 2026.2.x series and the older 12.3.x branch — and nearly every release carries at least one GHSA advisory. The recent run has closed unserialize abuse in ImageGallery hotspots, a Classificationstore field-name validation bypass, a Twig sandbox escape via pimcore_file_exists, and a blind SSRF through email test-send CSS fetching. The remainder is bug fixes and internal type corrections.
◆ Where it's heading
The pattern is systematic input-validation retrofitting rather than isolated CVE response: column allowlists on Redirect listings, escaped FieldCollection names in JOIN conditions, rejected filter properties in the notification parser, CSV exports bound to the requesting user. That is a codebase being swept for a class of injection and deserialization flaws, not patched one report at a time. Feature work has effectively paused while this runs.
◆ Prediction
Expect the 2026.2.x cadence to keep pairing bug batches with security advisories until the sweep exhausts itself. The 12.3.x line looks like it will receive backport-only releases.
Pushwoosh
6.3MKT AUTO
Pushwoosh journeys can now read what a webhook says back and act on it mid-run.
◆ Current state
The current release batch is broad but coherent. Journeys gained the ability to consume webhook response data and use returned values to personalize later steps in the same run. Messaging coverage evened out across channels, with PW_SMSSent and PW_WhatsAppSent events matching what email already emitted, and one-time WhatsApp sends no longer requiring a journey. On the web side, subscription forms can be dropped into any popup as lead capture, form field labels are editable without code, and the popup editor and targeting both got more room to work.
◆ Where it's heading
Two things are being closed at once. The channel gap is narrowing — SMS and WhatsApp are being given the same event surface and standalone send path email has had, which makes them first-class for segmentation and triggering rather than journey-only endpoints. The bigger change is that journeys are becoming stateful against the outside world: a webhook step that can return a value into the run turns the journey builder from a sequencer into something closer to orchestration.
◆ Prediction
Now that webhook responses can feed a running journey, the natural extension is branching on those values and handling failure paths when the external call does not answer as expected. Expect the remaining email-only capabilities to keep arriving for SMS and WhatsApp until channel parity is complete.
Alternatives to Pimcore and Pushwoosh
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 Pushwoosh.
OpnForm
OpnForm is turning its V2 platform into an automation surface, one integration at a time.
Zoho Social
Zoho Social opens its management surface to AI assistants via MCP.
AWeber
AWeber is moving the console out of the browser and into the chat window
SalesBlink
Building an agent-drivable outreach stack — MCP, then OpenClaw, now an in-dashboard AI copilot.
Formaloo
Formaloo is turning its form builder into something you describe rather than configure.
See all Pimcore alternatives → · See all Pushwoosh alternatives →
Recent activity from Pimcore and Pushwoosh
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 16h agoPimcoreThree security advisories close unserialize, Classificationstore, and Twig sandbox holes
- 4d agoPimcore12.3 branch patch: object deserialization and Carbon assertion fixes
- 4d agoPimcoreBug batch: inheritance precedence, cache sessions, workflow checkboxes
- 6d agoPimcoreBlind SSRF in email test-send closed; language permissions enforced on grids
- 8d agoPushwooshRename subscription form field labels
- 8d agoPushwooshNew send events for SMS and WhatsApp
- 8d agoPushwooshAnimation timing for modal Rich Media
- 8d agoPushwooshBring webhook response data into a journey ⚡
- 8d agoPushwooshUse a subscription form as your Web popup content
- 8d agoPushwooshSend one-time WhatsApp messages
- 14d agoPimcoreCustom Report locked to a field allowlist; raw DB errors no longer leak
- 21d agoPimcoreQuery allowlists, JOIN escaping, and export ownership tighten the data layer
Frequently asked questions
What is the difference between Pimcore and Pushwoosh?
They serve adjacent needs but don't currently overlap on shipped themes. Pushwoosh 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.
Is Pimcore better than Pushwoosh?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pushwoosh 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.
What are the best alternatives to Pimcore?
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.
What are the best alternatives to Pushwoosh?
Top Pushwoosh alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Pushwoosh alternatives" section above for the current picks, or visit /alternatives/pushwoosh for the full list with editorial commentary on each.