Pimcore
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
A side-by-side editorial comparison of OpnForm and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
OpnForm is turning its V2 platform into an automation surface, one integration at a time.
OpnForm shipped V2 in June — a major release that added PDF generation, computed variables, form import from Typeform, Tally, Google Forms and Fillout, and a Free/Pro/Business/Enterprise plan system with self-hosted license gating. The three releases since have been almost entirely self-hosting repair: OIDC sign-in recovery, trusted-proxy handling, PDF template editors breaking under relative API paths. v2.3.0 is the first post-V2 release that adds capability rather than fixing it.
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.
OpnForm shipped V2 in June — a major release that added PDF generation, computed variables, form import from Typeform, Tally, Google Forms and Fillout, and a Free/Pro/Business/Enterprise plan system with self-hosted license gating. The three releases since have been almost entirely self-hosting repair: OIDC sign-in recovery, trusted-proxy handling, PDF template editors breaking under relative API paths. v2.3.0 is the first post-V2 release that adds capability rather than fixing it.
The pattern is a large platform release followed by a long tail of self-hosted fixes, and OpnForm is now coming out the other side. v2.3.0 layers automation onto the V2 foundation — Make and Albato integrations, AI-assisted formula generation for the computed variables V2 introduced, and an audio block — while still closing self-hosted PDF bugs. Feature gating is doing real work now: Custom Code and similar capabilities are tied to license entitlements, with migrations backfilling existing self-hosted records.
Expect more integration connectors and further AI assistance layered onto computed variables, since both extend V2 primitives rather than requiring new ones. The self-hosted PDF editor has needed fixes in three consecutive releases, so another round there is likely.
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.
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.
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.
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 OpnForm or Pushwoosh.
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
Three release lines running in parallel, all of them shipping nothing but fixes this week
Zoho Social opens its management surface to AI assistants via MCP.
AWeber is moving the console out of the browser and into the chat window
Building an agent-drivable outreach stack — MCP, then OpenClaw, now an in-dashboard AI copilot.
Formaloo is turning its form builder into something you describe rather than configure.
See all OpnForm alternatives → · See all Pushwoosh alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top OpnForm alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "OpnForm alternatives" section above for the current picks, or visit /alternatives/opnform for the full list with editorial commentary on each.
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.