I’ve deployed traditional, legacy WordPress form plugins like WPForms and Gravity Forms, alongside standalone web-based SaaS platforms like Typeform and Tally. While Gravity Forms handles deep hook filtering and Typeform excels at client-side UI animations, they introduce significant data silos, ongoing subscription overhead, or expensive add-on pricing structures to access basic webhooks. I chose IvyForms because it provides complete on-premise data security, native database connections to the Melograno ecosystem, and zero entry volume caps right out of the box.
IvyForms
Thank you for such a detailed and technically grounded review, this is exactly the kind of feedback that helps us prioritize.
On calculated fields: you're right that today's conditional logic only handles show/hide, not arithmetic. The calculation fields and logic are actively in development right now — the groundwork for linked product/quantity/total fields with per-line and form-wide calculation scopes is already being built, so this is close, not just "on the list."
On the server-side throughput point: that's fair, and it's really the flip side of the same choice you praised in "vs Alternatives" — because everything lives in your own WordPress database instead of a third-party cloud service. We think owning your data outright is worth that trade, but it's a real one!
Really appreciate the depth here, comparisons like this against Gravity Forms/Typeform on real architecture (not just feature checklists) are rare and useful. Thanks for taking IvyForms on a real test drive. Stay tuned, there's a lot more growing on the vine 🌿