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 WPForms and Pimcore — release velocity, themes, recent moves, and the top alternatives to consider.
WPForms fills its feed with tutorials while signposting a v2.0 it has not shipped here.
WPForms publishes on a near-daily tutorial cadence, and the entire visible window is instructional: connecting forms to Make.com and Slack, assembling an applicant tracker out of forms and entries, and separating confirmations from notifications. A retrospective post frames the recent stretch of releases as the road to WPForms v2.0, but the feed carries no release notes for it. What is visible is documentation of existing capability, not new capability.
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.
WPForms publishes on a near-daily tutorial cadence, and the entire visible window is instructional: connecting forms to Make.com and Slack, assembling an applicant tracker out of forms and entries, and separating confirmations from notifications. A retrospective post frames the recent stretch of releases as the road to WPForms v2.0, but the feed carries no release notes for it. What is visible is documentation of existing capability, not new capability.
The through-line across the tutorials is integration and routing — getting submissions out of WordPress and into the tools where work actually happens. Stacked with the v2.0 retrospective's claim that AI features have been accumulating quietly, the product is being positioned as a data-capture front end for other systems rather than a forms builder alone. The conversion-benchmarks post points the same way, toward measurement of what forms produce.
Given the v2.0 framing and the run of integration tutorials, the next substantive post is likely a v2.0 feature tour or another native integration walkthrough. The feed does not carry release notes, so any actual shipping detail will have to come from elsewhere.
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.
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 WPForms or Pimcore.
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 WPForms 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. WPForms and Pimcore are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. WPForms and Pimcore are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top WPForms alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "WPForms alternatives" section above for the current picks, or visit /alternatives/wpforms 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.