OpnForm
OpnForm's V2 bet: import your Typeform, generate the PDF, self-host the lot.
A side-by-side editorial comparison of Craft CMS and WPForms — release velocity, themes, recent moves, and the top alternatives to consider.
Craft 6 is being rebuilt on Laravel in public, one alpha at a time
Craft CMS is running its 6.0 line through rapid alphas, and each one moves another subsystem onto Laravel. Blade views can now be loaded inside Twig templates with Craft registering Blade directives for near parity; asset I/O resolves through Laravel filesystem disks; queue jobs resolve dependencies through the service container; user elements implement Illuminate's HasLocalePreference. SQLite is now a supported database, login is rate limited, and accounts can connect to Socialite providers.
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.
Craft CMS is running its 6.0 line through rapid alphas, and each one moves another subsystem onto Laravel. Blade views can now be loaded inside Twig templates with Craft registering Blade directives for near parity; asset I/O resolves through Laravel filesystem disks; queue jobs resolve dependencies through the service container; user elements implement Illuminate's HasLocalePreference. SQLite is now a supported database, login is rate limited, and accounts can connect to Socialite providers.
This is a framework transplant carried out in the open. The alphas move from templating and storage (alpha.10) through identity and asset handling (alpha.11, alpha.12) to session, queue and control-panel internals (alpha.13, alpha.14) — each step replacing a Yii-era mechanism with its Laravel equivalent. alpha.14 makes the cost explicit for the ecosystem: plugins must stop declaring extra.laravel.providers and lose automatic trait lifecycle hooks, while a new first-party control-panel component library (Button, ButtonGroup, Callout, Checkbox) arrives to replace ad-hoc markup.
Expect further alphas to continue converting Yii-era subsystems and to keep breaking the plugin contract until the component library and provider model settle; a beta is unlikely before plugin authors have a stable API to target.
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.
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 Craft CMS or WPForms.
OpnForm's V2 bet: import your Typeform, generate the PDF, self-host the lot.
Three release lines in parallel, and changelogs that publish checksums instead of changes
Location becomes a trigger, Twilio stops being the only SMS path, and the LLM layer gets a memory
Buttondown ships something almost every day, and most of it is somebody's bug report.
Systeme.io's feed is an unbroken run of customer success stories, not a changelog.
Customer.io's summer wave pushes messaging into location triggers and live device surfaces.
See all Craft CMS alternatives → · See all WPForms alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Craft CMS 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. Craft CMS 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 Craft CMS alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Craft CMS alternatives" section above for the current picks, or visit /alternatives/craft-cms for the full list with editorial commentary on each.
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.