Loading page
Both are aimed at sites without a backend. Web3Forms optimises for email delivery with an embedded access key; Formivo optimises for stored submissions you can hand to a client.
| Dimension | Formivo | Web3Forms |
|---|---|---|
| Integration | Form action URL, no key | Form action URL plus a hidden access key |
| Primary delivery | Dashboard record; email notification configurable per form | Email delivery |
| Submission dashboard | Included | Included |
| Per-form client access | Built in, revocable | Not a documented feature of the free workflow |
| Free volume | 300 submissions/month | 250 submissions/month |
| Lead statuses | Six states including converted and archived | Check current dashboard features |
Not automatically — Web3Forms designs it as a public alias for an email address. The trade-off is that anyone who copies it can post to that form, so abuse control has to come from rate limits and spam filtering rather than from the key being secret.
Yes, on different forms. Point one form at Web3Forms and another at Formivo; they are independent endpoints.